On 10/29/2013 02:51 AM, Cristian Rodríguez wrote:
El 28/10/13 18:34, Lee Duncan escribió:
On 10/29/2013 02:25 AM, Cristian Rodríguez wrote:
And they do not require the directory to be clean, at start up.
I find "wrong" a bit strong, as it is working as designed, and the system around it has changed.
I would agree it should be updated, but it certainly is not currently breaking anything.
But please feel free to file a bug on it, and assign it to me (lduncan at suse dot com).
we do have that requirement.. that's why /var/lock existed and now /run/lock does. unless we want applications failing in subtle ways of course..
I understand it is an issue, but one unrelated to systemd integration.
The daemon has to be running for the device to show up, so by the time udev gets called there is no need to tell iscsid anything.
That was the piece of the puzzle that wasn't clear to me, if there is no kernel event *before* starting the daemon then my suggestion does not apply.