You are not logged in.

#1 2012-01-26 02:39:23

twelveeighty
Member
From: Alberta, Canada
Registered: 2011-09-04
Posts: 311

Has UDEV_TIMEOUT been dropped from rc.conf as an option?

I was merging changes with a recent rc.conf.pacnew and I noticed that UDEV_TIMEOUT is not part of that file.

I also checked with 'man rc.conf' and it's not listed there either. It that no longer a valid option in rc.conf? If so, where should that timeout be configured now?

Offline

#2 2012-01-26 02:40:18

falconindy
Developer
From: New York, USA
Registered: 2009-10-22
Posts: 4,094
Website

Re: Has UDEV_TIMEOUT been dropped from rc.conf as an option?

Offline

#3 2012-01-26 02:48:26

twelveeighty
Member
From: Alberta, Canada
Registered: 2011-09-04
Posts: 311

Re: Has UDEV_TIMEOUT been dropped from rc.conf as an option?

Puzzling - since the timeout is still 30 seconds, but that commit msg states it should be 120 seconds now that the setting in rc.conf is ignored...?

Offline

#4 2012-01-26 02:53:54

falconindy
Developer
From: New York, USA
Registered: 2009-10-22
Posts: 4,094
Website

Re: Has UDEV_TIMEOUT been dropped from rc.conf as an option?

Not sure where you're seeing a 30 second default timeout. The timeout on worker processes is not the same as the timeout on udevadm's settle call.

Offline

#5 2012-01-26 03:01:09

twelveeighty
Member
From: Alberta, Canada
Registered: 2011-09-04
Posts: 311

Re: Has UDEV_TIMEOUT been dropped from rc.conf as an option?

OK - so this is different from the timeout that I see during boot, which is 30 secs:

Wed Jan 25 19:49:47 2012: :: Waiting for UDev uevents to be processed    [BUSY] udevd[160]: worker [187] timeout, kill it
Wed Jan 25 19:49:47 2012: udevd[160]: seq 1347 '/devices/pci0000:00/0000:00:1c.1/0000:07:00.0' killed
Wed Jan 25 19:49:47 2012: udevd[160]: worker [187] terminated by signal 9 (Killed)

Offline

#6 2012-01-26 03:06:40

falconindy
Developer
From: New York, USA
Registered: 2009-10-22
Posts: 4,094
Website

Re: Has UDEV_TIMEOUT been dropped from rc.conf as an option?

...which is the timeout on worker processes. You do not have control over this.

Offline

Board footer

Powered by FluxBB