Chun Tian (binghe) <[EMAIL PROTECTED]> writes:
> I'm using many Debian servers on i386 and amd64 to deploy openafs network,
> I only see ONE afsd process when openafs-client is running.
> Without -rmtsys, my process table is like this:
> root 11303 0.0 0.0 2016 560 ? Ss 08:31 0:00
> /sbin/afsd -afsdb -dynroot -fakestat
> root 11305 0.0 0.0 0 0 ? S 08:31 0:00 [afsd]
That's two processes named afsd, which is what I was thinking of;
apologies for not being clear. (You may well be correct that the second
one is just a kernel thread.)
> Two REAL processes is started, but this is normal, because the 2132-2141
> lines of afsd.c says:
> if (afsd_rmtsys) {
> if (afsd_verbose)
> printf("%s: Forking 'rmtsys' daemon.\n", rn);
> code = fork();
> if (code == 0) {
> /* Child */
> rmtsysd();
> exit(1);
> }
> }
Aha, okay. Thanks for looking into that!
> If you have i386 debian box, I think its quite easy to find this (two
> afsd, and one didn't close). Acturally, I'm still not sure the AFS/NFS
> trans can work, studying. But when I stop openafs-client, the process
> which the first afsd forked still here:
> root 11893 0.0 0.1 3028 1812 pts/12 S 08:34 0:00
> /sbin/afsd -rmtsys -afsdb -dynroot -fakestat
> Seems Debian initscript use afsd -shutdown to stop afs client, maybe
> this part have a bug?
That would be my guess. I'm not sure how this is supposed to work.
I'll raise this with upstream.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
