Hello,sorry, I kept it short because I hoped, you might be able to reproduce it easily.
The output of http://owww.molgen.mpg.de/~buczek/autofs-demo/AAA_test.sh is in http://owww.molgen.mpg.de/~buczek/autofs-demo/AAA_test.log. Clearly the expiry stops after the first HUP. Maps not changed. The two config files are also in http://owww.molgen.mpg.de/~buczek/autofs-demo/.
Thank you ! Donald Am 01.12.2013 08:21, schrieb Ian Kent:
On 30 Nov 2013, at 6:11 pm, Donald Buczek <buczek@xxxxxxxxxxxxx> wrote: Hello, autofs-5.0.8 kernel 3.8.2 I've noticed, that in our installation mounts stop expiring after we send the daemon a SIGHUP to notify it about map updates.I don't see that here.Debug log from the daemon seems to confirm that, the regular "st_expire: state 1 path... " messages no longer appear after the HUP is received and processed ("re-reading master map"...).There have been a couple of changes in that area, I'll have a look around. Can you give a bit more detail about the problem like: does it happen the very first time every time. are there specific changes that trigger the behaviour. does it happen if no changes are actually made. what sort of activity is happening when the problem occurs. and a look at the log would probably be useful.Maybe the signal goes to the st_queue_handler task?The signal goes to the main thread and the thread is responsible for adding tasks to the task queue as needed. That's pretty much only for readmap and program exit, but alarms (which trigger the expire runs) are cleared and set at various places, mostly at the start and end of expire run.Regards Donald Buczek -- Donald Buczek buczek@xxxxxxxxxxxxx Tel: +49 30 8413 1433
-- Donald Buczek buczek@xxxxxxxxxxxxx Tel: +49 30 8413 1433
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
