> >I'll offer this without asking what your setup is.
Sorry, here's the run down
Linux 2.4.19
all software compiled from source using gcc 2.95.3
glibc 2.2.5
samba 2.2.5
dual P3 500 MHz Intels(Dell Poweredge)
--
To unsubscribe from this list go to the following URL and read the
instructions: h
I'll offer this without asking what your setup is.
In the Global section, add:
oplocks = no
level2 oplocks = no
kernel oplocks = no
Then killall -HUP smbd
Then killall -HUP nmbd
to force Samba to reread the config file.
If you already did this then others will have to help. This fixed that pro
On Mon, Sep 23, 2002 at 06:44:35PM -0400, Jason Valenzuela wrote:
> I am having a SERIOUS problem with our new 2.2.5 server. In fact I will
> probably be forced to move to a Windows 2000 Server platform, as the samba
> server is practically useless. Work on any files on the share cannot be
> d
I am having a SERIOUS problem with our new 2.2.5 server. In fact I will
probably be forced to move to a Windows 2000 Server platform, as the samba
server is practically useless. Work on any files on the share cannot be
done without major risk of losing data. I get these two errors all day:
[2
