Search results for query: *

More specifically, I'm looking for the correct search that would be used for the nss modules inside of ldap.conf.

Greetings all, I'm currently running SuSE 10 Linux as a LDAP client that authenticates against my company's Active Directory servers for logins. I have everything working in terms of logins, home directory creation, etc., however my login times range in the 3 to 4 second range. Many articles...

Turns out I was missing the following line in my /etc/pam.d/common-auth file: auth [default=1 success=ignore] pam_succeed_if.so uid > 1000 quiet

I'm hoping someone can help point me in the right direction. I've got a SuSE 10 server setup to use LDAP and authenticate against our AD domain controller. getent password and ldapsearch works fine, in fact I can su - <AD user> successfully as well, however I'm not able to ssh into the server...

Does anyone know of a way to disable monitoring or alerting of hundreds of nodes at a time? For example, using the send-event.pl script I was able to bulk load 700 devices by passing the program an IP address. I'd like to be able to do something similar, but in this particular case just...

That sounds correct. You could either run it hourly as a cronjob or you could run it manually after you run your useradd commands. Whichever works better for your particular situation.

Rsync will allow you to do that. Keep in mind that if you want to create a user you'll need to copy /etc/passwd and possibly /etc/group and if you want their passwords the same you'll need to replicate /etc/shadow. From there they'll need a home directory to login to which is why rsync'ing an...

You could use one "central" node to make the changes on and rsync could replicate just the changes the other servers. Rsync at it's most basic level does file copying, but it also can just send deltas based on the number of machines you'd like to set it up with. In essence you'd be creating a...

I agree with Annihilanic, NIS or LDAP would be more ideal solutions. However if you think your environment will stay small another easy tool to consider is rsync. You can configure a cronjob between the machines to make sure they all stay the same. Just do a manpage on rync or google it and...

You could always try setting up a Jumpstart server. Assuming you have enough free space on a master server to house the CDs it's pretty easy to setup. I don't have my documentation in front of me now, but if you do a google search for jumpstart solaris 8 I'm sure you could come up with the steps.

I think it works for incoming and outgoing mail, but could be mistaken. Anyone else have any experience with using the /etc/mail/aliases file?

FYI...if you're running an older version of Solaris (like me), the following command will show you the number of free inodes: # df -F ufs -o i HTH bp

Gallows, I believe if you edit /etc/mail/aliases you can achieve the desired results. The syntax would look something like this for accounts named testuser and sgreen: testuser bobjones@hotmail.com sgreen bonecrusher@gmail.com If for some reason my syntax is wrong just do a man page on...

keak, The time out is most likely caused by how you have the TCPKeepAlive option set in sshd_config. Please see the following link for a brief explanation. http://drupal.star.bnl.gov/STAR/comp/sofi/facility-access/ssh-stable-con/ If this documentation is unclear you could also try doing some...

Try chmod -R 775 /x/hdisk1 It will give the read/write/execute permissions to anyone in the 'users' group.

Gallows, Not all Sun gear has hardware RAID controllers so you most likely have everything setup as best as possible with the options available to you. Please see the link below for instructions on setting up a RAID 0 container using SVM (Solaris Volume Manager)/Disk Suite...

Unfortunately with some cables you'll need a null modem adapter. By no means am I an electrical engineer, but having experienced most of what Sun has to offer I can tell you that this is most likely the cause of your lack of signal. Sounds like your hyper term settings are correct though...

If I'm understanding your question correctly the server is giving errors now because you took the workstation offline. You're most likely mounting a share off of the workstation onto the server. While logged into the server as root run the following command: # mount | grep workstationname In...

Unfortunately without some sort of auditing enabled this sort of information is unlikely to exist. As Ken stated your best bet will depend on the user's shell. Try looking in the user's home directory for the following files: .bash_history .sh_history These are the history files created for...

CPU - psrinfo -v Memory - prtdiag -v prtdiag -v will show you most attached devices, but the best tool available for concise memory output is memconf. disk - format I/O adapters - you can use prtdiag -v or cfgadm -al HTH