------- 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. > > > > If you need to write a file during early boot before the filesystem is > > > guaranteed to be set up, it would be better to use /run for this instead > > > of > > > /var/lib. > > > Ok.. Our requirement is : > > We have static vpd.db file under /var/lib/lsvpd which contains system VPD. > > We use udev script to detect change in devices so that next time someone > > requests to read from vpd.db we can refresh the database and get upto date > > information. > > Is /run recommended for this kind of usage? > > "static" seems to be relative here, since with the current logic you are > asking for it to be regenerated at least once every boot. If the contents > do not need to persist across reboots, then /run is appropriate. If you do > want to save the results across reboots so that they're available early, and > only regenerated if needed, then /var/lib/lsvpd is appropriate. > > But I think the only consumers of this database are tools that are run later > in boot (i.e. after reaching multi-user.target), and the database will > always be regenerated unconditionally on boot because there's no other way > to know if the database contents match the current system the disk is > attached to. So it seems to me that /run would be perfectly correct for all > of this. This may need some code changes. Let me give a try and get back to you. -Vasant -- 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
