Just HOW BAD is an ungraceful shutdown? I.e., when somebody just hits
switch? Besides forcing an fsck, would fsck tell me if some file were
BTW, I'm having the 'XX interrupt' problem on boot-up as well,
syslogd. I added the ';;' to the default case, but that didn't do it.
starting and stopping syslogd from the command line with the same
cause the message. I'm guessing, then, that it's a BASH 2.0 problem?
switching the order of syslogd & klogd didn't change things; syslogd
it. I'm afraid that's about the limit of my analytical ability with
doing a LOT more reading. (heck, I wasn't even sure if switching the
order was a
David L. Parsley He's a real UNIX Man, sitting in his UNIX LAN
In the Mind of God Making all his UNIX .plans -- for nobody.
UNIX Man - If the Beatles were Programmers
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com