Just a side note. I'm aware that some of you folks may have appear to have
no problems. However I can only report on what I've seen. This happened last
night on a system I was recovering and I double checked it this morning by
doing some independent tests. The system I was recovering was 4.0D, my tests
were on 4.0E - so it's o/s independent. If you don't have a problem - great
news! But note this for future reference, you never know if it might come in
handy!
Dave.
-----Original Message-----
From: dave.campbell_at_vf.vodafone.co.uk
[mailto:dave.campbell_at_vf.vodafone.co.uk]
Sent: 23 June 1999 13:47
To: tru64-unix-managers_at_ornl.gov
Subject: SUMMARY: Possible problem with fstab and lsmbstartup
Folks,
Please note the following very carefully and pass it onto anyone who either
builds or manages Tru64 Unix boxes.
If a system is using LSM, a problem can occur that will prevent LSM from
starting at system boot. This will manifest itself as a `test: argument
expected` message just before the point where the message `Starting LSM`
would normally occur. LSM will then not start and the system cannot be
booted to multi-user mode. This is due to the root volume entry in fstab
being separated using tabs instead of normal white space.
If a system is using LSM, ensure the fstab file for the root volume entry
only is separated by white space, e.g.
root_domain#root / advfs rw 0 0
The script /sbin/lsmbstartup makes a check for a line in fstab containing
`/` surrounded by spaces. This check will return a null value if tabs are
used.
Regards,
Dave.
Received on Wed Jun 23 1999 - 14:43:06 NZST