<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 07/06/2017 02:50 AM, Charles Lepple
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:56ED9270-F704-41E4-AB0D-D45D105CD26B@gmail.com">
<div class="moz-text-plain" wrap="true" graphical-quote="true"
style="font-family: -moz-fixed; font-size: 13px;"
lang="x-western">
<blockquote type="cite" style="color: #000000;">
<pre wrap="">On Jul 5, 2017, at 7:45 PM, Manuel Wolfshant <a class="moz-txt-link-rfc2396E" href="mailto:wolfy@nobugconsulting.ro" moz-do-not-send="true"><wolfy@nobugconsulting.ro></a> wrote:
udevadm control --reload ||:
</pre>
</blockquote>
<pre wrap="">from the man page:
--reload
Signal systemd-udevd to reload the rules files and other databases like the kernel module index. Reloading rules and databases does not apply any changes to already existing devices; the new configuration will only be applied to new events.
So that might not be sufficient for devices that are plugged in at the time the package is installed.</pre>
</div>
</blockquote>
<p> Thanks for the heads up. Docs say:<br>
</p>
<blockquote>
<pre>I've installed udev rules and want udev to do something about it.
udevadm trigger --action=change
*and* Depend on udev (you can't udevadm when udev is
unconfigured)
The action argument is of utmost importance. Without it, the
kernel will tell udev to treat all devices as *NEW*. This will
have lots of side-effects you are probably not expecting.
"change" is completely safe. It tells udev just to refresh
devices, and make sure everything's as it should be.
</pre>
<p><br>
</p>
</blockquote>
<p>So I have changed my spec file to issue the trigger command you
mentioned earlier.</p>
<p><br>
</p>
</body>
</html>