Ah indeed. But this has worked by sheer accident, not by design. udev
rules aren't supposed for this, and if they write any files it should be
into /dev/ or /run. They can race in both ways: before the file system
becomes available, or they run too late when the display manager is
already starting (admittedly the latter is much less probable, but still
possible).
The cleanest solution for this would be to move that logic into an
init.d file/upstart job/systemd unit, so that you can put it into the
proper place in the boot sequence. As a hack you could either add a
WAIT_FOR clause and wait on a file (in /run or so) that only starts to
exist after the fs becomes writable, or add a waiting loop to the RUN
clause (/bin/sh -c 'while [ ! -w /etc ]; do sleep 0.5; done; ln -s
...').
** Summary changed:
- udev rule file naming requirements changed breaking compatibility to Ubuntu
12.04
+ udev rule file execution races with fs to become writable
** Changed in: systemd (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1319047
Title:
udev rule file execution races with fs to become writable
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1319047/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
