|
From: Joe Z. <jz...@at...> - 2003-06-11 01:48:59
|
D'Arcey Carroll wrote:
>This is my second try with this message. I've "successfully subscribed" 2 or
>3 times, but only 1 of my messages has made it to the list, and I never
>receive any.
>
>Please read the details and any associated ("duplicate") bugs related to
>RedHat Bugzilla #90036:
>
>http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=90036
>
>pointedly referenced in RedHat Bugzilla #82820:
>
>http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=82820
>
>
>It seems that there is no reliable workaround, but that you could
>theoretically launch the smbmount in the background (mount -t smbfs ... &),
>note the PID, and 'kill -TERM' the process later. Perhaps a 'umount' would
>properly kill it??? Based on the bug description, it seems as though the
>mounter should be functioning properly, it just cannot properly daemonize
>and return.
>
>Thoughts?
>
>DC
>
>
>
I read your related message on June 6th. I couldn't find the bug report
on bugzilla when I tried earlier, I'm glad you found it. It matches the
symptoms I've observed. When it hangs, there are 2 smbmount processes,
one forked from the other. I have to kill the child (the parent too? I
don't remember) and then smbmount terminates okay.
To try to do that in bobs would likely be sloppy. I'd have to be careful
not to kill other smbmount processes. The right way is to wait for glibc
to be fixed, but I couldn't tell when that will be from looking at the
bug report.
Joe
PS - I'm CC'ing you directly in case you still have problems receiving
the list messages.
|