Yet another UDEV question

Yet another UDEV question

[Kilau, Scott]

Hi everyone,

Sorry to bug again.

What is the "proper" way to inform the udev subsystem
that I have added some new rules in /etc/udev/rules.d ?

I did see this from:
http://www.reactivated.net/writing_udev_rules.html

> If your kernel does not have inotify support,
> new rules will not be detected automatically.
> In this situation, you must run udevcontrol reload_rules
> after making any rule file modifications for those
> modifications to take effect. 

The problem is that Red Hat AS/ES/WS 4 does not have the "udevcontrol"
command.

Is it fair to say that if "udevcontrol" does not exist,
then hunting down the process id of "udevd", and sending
it a kill -HUP would work okay?

Or is there a better way to do it under distros that do not have
"udevcontrol"?

Thanks yet again!
Scott Kilau
Digi International

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: Yet another UDEV question

[Greg KH]

On Tue, Nov 28, 2006 at 02:55:48PM -0600, Kilau, Scott wrote:
> Hi everyone,
> 
> Sorry to bug again.
> 
> What is the "proper" way to inform the udev subsystem
> that I have added some new rules in /etc/udev/rules.d ?
> 
> I did see this from:
> http://www.reactivated.net/writing_udev_rules.html
> 
> > If your kernel does not have inotify support,
> > new rules will not be detected automatically.
> > In this situation, you must run udevcontrol reload_rules
> > after making any rule file modifications for those
> > modifications to take effect. 
> 
> The problem is that Red Hat AS/ES/WS 4 does not have the "udevcontrol"
> command.
> 
> Is it fair to say that if "udevcontrol" does not exist,
> then hunting down the process id of "udevd", and sending
> it a kill -HUP would work okay?
> 
> Or is there a better way to do it under distros that do not have
> "udevcontrol"?

Ick, RH4 is pretty old for udev.  I'd suggest asking RH for what to do
here, as that system is pretty far off of mainline for a variety of
different things (kernel and udev).  They might have added inotify, and
you could be fine.

thanks,

greg k-h

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel