That is the client hostname. There are others, but I'm just trying to get this one working first, then I'll mess with the others.

On 6/16/2010 12:53 AM, Gustin Johnson wrote:
On 10-06-02 06:34 PM, Josh Rector wrote:
voyage:/var/log/samba# ls
cores                                   log.__ffff_192.168.0.2
log.nmbd           log.smbd
log.0.0.0.0                           log.d3s1gn2bph34r3d
log.nmbd.1.gz    log.smbd.1.gz
log.__ffff_192.168.0.104     log.dad_desktop             log.nmbd.old
----------------------------------------------------------------------------------------

vi /var/log/samba/log.d3s1gn2bph34r3d

returned:

[2010/05/15 20:04:02,  0] lib/util_sock.c:write_data(1136)
[2010/05/15 20:04:02,  0] lib/util_sock.c:get_peer_addr_internal(1676)
   getpeername failed. Error was Transport endpoint is not connected
   write_data: write failure in writing to client 0.0.0.0. Error
Connection reset
[2010/05/15 20:04:02,  0] smbd/process.c:srv_send_smb(74)
   Error writing 4 bytes to client. -1. (Transport endpoint is not connected)
-------------------------------------------------------------------------------

is that what you're looking for?

Usually the logname is log.client_ip or log.client_hostname

Is d3s1gn2bph34r3d the hostname of the client or the server?



_______________________________________________
Voyage-linux mailing list
[email protected]
http://list.voyage.hk/mailman/listinfo/voyage-linux
_______________________________________________
Voyage-linux mailing list
[email protected]
http://list.voyage.hk/mailman/listinfo/voyage-linux

Reply via email to