LINUX.ORG.RU
ФорумAdmin

SAMBA выдает ошибки


0

0

Здравствуйте!
Помогите пожалуйста разобраться с сообщениями SAMBA. 
Ничего не могу понять. Все работает нормально, но ими забит весь лог.
Заранее большое спасибо.

Может ли влиять на эти сообщения то что DNS обслуживает домен just.local, А в SAMBA указан домен JUSTLAN ?

OS Fedora Core 3, Samba 3.20.
-----------------------------------------------------------------
Вот вырезка из /var/log/messages
--------------------------------
Dec  4 12:32:37 fedora smbd[6178]: [2005/12/04 12:32:37, 0] lib/util_sock.c:get_peer_addr(1222)
Dec  4 12:32:37 fedora smbd[6178]:   getpeername failed. Error was Transport endpoint is not connected
Dec  4 12:32:37 fedora smbd[32741]: [2005/12/04 12:32:37, 0] lib/util_sock.c:get_peer_addr(1222)
Dec  4 12:32:37 fedora smbd[32741]:   getpeername failed. Error was Transport endpoint is not connected
Dec  4 12:32:37 fedora smbd[6178]: [2005/12/04 12:32:37, 0] lib/util_sock.c:get_peer_addr(1222)
Dec  4 12:32:37 fedora smbd[6178]:   getpeername failed. Error was Transport endpoint is not connected
Dec  4 12:32:37 fedora smbd[32743]: [2005/12/04 12:32:37, 0] lib/util_sock.c:get_peer_addr(1222)
Dec  4 12:32:37 fedora smbd[32743]:   getpeername failed. Error was Transport endpoint is not connected
Dec  4 12:32:37 fedora smbd[32743]: [2005/12/04 12:32:37, 0] lib/util_sock.c:read_data(526)
Dec  4 12:32:37 fedora smbd[32743]:   read_data: read failure for 4 bytes to client 0.0.0.0. Error = Connection reset by peer
Dec  4 12:32:37 fedora smbd[32741]: [2005/12/04 12:32:37, 0] lib/util_sock.c:read_data(526)
Dec  4 12:32:37 fedora smbd[32741]:   read_data: read failure for 4 bytes to client 0.0.0.0. Error = Connection reset by peer
Dec  4 12:32:37 fedora smbd[6178]: [2005/12/04 12:32:37, 0] lib/util_sock.c:get_peer_addr(1222)
Dec  4 12:32:37 fedora smbd[6178]:   getpeername failed. Error was Transport endpoint is not connected
Dec  4 12:32:37 fedora smbd[32745]: [2005/12/04 12:32:37, 0] lib/util_sock.c:get_peer_addr(1222)
Dec  4 12:32:37 fedora smbd[32745]:   getpeername failed. Error was Transport endpoint is not connected
Dec  4 12:32:37 fedora smbd[6178]: [2005/12/04 12:32:37, 0] lib/util_sock.c:get_peer_addr(1222)
Dec  4 12:32:37 fedora smbd[6178]:   getpeername failed. Error was Transport endpoint is not connected
Dec  4 12:32:37 fedora smbd[32745]: [2005/12/04 12:32:37, 0] lib/util_sock.c:read_data(526)
Dec  4 12:32:37 fedora smbd[32745]:   read_data: read failure for 4 bytes to client 0.0.0.0. Error = Connection reset by peer
Dec  4 12:32:37 fedora smbd[32747]: [2005/12/04 12:32:37, 0] lib/util_sock.c:get_peer_addr(1222)
Dec  4 12:32:37 fedora smbd[32747]:   getpeername failed. Error was Transport endpoint is not connected
Dec  4 12:32:37 fedora smbd[32747]: [2005/12/04 12:32:37, 0] lib/util_sock.c:read_data(526)
Dec  4 12:32:37 fedora smbd[32747]:   read_data: read failure for 4 bytes to client 0.0.0.0. Error = Connection reset by peer
-------------------------------------------------------
Вот мой smb.conf
[global]
        log level = 0;
        workgroup = JUSTLAN
        server string = Fedora Server
        log file = /var/log/samba/%m.log
        security = user
        max log size = 50
        socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
        domain logons = Yes
        os level = 85
        preferred master = Yes
        domain master = Yes
        dns proxy = No
        wins support = Yes
        load printers = No
        show add printer wizard = No
        use sendfile = no

[homes]
   comment = Home Directories
   browseable = no
   writable = yes

[public]
   comment = Public Stuff
   path = /home/public
   public = yes
   read only = yes
anonymous

Подскажите кто нибудь. Очень надо, так и big HDD не хватит...

anonymous
()
Вы не можете добавлять комментарии в эту тему. Тема перемещена в архив.