Search results for query: *

You also might want to check if you've been the victim of a Trojan (someone sub'd the passwd binary for their own, and has now collected passwords).

Check the man page for the shadow file - lots of stuff on pw aging.

Oops - missed the part about it running OK before the patches. You could try looking at all the patches (showrev -p), and making an educated guess which patch is causing the problem and backing it out. Checking with the app vendor would help - they usually have patch revs that work with their...

More info needed: 1. Do you have routed running? 2. Do you have the default route before or after you can reach servers? 3. How are the systems involved connected (hub, switch, router,etc)?

If you don't have Sun's compiler (use 'which cc'), go to www.gnu.org and get the gcc compiler. RTM and you should be fine.

It could be that the app in question was written for Wincrap and ported (however poorly) to Solaris. I agree with Butterfly: look into a better video card.

Set the env var SHELL to whatever shell you need it to be

What do you see when you do the iostat, vmstat , etc when the system seems to lockup (as opposed to BEFORE it happens)? You might want to check the output of ipcs and netstat -af inet.

You might want to look into ssh/scp; that way, there are no passwords anywhere in cleartext. You just have to keep your private key read-only by the user (400). :)

Perhaps the answer they were looking for was "dynamic kernel". In SunOS, you had to edit files and recompile the kernel to change the kernel; Solaris doesn't require that. BSD vs. SVR4 is another possibility. You could also mention sockets, TLI and STREAMS, etc.

Have an entry in /etc/shells?

Or you could use NIS if you're running Unix....but be careful with nsswitch.conf.

I emailed Tech Support a few weeks ago and was told that Networker uses space on each tape for overhead, and that this message signifies that a backup ran over into that space (v6.1.1). Or it could mean you won the lottery. ;-)

Look at the docs on the website for "Directives"; I was able to skip NT temp files from my Solaris NW server.

How about routes? Can the client and server reach each other in 0-2 hops? Is the D drive local to that client? Make sure that you have both short and long names in the hosts files (myserver and myserver.mydomain.com)

I've been using NW since 1995. Is this enough time? We're using 6.1.1 build 238 (latest, I think), and boy there are funky things going on. My personal favorite is the Read-Only/Recyclable problem (which just surfaced 2 weeks ago): mark a volume as Recyc, and sometimes it never does.

I reported this to Tech Support and they told me it was "interesting"; never heard anything further. I had an NT admin restart the client service on the Exchange cluster and it cleared up by itself (v. 6.1.1 build 238).

Is the Win2k server a Networker server or client? Are you using virtual IPs (one hostname, 2 addresses)? I was not able to make VIPS and Unix Networker play together nicely. We set up a separate subnet for backups (one card), and the other card gets used for everything else.

Ooooook. How about people that DON'T work for Legato? ;)

Create a mail alias that contains a list of users to receive the mail, along with root on that system. In the notifications window, stick in "myalias@whatever.com".