At 7:42 AM -0600 10/29/03, Charles Howse wrote:
Note below, that the connection was opened on the 28th, but
did not close, however the connection to "Seeds" closed
about 4 mins after I opened it.
Snippet from /var/log/moe.log
[2003/10/28 12:11:13, 1] smbd/service.c:make_connection_snum(698)
moe (192.168.254.4) connect to service WWW initially as user nobody
(uid=65534, gid=65534) (pid 3064)
[2003/10/28 15:31:04, 1] smbd/service.c:make_connection_snum(698)
moe (192.168.254.4) connect to service Seeds initially as user nobody
(uid=65534, gid=65534) (pid 3064)
[2003/10/28 15:35:49, 1] smbd/service.c:close_cnum(880)
moe (192.168.254.4) closed connection to service Seeds
Am I way off target here, or do I have a process that isn't
disconnecting when it should?
How can I find out why the connection to "WWW" didn't close,
and prevent that from happening in the future?
I believe that what happens is that samba starts a process
which handles connections as they come-and-go from the
client machine. If you make additional connections, you'll
notice that they all happen to 'pid 3064' (in the above
example). I expect samba does this because there are times
when the windows client will make a whole bunch of very
short-lived connections, and it's better to have one process
which keeps track of client-information than to rebuild all
that information every time.
I'm not much of an expert on the low-level details, but I can
say that what you're seeing is also what I've seen, and that
I believe samba is supposed to work that way.
--
Garance Alistair Drosehn = [EMAIL PROTECTED]
Senior Systems Programmer or [EMAIL PROTECTED]
Rensselaer Polytechnic Institute or [EMAIL PROTECTED]
_______________________________________________
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
