Thanks to replies from:
William_Bochnik
Richard Jackson
Ettore Aldrovandi
Oisin McGuinness
Dr. Thomas Blinn
The general consensus is that Digital Unix/Compaq Tru64 doesn't natively handle logging the output of the rc*d script results to anything but the console (/dev/console).
Suggestions ranged from putting "2>&1 | tee /path/to/logfile" into one spot or another in the rc structure (probably within the rc0, rc1, rc2, rc3 scripts themselves, where they call the individual S* and K* scripts), or to change the rc calls in /etc/inittab to do the same thing. Strong words of warning from Oisin about fiddling with that file and the location of the desired logfile, to ensure it's to a filesystem that is mounted and writeable at the time the rc scripts are run. Additional warnings about making changes to the rc[0-3] scripts themselves, as they would likely be overwritten during an upgrade.
Not sure what I'm going to do yet, but rest assured I'll be taking the advice given to document it carefully for the next guy to come along after me who has to maintain this.
Thanks all.
>>> Rick Greene <GREENER_at_labs.wyeth.com> 5/10/01 12:38:08 PM >>>
After searching through the archives as best I could, I didn't see any direct answer to this (though someone had asked the question)
Under HP-UX, there is a file that captures the results of the various /sbin/rc*.d/* scripts being executed. Is there no matching functionality under Digital Unix 4.0D?
One summary did say that the person was going to add "tee -a $LOG_FILE" to the individual script calls in /sbin/rc0, /sbin/rc2, and /sbin/rc3, but this would only catch the standard output, not the standard error from the script, correct?
Thanks,
Rick Greene
Consultant, Systems Programming
UNTIL May 11 | AFTER May 14
Wyeth-Ayerst | Wyeth-Ayerst
280 King of Prussia Road |31 Morehall Road
Radnor PA 19087 |Frazer PA 19355
610-902-7560 |484-563-2405
fax 610-964-3947 |fax:
Received on Fri May 11 2001 - 18:39:29 NZST