From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703 Description of problem: After suspending my laptop with apm -s, then resuming it, named is correctly restarted, but amd (that uses only named from localhost to resolve names, as mandated by my /etc/resolv.conf) is no longer able to mount /net/<hostname> mountpoints any longer. I have to restart it in order for such mountpoints to work again. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.service amd start 2.apm -s 3.<resume> 4.ls /net/<NFSserver> 5.service amd reload 6.ls /net/<NFSserver> 7.service amd restart 8.ls /net/<NFSserver> Actual Results: 4 and 6 fail to mount, whereas 8 works (unless your NFSserver won't let you mount, in which case the whole thing was pointless :-) Expected Results: Ideally amd should be restarted over suspend/resume, just like named. Additional info:
And the solution is similar to that of bug 80228, namely, add amd to RESTORESERVICES in /etc/sysconfig/apmd.
Is there any problem with simply adding amd to RESTORESERVICES in /etc/sysconfig/apm? It seems like a very simple fix. Am I missing any reason for it to not have been put in after such a long time?
fixed in 3.0.2-20
Thanks, verified.