I am really having a problem with my netlogon script. It is locking almost
on a daily basis. This did not happen before moving to 2.2.0. Anyone have
any ideas to help me. This is the smbstatus line showing me the lock
24912 DENY_NONE RDONLY EXCLUSIVE+BATCH
/home/samba/netlogon/syslogon.bat Wed May 9 12:11:33 2001
The other thing I noticed is the no other connections at the time are using
24912.
RESEND....
since upgrading my system to samba 2.2.0 I am having a problem with my
logon script getting locked, so that when users log on, they are not
getting the proper drive mappings. I have attached the appropriate chunks
of my smb.conf.
[global]
security = user
status = yes
workgroup = ECSAMBA
netbios name = SAMBA
server string = Linux Samba Server
encrypt passwords = Yes
update encrypted = Yes
min passwd length = 6
passwd program = /usr/bin/passwd %u
passwd chat = *password* %n\n *password* %n\n *successfull*
username map = /etc/smbusers
unix password sync = Yes
log level = 1
log file = /var/samba/logs/log.%m
admin users = root
add user script = /usr/sbin/adduser -n -g machines -c Machine -d
/dev/null -s /bin/false %m$
logon script = syslogon.bat
logon path = \\SAMBA\%U\conf\profile
logon drive = h:
logon home = \\SAMBA\%U
domain logons = Yes
os level = 65
preferred master = True
domain master = True
wins support = Yes
default service = homes
hosts allow = 192.168. 127.
guest account = nobody
share modes = no
show add printer wizard = Yes
printer admin = root
valid users = @users
hide local users = No
time server = yes
[homes]
comment = Home Directories
read only = No
create mask = 0770
directory mask = 0770
browseable = No
guest ok = no
[netlogon]
comment = Network Logon Service
path = /home/samba/netlogon
guest ok = no
locking = No
share modes = No
writeable = no
read only = yes
If I am missing any sections which could be useful, please let me
know. Thanks in advance....
Marc Harding
I am sorry if I did not make it clear. I meant no clients had a connection with that PID. Marc At 01:40 PM 5/10/2001 +0100, Simon Allenby wrote:>Marc, > >24912 is the PID of the client's connection, so no reoccurences of this >number means that this user has no other files open, NOT that no other >clients are trying to access the file. Have you tried setting the netlogon >share to being readonly? > >Simon > >------------------------------------------------------------- >Simon Allenby - IT - Project Telecom >email - simona@projtel.co.uk >Direct line 01636 615200 > > > ------------------------------------------------------------ > This communication is confidential and is intended > only for the person to whom it is addressed. > If you are not that person you are not permitted to > make use of the information and you are requested > to destroy the copy in your possession immediately. > ------------------------------------------------------------
I posted a message about "ghost" locks last week and received no response to it. As a work around, I would assume netlogon is read-only? Turn off locking for the share. You might also have to clear out any existing locks by clearing the database in your locks directory with appropriate cautions. Danny