On 17:36 07 Feb 2002, Gilberto Ramírez <[EMAIL PROTECTED]> wrote: | How can I avoid Running fsck after the machine turn off accidentaly o reset. | Because when I turn it back on, it makes me run fsck command on my partitions | mannually, and I have like 30 machines with this problem, and is problem | because I onle have access this machines by network (rsh) or (telnet) | I have Red Hat 6.2.
But you MUST run fsck after a dirty shutdown because the fielsystems may be in almost any state of disrepair due to caches not being flushed to disc. Now, since you're just going to run "fsck -y" anyway then one could argue that just making the boot fsck script do that would do. The reason it's manual is partly historic, partly to alert you to machines badly shutdown (which should almost never happen, and points to a more serious underlying issue you should fix) and partly because pre-fsck there were cruder tools which gave more control to the person running them, but less automation for when you wanted to say "just fix it". BTW, both rsh and telnet are VERY insecure. We only allow access to our machines with ssh. -- Cameron Simpson, DoD#743 [EMAIL PROTECTED] http://www.zip.com.au/~cs/ Shoulder holsters. Beautiful women in business suits with shoulder holsters. I think it's hot. It really appeals to me. - H. Rollins _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
