ntpdate should not run in runlevel S

[Fabio Marzocca]

Only things that need to be run once to get the system into a consistent state
(aka system scripts) are to be run in runlevel S. As many users need to remove
ntpdate at startup, they dangerously play with rcS.d directory. Moving ntpdate
into user's runlevel (2-3-4-5) will be more proper and will give some more time
to wireless devices to be up. Furthermore, it could also fix bug #19034.

[Matt Zimmerman (mdz)]

Correct system time is important for a properly functioning system, including
the services which start in runlevel 2.

[Fabio Marzocca (thesaltydog)]

(In reply to comment #1)
> Correct system time is important for a properly functioning system, including
> the services which start in runlevel 2.

I didn't say they are not important.
I said that runlevel S is not the right place for ntpdate, and this is causing a
lot of people manually going with root permissions into rcS.d directory.
I thought it was also a matter of safety, considering that ntpdate is giving
problems to wireless that are a little bit slower to synchronize than the short
runlevel S boot time. So often computers are hanging on waiting for ntpdate, and
it is not fair, because it should be enough to move it into rc2.d with an high
sequence number.

[Matt Zimmerman (mdz)]

(In reply to comment #2)
> (In reply to comment #1)
> > Correct system time is important for a properly functioning system, including
> > the services which start in runlevel 2.
>
> I didn't say they are not important.

I am saying that it is important to have it run early, in runlevel S. It was
placed there intentionally. Having the time change in the middle of the startup
process is undesirable.