> -Original Message-
> From: David Herrmann [mailto:dh.herrm...@gmail.com]
> Sent: Thursday, September 18, 2014 1:57 PM
> To: Hoyer, Marko (ADITG/SW2)
> Cc: systemd-devel@lists.freedesktop.org; Harald Hoyer; Kay Sievers
> Subject: Re: [systemd-devel] cdrom_id opens devic
Hi again
On Thu, Sep 18, 2014 at 1:34 PM, David Herrmann wrote:
> I'm putting Harald and Kay on CC, as they added O_EXCL to protect
> against parallel burning-sessions. Maybe they can tell you whether
> that is still needed today and whether we can drop it.
So my conception of O_EXCL was kinda w
Hi
On Thu, Sep 18, 2014 at 1:02 PM, Hoyer, Marko (ADITG/SW2)
wrote:
> Thx for the answer.
>
> The automounter is listening to the udev socket so it is actually waiting for
> the
> event to be processed completely. But unfortunately, it appears that sequences
> of change events might come in a sh
> -Original Message-
> From: David Herrmann [mailto:dh.herrm...@gmail.com]
> Sent: Thursday, September 18, 2014 10:31 AM
> To: Hoyer, Marko (ADITG/SW2)
> Cc: systemd-devel@lists.freedesktop.org
> Subject: Re: [systemd-devel] cdrom_id opens device with O_EXCL, why?
>
Hi
On Thu, Sep 18, 2014 at 8:22 AM, Hoyer, Marko (ADITG/SW2)
wrote:
> Hello together,
>
> I recently stumbled over cdrom_id opening the device with the O_EXCL flag
> set, if it is not currently mounted:
>
> "fd = open(node, O_RDONLY|O_NONBLOCK|(is_mounted(node) ? 0 : O_EXCL));"
>
> The effect of
> -Original Message-
> From: Hoyer, Marko (ADITG/SW2)
> Sent: Thursday, September 18, 2014 8:22 AM
> To: systemd-devel@lists.freedesktop.org
> Subject: cdrom_id opens device with O_EXCL, why?
>
> Hello together,
>
> I recently stumbled over cdrom_id opening the device with the O_EXCL flag
Hello together,
I recently stumbled over cdrom_id opening the device with the O_EXCL flag set,
if it is not currently mounted:
"fd = open(node, O_RDONLY|O_NONBLOCK|(is_mounted(node) ? 0 : O_EXCL));"
The effect of this is that automatically mounting a cdrom sometimes results in
"resource busy",
