similar to: 2.2.8a with kernel-2.4.22 has kernel oplock problems (NOT Failed to setup RT_SIGNAL_LEASE handler)

Hi @all, I have many messages in the log file with this version: [2006/05/25 15:25:42, 0] smbd/oplock_linux.c:linux_init_kernel_oplocks(247) Failed to setup RT_SIGNAL_LEASE handler [2006/05/25 15:25:42, 0] smbd/notify_kernel.c:kernel_notify_init(224) Failed to setup RT_SIGNAL_NOTIFY handler [2006/05/25 15:25:49, 0] smbd/oplock_linux.c:linux_init_kernel_oplocks(247) Failed to setup

hi, my smbd.log file is full of such messages: ----------------------------- [2003/05/09 09:35:42, 0] smbd/oplock_linux.c:linux_init_kernel_oplocks(287) Failed to setup RT_SIGNAL_LEASE handler [2003/05/09 09:37:27, 0] smbd/oplock_linux.c:linux_init_kernel_oplocks(287) Failed to setup RT_SIGNAL_LEASE handler ----------------------------- on redhat9 with kernel-2.4.20-9 and

This is part of the log and strace output from samba 3.0.9 running on kernel 2.4.27. The output from samba 3.0.8 on kernel 2.6.9 looked somewhat similar... I haven't seen much on the list or ancilliary documentation recently, other than "it is fixed for samba > 3.0"... Could someone please shed some light on this? Syslog entries: Nov 22 22:25:48 toshiba smbd[32209]:

RH9.0 / samba-2.2.7a-8.9.0 / Linux pegasus.houtsma.net 2.4.20-9 #1 Wed Apr 2 13:42:50 EST 2003 i686 i686 i386 GNU/Linux The syslog shows the following messages: [2003/04/13 04:02:36, 0] smbd/server.c:open_sockets(238) Got SIGHUP [2003/04/13 16:13:52, 0] smbd/oplock_linux.c:linux_init_kernel_oplocks(287) Failed to setup RT_SIGNAL_LEASE handler [2003/04/13 23:14:06, 0]

I'm running Slackware 9.0 with a vanilla Linux kernel 2.4.25. Due to the announced EOL for 2.2.x, I'm trying to migrate our Samba hosts to version 3.0.5. These Samba hosts serve shares mounted off a seperate NFS fileserver. All is going well, except I've started getting the following messages in the smbd logs: ---- Start of snippet ---- [2004/08/11 09:59:30, 0]

Thomas Bork wrote: > [2006/05/25 15:25:42, 0] smbd/oplock_linux.c:linux_init_kernel_oplocks(247) > Failed to setup RT_SIGNAL_LEASE handler Switched back to 3.0.21c. Ouch, access to shares is not granted anymore :( The client is confused and thinks the samba server is an domain controller!: Auf \\Deveis\public kann nicht zugegriffen werden. Sie haben eventuell keine Berechtigung,

(Samba 3.0.21c / kernel 2.4.27 / Debian Sarge) Hello, One of my user open a file (located on a SAMBA server) in its application, and when he tries to save it, he gets a "share violation" error. (other people have this problem too). This error happens since I upgraded the SAMBA server from 3.0.14a to 3.0.21c. smbstatus for this file: 32613 DENY_WRITE 0x20089 RDONLY

I just upgraded to -test47 from 0.99.11-test4, and am getting a bunch of these messages in the logfile: dovecot: Oct 14 07:30:21 Info: imap-login: Login: andrew [64.36.1.74] dovecot: Oct 14 07:30:22 Error: IMAP(andrew): sigaction(SIGRTMIN) failed: Invalid argument dovecot: Oct 14 07:30:22 Error: IMAP(andrew): fcntl(F_SETSIG) failed: Invalid argument dovecot: Oct 14 07:30:22 Error: IMAP(andrew):

I'm upgrading to a RH 9 box and using the version of Samba that comes with RH 9. I notice this error message in the smbd.log file; [2003/11/21 21:15:19, 0] smbd/oplock_linux.c:linux_init_kernel_oplocks(287) Failed to setup RT_SIGNAL_LEASE handler It seems to effect the "domain admin group" parameter. In previous version of RH (7.3) and Samba (2.2.7-3.7.3), I'm able to

Hi all, I just downloaded the most recent 2.2.0alpha2 from samba.org and am trying to compile it on a Sun Ultra 5 running Solaris 8. I'm getting the following error when smbd is being linked: Compiling smbd/noquotas.c Compiling smbd/oplock.c Compiling smbd/oplock_irix.c Compiling smbd/oplock_linux.c Compiling smbd/notify.c Compiling smbd/notify_hash.c Compiling smbd/notify_kernel.c Linking

Hello all, We have an application running over samba share that creates a lot of 0-length files, and eventually throws an error because one of more of the files could not be created or does not appear to be created. At the same time in the samba log there are many messages like [2015/02/02 14:02:05.545710, 0, pid=32169, class=locking]

Okay, we're doing a bit of system revamping at my work since our last file server crashed and burned in a horrible tragic failure (hard disk died). Anyways, we've stepped it up a notch with some nice hardware and the fileserver will be running linux (Redhat 9.0 currently). Anyways, I'm currently running into an issue. (I'm using samba 2.2.7a-8.9.0 for reference). Anyways,

