on 1st Karmic machine:
manually restart atd
atd mail test
== it works
on another Karmic machine:
atd mail test
== it fails
manually restart atd
atd mail test
== it works
In order to be thorough, I rebooted the first machine, did *not* manually restart atd, and re-tried my mail test. It still worked. So my workaround for this problem appears to be manually restarting atd everywhere.
The quirk in this is that all of my Karmic machines had already had nscd installed, and then rebooted several times. So presumably atd had *already* been restarted during those reboots.
Maybe it's also relevant that I first had Jaunty installed on all of these machines, then upgraded to Karmic?
So the following questions still remain:
- shouldn't an atd stop/start due to a machine reboot have fixed this?
- should there be package modifications to atd, nscd, and/or libgcrypt to fix, document, or work around this problem?
Here's what I tried:
on 1st Karmic machine:
manually restart atd
atd mail test
== it works
on another Karmic machine:
atd mail test
== it fails
manually restart atd
atd mail test
== it works
In order to be thorough, I rebooted the first machine, did *not* manually restart atd, and re-tried my mail test. It still worked. So my workaround for this problem appears to be manually restarting atd everywhere.
The quirk in this is that all of my Karmic machines had already had nscd installed, and then rebooted several times. So presumably atd had *already* been restarted during those reboots.
Maybe it's also relevant that I first had Jaunty installed on all of these machines, then upgraded to Karmic?
So the following questions still remain:
- shouldn't an atd stop/start due to a machine reboot have fixed this?
- should there be package modifications to atd, nscd, and/or libgcrypt to fix, document, or work around this problem?