OK. Left things going over night. I left strace going too... and at some
point the smbclient processes did leeave pause and attempt to reconnect.
(Probably wehn updatedb ran via the cron).
These would correspond to that:
07:43:09 caffeine kernel: smb_offerconn: state valid, pid=2964
07:43:09 caffeine kernel: smb_retry: new connection pid=2964
07:43:09 caffeine kernel: smb_proc_readdir_long: error=-5, retrying
When deliberatly try to access the volumes though... no luck. No signals
sent to the smbclient processes, etc.
11:26:04 caffeine kernel: smb_request: result -32, setting invalid
11:26:15 caffeine kernel: smb_retry: timed out, try again later
11:26:15 caffeine kernel: smb_request: result -32, setting invalid
11:26:26 caffeine kernel: smb_retry: timed out, try again later
Then, later on - when trying to read the directories I get these:
11:30:43 caffeine kernel: smb_retry: timed out, try again later
11:30:43 caffeine kernel: smb_lookup: find //cacerts.htm failed, error=-5
(I've trimmed the output to make it fit in 80 columns).
-Chris
P.S. Why has the connection stuff been moved into user space? Its seems a
tad unreliable having to keep a user-space program around just to
access volumes, which may be an very infrequent times.
Things like shutdown scripts can also interfere here surely...
(likewise with killall5)