Loading ...
Sorry, an error occurred while loading the content.

Samba Logging somewhat screwed up

Expand Messages
  • bloedmann999
    Hi, running Unslung V5.5 and Samba 3.0.24, I was trying to optimize my Samba setup and started samba with the following command (after a kill of both
    Message 1 of 1 , Jun 18, 2007
    • 0 Attachment
      Hi,
      running Unslung V5.5 and Samba 3.0.24, I was trying to optimize my
      Samba setup and started samba with the following command (after a kill
      of both processes:

      echo "Starting nmbd:"
      /opt/sbin/nmbd -D --configfile=/opt/etc/samba/smb.conf
      echo "Starting smbd:"
      /opt/sbin/smbd -D --configfile=/opt/etc/samba/smb.conf

      Now, I get in /var/log/samba/ the following files:
      -rw-r--r-- 1 root root 1074 Jun 18 20:48
      log.192.168.123.180
      -rw-r--r-- 1 root root 1608 Jun 18 20:48 log.brian
      -rw-r--r-- 1 root root 13556 Jun 18 21:05 log.nmbd
      -rw-r--r-- 1 root root 15608 Jun 18 13:47 log.nmbd.old
      -rw-r--r-- 1 root root 618 Jun 18 04:11 log.smbd

      which fits to my smb.conf:
      log file = /var/log/samba/log.%m
      log level = 2

      but, in /opt/var/samba/ I also have:
      -rw------- 1 root root 8192 Jun 15 20:21 account_policy.tdb
      -rw-r--r-- 1 root root 40200 Jun 18 04:11 brlock.tdb
      -rw-r--r-- 1 root root 216 Jun 18 20:59 browse.dat
      -rw-r--r-- 1 root root 8192 Jun 18 04:11 connections.tdb
      drwx------ 4 root root 4096 Jun 16 08:48 cores
      -rw-r--r-- 1 root root 696 Jun 15 20:21 gencache.tdb
      -rw------- 1 root root 8192 Jun 15 20:21 group_mapping.tdb
      -rw-r--r-- 1 root root 40200 Jun 18 04:11 locking.tdb
      -rw-r--r-- 1 root root 79386 Jun 18 05:28 log.nmbd
      -rw-r--r-- 1 root root 7572 Jun 18 04:11 log.smbd
      -rw------- 1 root root 696 Jun 18 04:11 messages.tdb
      -rw-r--r-- 1 root root 4 Jun 18 04:11 nmbd.pid
      -rw------- 1 root root 8192 Jun 15 20:21 ntdrivers.tdb
      -rw------- 1 root root 696 Jun 15 20:21 ntforms.tdb
      -rw------- 1 root root 8192 Jun 15 20:21 ntprinters.tdb
      drwxr-xr-x 2 root root 4096 Jun 15 20:21 perfmon
      drwxr-xr-x 2 root root 4096 Jun 15 20:21 printing
      -rw------- 1 root root 8192 Jun 15 20:21 registry.tdb
      -rw-r--r-- 1 root root 696 Jun 18 04:11 sessionid.tdb
      -rw------- 1 root root 8192 Jun 15 20:27 share_info.tdb
      -rw-r--r-- 1 root root 4 Jun 18 04:11 smbd.pid
      -rw-r--r-- 1 root root 395 Jun 18 21:10 wins.dat
      -rw------- 1 root root 8192 Jun 18 04:11 wins.tdb

      So my log.smbd and log.nmbd exist twice, and are always newly created,
      and both are used. It looks like as soon as anything is written by
      loglevel, that it is written to the /opt/var/samba dir, and normal
      messages to /var/log/samba/, despite the log file variable.

      Can anyone confirm that?

      Known bug?

      Cheers Brian
    Your message has been successfully submitted and would be delivered to recipients shortly.