I'm trying to setup a printer using Cups, using cupsaddsmb It uploads the files ok (smbclient ... -c 'mkdir W32X86;put ...;put ...') It adds the driver ok (rpcclient -c 'adddriver "Windows NT X86" "Canon:file1:file2..." (I have verified this worked from server properties in "printers and faxes" of the linux server: the driver "canon" shows

Hello, I'm using the Samba server 3.0.33 that exports volume from a GPFS. The GPFS strongly dislikes unlinking files that are locked (resulting in permission denied) using fcntl F_SETLEASE. It seems that the Samba *sometimes* tries to unlink a file that is oplocked. Why? Is this a bug? Why it does not happen always but only sometimes? I have strace logs showing: Wrong case: 8711

Hello, I am running samba 2.2.7a on Red Hat 9. The clients are running Win2k with SP3 and Office XP with SP2. The Samba server authenticates with a WinNT 4 domain controller. When the users open a Word or Excel document there is a 30sec delay before the file opens. From info gleaned from searches on this subject I have tried turning oplocks off altogether, which resulted in Word and Excel

Hello, We are trying to compile the samba 2.2.0-alpha3 source on a SCO Openserver 5.0.6 server. we ran configure with standard options no visible problems. On running make we get the following error ..... Compiling tdb/spinlock.c Compiling tdb/tdbutil.c Compiling printing/printing.c Compiling printing/nt_printing.c Compiling smbd/noquotas.c Compiling smbd/oplock.c Compiling smbd/oplock_irix.c

We have 2.2.7a running on redhat 9.0 with 256 MB ram. Dual cpus - but only PII 300's. Its not running as a PDC - the PDC is an nt box. The system is set up as our main print server with 60 odd print queues that service a wide variety of printers. Approx 200 odd windows pc's as clients. The print files themselves can be largish with multi-page docs with lots of graphics. What we are

Hi All, Need your help/inputs on what could be the probable cause/how to debug this further. We are using samba-4.0.25 & expose a share that has oplocks enabled & no kernel-oplocks set. We constantly see these messages in samba logs [2015/06/25 03:05:30.593150, 0, pid=1581, class=locking] ../source3/smbd/oplock_linux.c:184(linux_release_kernel_oplock) linux_release_kernel_oplock:

I am trying to build Samba 2.2.12 on Solaris 10 x86 with gcc. I am not able to successfully build it, however. I get a linker error for an undefined symbol VA_COPY. How can I fix this problem? Linking bin/smbd Undefined first referenced symbol in file VA_COPY lib/snprintf.o ld: fatal: Symbol referencing errors. No

I have a reproducible intermittent error large site - "The specified network name is no longer available". This happens when copying large files. Below is part of log level 10 output & strace. Sorry for the long posting. I will probably need to put the loglevel 10 attached to a bugzilla - but thought I would try the lists initially. RHEL4 samba-3.0.25b-1.el4_6.4