>It's now Sunday, so hopefully Wally Terhune and U2 support helped you get
your system back up and healthy.
Greetings,
Thanks to everyone for their support, moral and technical, throughout this
ordeal. The U2 support folks were GREAT!, especially Paul Chang and Jim
Abshire. I'm not out of the woods yet, but I'm in much better shape now than
yesterday at this time!
Some things that helped:
I ran a sys_check after the first crash, which saved a lot of important
information in a .html file
Almost all of my Unidata install was on a separate disk which was
unaffected by the crash
After the second crash, we saw where we were headed and had everyone
start
preparing for the worst while the system was available
And excellent support from both IBM (UniData) and HP (the OS)
Some things I still have to figure out:
Print queues seem to be set up correctly, but they're not printing (jobs
hang in the queue)
We're running on a 40-user 30-day temporary license. Gotta fix that
Monday.
Our normal login routines aren't working. (see below)
And I have to rebuild a lot of OS startup files, etc
Login procedure problem: We used to point user logins to a udt startup
script by naming it as the shell in /etc/passwd. So, for example, a user
name TEST would have as the default shell in /etc/password something like
/unidata/local/bin/udtlogin. That script would set UDTBIN, UDTHOME, etc then
cd to the unidata account directory, then start unidata. The advantage of
this is that the user never gets to the Unix command prompt. When they leave
Unidata, their session goes away. It doesn't work now for some reason. It
never goes into Unidata. Instead the session starts up then ends abruptly.
OK, back to work I go.
Dana Baron
System Manager
Smugglers' Notch Resort
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
