"Matthew C. Aycock" <[EMAIL PROTECTED]> wrote: > On Wed, 2005-11-09 at 15:26, [EMAIL PROTECTED] wrote: > > "Matthew C. Aycock" <[EMAIL PROTECTED]> wrote: > > I've seen similar things, but only when the SRSS files under > > /tmp/SUNWut have been damaged by some external activity like a > > /tmp cleaner cronjob. > > This is exactly what happened I am afraid. In your experience was a > reboot of the server necessary or just killing the multiple sessions > and allowing them to be recreated enough?
The only way to be really sure that the system is in a sane configuration would be to do a cold restart of SRSS. (An actual reboot isn't necessary.) However, if you've been running for a while after the damage occurred and have only had a couple of reports of lost/duplicated sessions then there's a good chance that you might get away with leaving SRSS running and just killing off the lost sessions. I'd probably cross my fingers, mark this server "offline" via 'utadm -f' so that it stops accepting new sessions (other group members will take the new ones), then tell everyone who already has a logged-in session on this server that it will be going down briefly at the end of tomorrow and that they should log out at a convenient time before then and start a new session on a different server. When they're all off, or when the announced time arrives, do a cold restart. Remember to run 'utadm -n' after the restart, so that the machine can accept new login sessions. OttoM. __ ottomeister Disclaimer: These are my opinions. I do not speak for my employer. -- ___________________________________________________ Play 100s of games for FREE! http://games.mail.com/ _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
