Red Hat Bugzilla – Bug 63052
amd service inoperational after a suspend
Last modified: 2014-03-16 22:26:45 EDT
Description of Problem: On a laptop with an active 'amd' service after a suspend and resume 'service amd status' reports something like that "amd (pid 12117) is running..." but no mounts are occuring until the service is restarted. I think that 'NETFS_RESTART="yes"' is responsible as it unmounts also something like '<host>:(pid12117) on /net type nfs ....' rendering amd as good as dead. Either unmounting on suspend has to be limited only to remote hosts (better) or upon resume amd status checked and restarted if it is running. 'service amd condrestart' hopefuly will do. Yes, I would use autofs instead if it would be capable to mount NFS exported trees instead of single file systems. Before that this is not a good proposition. Not sure at this moment if "public beta" is affected the same way but quite likely this is the case.
Well, indeed, the following 'apmcontinue' scripts seems to solve the matter: #!/bin/bash PROG="$1" case "$PROG" in resume) if [ "$NETFS_RESTART" = "yes" ] ; then if ! mount | grep -q 'on /net type nfs' ; then /sbin/service amd condrestart fi fi ;; esac
Closing out bugs on older unsupported releases. Apologies for any lack of response. Please reopen if it persists on current releases such as Fedora Core 3.