--=-=-=
* Wed Jul 16 2003 Juan Quintela <[EMAIL PROTECTED]> 1.0.4-1mdk
- remove patch5 (time.h) already included upstream. - remove patch2 no-chroot (not needed after removing patch0). - remove patch0 (drop privs) included better patch upstream. - 1.0.4.
--=-=-=
I just updated this package, and rpc.mountd crashes on the second request it gets:
Restart the NFS services:
[EMAIL PROTECTED] root]# service nfs stop Stopping NFS mountd: [FAILED] Stopping NFS daemon: [FAILED] Stopping NFS services: [ OK ] [EMAIL PROTECTED] root]# service nfs start Starting NFS services: [ OK ] Starting NFS daemon: [ OK ] Starting NFS mountd: [ OK ]
check to see if rpc.mountd is running:
[EMAIL PROTECTED] root]# service nfs status rpc.mountd (pid 3192) is running... nfsd (pid 3181) is running... 3180 (pid 3179) is running... 3178 (pid 3177) is running... 3174 (pid 3173) is running... 3172 (pid ) is running...
on the remote system: # ls /mirrors/cooker/SRPMS
check to see if rpc.mountd is still running:
[EMAIL PROTECTED] root]# service nfs status rpc.mountd (pid 3192) is running... nfsd (pid 3181) is running... 3180 (pid 3179) is running... 3178 (pid 3177) is running... 3174 (pid 3173) is running... 3172 (pid ) is running...
on the remote system:
# ls /mirrors/contrib/SRPMS *ls: /mirrors/contrib/SRPMS: No such file or directory*
check to see if rpc.mountd is running:
[EMAIL PROTECTED] root]# service nfs status *rpc.mountd is stopped* nfsd (pid 3181) is running... 3180 (pid 3179) is running... 3178 (pid 3177) is running... 3174 (pid 3173) is running... 3172 (pid ) is running...
On my network this is reproduceable. rpc.mountd survives the first request, the second request kills it. Anybody else see this behaviour?
regards,
Stefan
smime.p7s
Description: S/MIME Cryptographic Signature