where are fsck return values documented?

I see /etc/rc.d/fsck checks fsck return values.

Where are they documented?

I see some in fsck_* sources.

I think 4 is for fsck_msdos.

8 is in fsck_msdos and fsck_ffs and fsck_lfs

fsck_ext2fs, fsck_ffs and fsck_lfs have 12

I am not sure about 2.

And where does 130 come from?

  Jeremy C. Reed

On Sat, Feb 23, 2008 at 08:43:33PM +0000, Christos Zoulas
wrote:
  | In article <Pine.NEB.4.64.0802231040260.19597tx.reedmedia.net>,
  | Jeremy C. Reed <reedreedmedia.net> wrote:
  | >And where does 130 come from?
  | >
  | 
  | 128 + 2 [SIGNALLED + SIGINT], should not really be
there, but fsck_msdos
  | does not catch signals :-( Someone should fix it 

Is it worth converting fsck(8) and fsck_*(8) to correctly
re-raise the default handler for SIGINT, as per
	http://www.c
ons.org/cracauer/sigint.html
?

I'm not sure how to detect that an application exited
with a signal from sh(1).


(I've converted various tools in the tree to using
raise_default_signal(3) (in libutil) so that they have
the signal behaviour as described in the URL above.)

> They are documented now in fsck.8

Thank you for documenting these.

Now I noticed it reboots every time (per exit code 4 and
rc.d/fsck script) 
after MARKING FILE SYSTEM CLEAN with "Root filesystem
was modified, 
rebooting ..."

I don't recall it ever doing that before. I know it had
option to reboot 
before but I don't remember ever noticing that happening to
me.

Something else change to cause this?

I see the new fsck man page says "and updating the
mount was 
unsuccessful". I just don't think I saw any indication
of that -- or maybe 
I don't know what that means.

Is this necessary? Why?

  Jeremy C. Reed