multiple instances of the same script?

paul phsdv at
Sat Mar 10 14:24:52 GMT 2007


The most important thing is that you can and should not miss any events. 
Each events should be dealt with in my opinion.

My udev rules has:
ACTION=="add",    SUBSYSTEM=="block", KERNEL=="*[!0-9]", 
RUN="/usr/sbin/initctl emit block-device-added %k -eDEVNAME"
So only block device (like /dev/hda) will generate an event, and not 
partitions on a block device (like /dev/hda1). Therefore point 1 is not 
an issue.

My problem is the a second different block device (like /dev/hdb) is not 
dealt with at the moment.


Hervé Fache wrote:
> Two cases:
> 1. if the devices are on the same physical device (sda1, sda2, sda5, 
> ...), then you do NOT want them to run at the same time
> 2. if the devices are not on the same physical device, then you could 
> benefit from parallelism
> So I think the answer should be NO, until interesting complication is 
> added to support case no 2.
> Just my R$ 0.02
> Hervé.
> On 3/10/07, *paul * <phsdv at <mailto:phsdv at>> wrote:
>     Hello,
>     Can multiple instance of the same script run at the same  time?
>     For example 2 or more block-device-added events happen directly after
>     each other. The first event will start a script. Before this
>     script ends
>     the second block-device-added event will happen. Will a second
>     instance
>     of the same script be launched? I have the impression that this is not
>     the case, but I think that  this is needed. On my test system udev
>     generates 2 block-device-added events, but only the first event is
>     dealt
>     with. The second event was emitted, but not dealt with.
>     regards,
>     Paul
>     --
>     upstart-devel mailing list
>     upstart-devel at <mailto:upstart-devel at>
>     Modify settings or unsubscribe at:

More information about the upstart-devel mailing list