[Gulli] Samba log

[Marco Fontani]

Da:
http://oreilly.com/catalog/samba/chapter/book/ch09_01.html

An effective way to diagnose problems without hampering other users is
to assign different log levels for different machines in [global]
section of the smb.conf file. We can do this by building on the
strategy we presented earlier:

[global]
	log level = 0
	log file = /usr/local/samba/lib/log.%m
	include = /usr/local/samba/lib/smb.conf.%m

These options instruct Samba to use unique configuration and log files
for each client that connects. Now all you have to do is create an
smb.conf file for a specific client machine with a log level = 3 entry
in it (the others will pick up the default log level of 0) and use
that log file to track down the problem.

Similarly, if only particular users are experiencing a problem, and it
travels from machine to machine with them, you can isolate ***logging
to a specific user*** by adding the following to the smb.conf file:

[global]
	log level = 0
	log file = /usr/local/samba/lib/log.%u
	include = /usr/local/samba/lib/smb.conf.%u

Then you can create a unique smb.conf file for each user (e.g.,
/usr/local/samba/lib/smb.conf.tim) files containing the configuration
option log level = 3 and only those users will get more detailed
logging.

Spero sia chiaro:
- in smb.conf aggiungi:
[global]
	log level = 0
	log file = /usr/local/samba/lib/log.%u
	include = /usr/local/samba/lib/smb.conf.%u
- crea un /usr/local/samba/lib/smb.conf.USERNAMEDALOGGARE
piazzaci opzione log level = 3

Dovrebbe andare..
Fintantoche' questi files di configurazione non sono accessibili
all'utente (i.e. l'utente non ha accesso al server samba in altro modo
che tramite la share samba), dovresti pure esser tranquillo del fatto
che l'utente non puo' sapere che in realta' stai loggando ogni suo
movimento su samba su quel server.

Fammi sapere come ti va, che e` un argomento che mi interessa ;)
A presto
-marco-