On Wed, Oct 30, 2013 at 8:29 PM, Tracy Reed <tr...@ultraviolet.org> wrote:
> On Wed, Oct 30, 2013 at 04:38:09PM PDT, Mathew Snyder spake thusly: > > Hopefully it is simply a matter of finding a practical way to pass the -y > > option as that seems to be the crux of all this. > > It seems like that would be a simple matter of modifying an init script. On > RedHat-like systems the file /etc/rc.sysinit looks to be the right place. > It > has a $fsckoptions variable and other interesting places to hack in a -y. > Just > watch out for yum etc. potentially wiping out your changes during upgrades. > Actually, I think -y may be the cause of this? Historically it meant "fix the utterly trivial stuff and abort and force admin intervention if anything else is seen, even if it is simple", and it may still have that meaning for some filesystems. Then again, fsck manpage on Centos6.4 implies the old -n behavior (just check, never fix) no longer exists and -n is now what -y used to be. I suggest you verify that -y means what you expect for all the filesystem types you support. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
_______________________________________________ Tech mailing list Tech@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
