samba2.0.6 write errors

[H.-P. Ermert]

Hallo,

We can see the same kind of Error Logs (the write errors) with
samba-2.0.5a on our Solaris-Server.
This kind of message ist produced every night at 3:00 am, when we reboot
our WinCenter Servers
and we too would like to know if these write failures can be problem.
I think we do not have the 'Gethostbyaddr failed' errors.

Peter

prasad.jampala at convergys.com wrote:
> 
> I am running Samba 2.0.6 on Solaris 2.6 and I have a bunch
> of write errors showing up in my log.smb file. Here are some of them:
> ----------------------------------------------
> 
> [1999/12/16 14:25:42, 1] lib/util_sock.c:client_name(997)
>   Gethostbyaddr failed for 10.41.0.184
> [1999/12/16 14:25:42, 0] lib/util_sock.c:write_socket_data(537)
>   write_socket_data: write failure. Error = Broken pipe
> [1999/12/16 14:25:42, 0] lib/util_sock.c:write_socket(563)
>   write_socket: Error writing 4 bytes to socket 7: ERRNO = Broken pipe
> [1999/12/16 14:25:42, 0] lib/util_sock.c:send_smb(751)
>   Error writing 4 bytes to client. -1. Exiting
> ------------------------------------------------
> My questions are:
> - Is something broken in my samba?
> - Why is Gethostbyaddr failing? Is this causing other errors?
> 
> Except for the above errors everything seems to be working. I can connect
> to
> all my defined shares. Please let me know if you need more information.

---
Ing. Buero Ermert, Dipl. Inform Hanns-Peter Ermert, 10715 Berlin
email: Hanns-Peter.Ermert at alcatel.de / Alcatel SEL AG,ZIT/B/S2
12099 Berlin,Colditzstrasse 34-36,Tel:+49-30-7002-4766/4788