What happens if during a long running period, you restart a daemon. Then it throws off your timestamp. Daemons are again shutdown in an order different than they started in.
Tom K said: > Tom K wrote: > >> If you add -t to the ls command in the leftover section, you get a >> list by modification time, with the newest first. So I'm going to try >> using that for all daemons, and removing the DAEMONS-based if >> statement altogether. I'll let you know how I get on, but I'd also be >> very grateful for any comments. >> > Well, it seems to work. With all daemons running, including my > manually-started ones, the modified rc.shutdown closed them all in > reverse start order, and with no error messages. I think I'll run with > it for a while, then submit a feature request. > > _______________________________________________ > arch mailing list > [email protected] > http://www.archlinux.org/mailman/listinfo/arch > -- Bender: It was horrible! A nightmare! Fry: What happened? Bender: I dreamt I was in a place of 0's and 1's and all of a sudden... I saw a two *whimper* Fry: It's ok Bender, don't worry. There's no such thing as 2's. -------------------------- There are only 10 types of people in the world; those who understand binary and those who don't. _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
