> |I'm having a problem where telneting into one of our user machines
> |(Ultra 10) is sourcing some other environment variable data from other
> |than the login user's .profile.
It is almost certainly using an existing environment (that of inetd)
rather than sourcing a file.
Quote:> |I've checked the /etc/profile and /etc/passwd to make sure everything
> |looks okay. I also truss'd the inet.d process to see what was being
> |executed on telnet login but that appeared normal.
Find the PID of inetd and do...
/usr/ucb/ps eww <PID>
If you have a USER variable defined, that's bad.
Quote:> I had this happen once - did someone su to root and then start inetd?
> If so, inetd captured their $USER variable and is passing it on to
> everyone else. If this is the problem, the fix is easy:
> su -
> pkill inetd
> /usr/sbin/inetd -s
Nope. You'll change the USER, but it will still exist...
Quote:> (or just reboot) and then make sure the person who restarted it knows
> they should almost never need to do that on Solaris - kill -HUP will
> make it re-read the inetd.conf file.
Great advice. Don't kill inetd unless extremely necessary.
To fix without rebooting though, start it like this...
/usr/bin/env -i PATH=/usr/sbin:/usr/bin TZ=US/Pacific /usr/sbin/inetd -s
Replace TZ with your proper timezone, obviously.
> Working for, but definitely not speaking for, Sun Microsystems, Inc.
Unix System Administrator Taos - The SysAdmin Company
Got some Dr Pepper? San Francisco, CA bay area
< How are you gentlemen!! Take off every '.SIG'!! >