> Those are also race conditions, and bugs. If the stop and start commands > return control before the action is completed, the results cannot be relied > on. The 'restart' command is not the only way that an admin may > programmatically stop and start a service; you might do this with something > based on puppet, for instance, with the intent of having the service fully > stopped before you edit its state, then restart it afterwards, so a race > here can even lead to corruption.
Just opened a bug[1] about the issue, since many daemons use start-stop- daemon, fixing it there would solve many race conditions. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694980 -- Salvo Tomaselli -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201212022254.36278.tipos...@tiscali.it