Problems with logs in samba 2.2.2: help me please!
Luiz Alfredo Baggiotto
luiz at pucrs.br
Wed Jan 23 11:23:05 GMT 2002
Hello
Thanks a lot for the help. :-)
I read your messages.
> I've want the same functionality as you for samba 2.2.1, but I did not
> yet figure it out. How did you get your samba 2.0.7 to log all the
> user-activities that you've described?
> I'm first of all interested in having a log entry for logon and logoff.
> Do you have any idea?
This is a sample of log.smb of the old version 2.0.7:
=========================
[2002/01/16 15:52:47, 1] smbd/service.c:make_connection(550)
usr_1 (200.17.94.73) connect to service netlogon as user usr_1 (uid=270, gid=100)
(pid 3003)
[2002/01/16 15:52:49, 1] smbd/service.c:make_connection(550)
usr_1 (200.17.94.73) connect to service software as user usr_1 (uid=270, gid=100)
(pid 3003)
[2002/01/16 16:01:59, 1] smbd/service.c:close_cnum(583)
w120863 (200.17.91.141) closed connection to service usr_2
[2002/01/16 16:01:59, 1] smbd/service.c:close_cnum(583)
w120863 (200.17.91.141) closed connection to service software
=========================
Using this information, I was made a script to find the period of users sessions. It´s very
important for us.
> When I was using Samba 2.0.7, the file MACHINE.SID, secrets.tdb and
> smbpasswd were saved in directory /usr/local/samba/private -- it is
> decided your option when compiling.
> When I am using Samba 2.2.2, I use /usr/priate directory, I met the same
> problem as yours ( Luiz Alfredo ...), after I copy those files to new
> folder, it works.
> I am not sure whether it works for you, just try it :)
I was check the directories and my files MACHINE.SID and smbpasswd, in old version
2.0.7, is in /opt/local/samba/private dir. In the new version 2.2.2, I compile with the
option /opt/local/Samba and the files is in /opt/local/Samba/private. There are not file
named secrets.tdb in old structure. Then, unfortunatly, I think the problem is another...
:-(
> Perhaps you can provide us with the OLD 207 smb.conf and the NEW 2.2 smb.conf
> they may contain hints on what is going wrong.
Of course! Here is it:
# Global parameters of samba 2.0.7
[global]
workgroup = DOMAIN
netbios name = SERVER
server string = Server
encrypt passwords = Yes
name resolve order = wins hosts bcast lmhosts
time server = Yes
logon script = script.bat
logon path = \\%N\profiles\%U
logon drive = h:
domain logons = Yes
os level = 34
preferred master = Yes
domain master = Yes
wins server = xxx.xxx.xxx.xxx
panic action = echo
create mask = 0755
hosts allow = yyy.yyy.yyy.
hide dot files = No
utmp = Yes
And
# Global parameters of samba 2.2.2
[global]
workgroup = DOMAIN
netbios name = SERVER
server string = Server
security = DOMAIN
encrypt passwords = Yes
passwd program = /bin/passwd %u
unix password sync = Yes
max log size = 50000
timestamp logs = No
large readwrite = Yes
time server = Yes
domain admin group = @adm
add user script = /usr/sbin/useradd -d /dev/null -g 122 -s /bin/false %u
delete user script = /usr/sbin/userdel %u
logon script = script.bat
logon path = \\%N\profiles\%U
logon drive = h:
domain logons = Yes
os level = 34
domain master = True
wins server = xxx.xxx.xxx.xxx
utmp = Yes
host msdfs = Yes
winbind uid = 50000-60000
winbind gid = 50000-60000
create mask = 0755
hosts allow = yyy.yyy.yyy.
> Also what is your exact question? "I want to see the problem machines IP in
> the logs?" is that it?
No. My problem is that the old log supplies to me the login and logoff of any user, with
the machine used for he (please, see the sample above). Now, I have only the errors in
my log and I haven´t any idea about what causes this errors.
> Have you tried upping debuglevel to 1 or higher?
I tried level 3 and individual logs for machine, but the errors persists and the
information desired don´t appear.
Thanks again
==============================
Administraçao da Rede
FACIN / PUCRS
Ramal 4184
Prédio 30 - Sala 145
More information about the samba
mailing list