Comment 14 for bug 833891

Quoting Kees Cook (<email address hidden>):
> It might be interesting to see if races are solved (or introduced) by
> having watershed itself offer a "daemonize" option to put itself in the
> background and immediately return to the caller (udev). This may solve it.

Kees, do you think it will introduce problems if the vgchange returns
an error but, now that watershed daemonizes and does not propagate
vgchange's exit status, the udev rule doesn't see it?

It seems to me there's no graceful recovery from that anyway so it
shouldn't really matter, but clearly I could be missing something.

thanks,
-serge