On Wed, Apr 19, 2017 at 09:49:25AM -0000, bugproxy wrote: > ------- Comment From [email protected] 2017-04-19 05:48 EDT------- > (In reply to comment #19) > > On Tue, Apr 18, 2017 at 11:49:17AM -0000, bugproxy wrote: > > > > Alternatively, is it possible that it's being run while the root > > > > filesystem > > > > is still mounted read only?
> > > Its possible during early boot.. But we see message even after booting > > > the system. > > Do you mean that the timestamp of when the message was generated was after > > system boot? Do you have a way that you are injecting kernel events, so > > that this udev rule is triggered post-boot? > What I meant is, every change in /sys/device entry causes this script to > trigger irrespective of whether its during boot time -OR- runtime. Sure. But I think what we need to understand is if a change in /sys/device post-boot also triggers the failure, or if it works as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682774 Title: [systemd-udevd] Process '/bin/touch /var/lib/lsvpd/run.vpdupdate' failed with exit code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvpd/+bug/1682774/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
