I read the man page for udevadm: --reload-rules
Signal udevd to reload the rules files. The udev daemon detects
changes automatically, this option is usually not needed. Reloading
rules does not apply any changes to already existing devices.
However, James' error is quite telling:
Jul 31 21:21:46 neptune udevd[409]: specified user 'tss' unknown
Jul 31 21:21:46 neptune udevd[409]: specified group 'tss' unknown
The package is both adding the user group and a udev rule. It may a bug in udev that it isn't doing another lookup if it can't find the group in its cache, but adding a "udevadm control --reload-rules" seems easy enough and ok for an SRU.
I read the man page for udevadm:
--reload- rules
Signal udevd to reload the rules files. The udev daemon detects
changes automatically, this option is usually not needed. Reloading
rules does not apply any changes to already existing devices.
However, James' error is quite telling:
Jul 31 21:21:46 neptune udevd[409]: specified user 'tss' unknown
Jul 31 21:21:46 neptune udevd[409]: specified group 'tss' unknown
The package is both adding the user group and a udev rule. It may a bug in udev that it isn't doing another lookup if it can't find the group in its cache, but adding a "udevadm control --reload-rules" seems easy enough and ok for an SRU.