Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices

Welcome to LinuxQuestions.org, a friendly and active Linux Community.

You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.

If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.

Having a problem logging in? Please visit this page to clear all LQ-related cookies.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

Why? You can always boot in level 3, mount the file system read-only, and run fsck by hand.

Looking at my /etc/rc.d/rc.sysinit suggests that a touch /forcefsck will cause a full fsck run next time you restart, since rc.sysinit checks for the presence of the forcefsck file in / before it runs fsck, and adds the -f option if it's found.

-w Donít actually reboot or halt but only write the wtmp record (in the /var/log/wtmp file).

-d Donít write the wtmp record. The -n flag implies -d.

-f Force halt or reboot, donít call shutdown(8).

-i Shut down all network interfaces just before halt or reboot.

-h Put all harddrives on the system in standby mode just before halt or poweroff.

-p When halting the system, do a poweroff. This is the default when halt is called as poweroff.

So, if I read that correctly, -f just reboots simulating a power failure. And, yes, pulling the plug on you system and then restarting will force fsck, but skipping the shutdown processing seems just a little drastic if you can get by with running a normal reboot.

It's your choice, Abe, but let us know how you make out.

And megaspaz, thanks for the reboot suggestion -- I hadn't realized that reboothad any options.