search for: allenbi

Hi, Is there a known problem with file locks when Samba restarts? I have several servers happily running Samba on RH Linux, and several hundred clients running M$ Win9x. There are always a large number of open files, and I am currently migrating the data off several NT servers and onto the Samba ones. This has meant changing the smb.conf file on a regular basis. I am restarting Samba using

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

CRAN (and crantastic) updates this week New packages ------------ * bdoc (1.0) Michael Anderson http://crantastic.org/packages/bdoc This package contains a function that will classify DNA barcodes as well as a few test and reference data sets. * bdsmatrix (1.0) Terry Therneau http://crantastic.org/packages/bdsmatrix This is a special case of sparse matrices, used by coxme and

Are you using wins? Try lmhosts for the start? Are all machines on the same subnet? Just a few hints to start with ... Christian > > > I have absolutely no clue what I could do to fix it. The only solution I > can think of, is to downgrade to redhat 6.2. > > Your help would be greatly appreciated. > > Stefan Kaes > > portax.com GmbH > Zielstattstrasse 40, Geb.

to see the logs to check. Andrew Bartlett Samba Build Farm Maintainer -- Andrew Bartlett abartlet@pcug.org.au abartlet@samba.org Return-Path: <gcarter@valinux.com> Delivered-To: samba@samba.org Received: from Eng.Auburn.EDU (dns.eng.auburn.edu [131.204.10.13]) by lists.samba.org (Postfix) with ESMTP id 48F454E77; Tue, 3 Jul 2001 06:56:24 -0700 (PDT) Received: from localhost

<-----------------------------------------------------------------------> Changes to user passwords are captured by a special DLL, which traps and then stores the password changes in encrypted form in a private area. On each synchronization schedule, the synchronization service first examines the SAM file for changes, and then checks this private area for passwords to be synchronized. Once