4.2 fsck and /etc/rc question

[Ed Trujillo]

Why does the following scenario happen under 4.2 running on a vax 750?

At boot time,  fsck finds out that the root file system was modified so 
it exits with a condition code of 4 that is passed on to /etc/rc which 
immediately does an /etc/reboot -n.  According to the documentation for
reboot the -n option avoids the sync.  Why then does fsck do a sync() 
before the call to exit(4) ???  Is there a logical reason for this?

BTW, this apparent bug didn't appear in the 4.2 buglist.
-- 

Ed(mund) Trujillo @ CADLINC, Menlo Park, CA
{amd,decwrl,nsc,seismo,spar}!turtlevax!edmund