Mark Dixon
2004-Aug-11 09:12 UTC
[Samba] Migrating from 2.2.8a to 3.0.5 / Failed to setup RT_SIGNAL_LEASE handler
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] smbd/oplock_linux.c:linux_init_kernel_oplocks(289) Failed to setup RT_SIGNAL_LEASE handler ---- End of snippet ---- I've not changed anything in my smb.conf file as, according to the Samba Guide chapter 'UPGRADING FROM SAMBA-2.X TO SAMBA-3.0.0', I've not needed to. I've looked at the mailing list archive for the last couple of years and there only appears to be one mention of this problem effecting Samba 3.0.x - without resolution. Any ideas, other than turning kernel oplocks off? Thanks, Mark -- ------------------------------------------------------ Mark Dixon Email : m.dixon@ucl.ac.uk Systems Integration Tel (int): 34371 Information Systems Tel (ext): 020 7679 4371 University College London, UK ------------------------------------------------------
Gerald (Jerry) Carter
2004-Aug-16 12:45 UTC
[Samba] Migrating from 2.2.8a to 3.0.5 / Failed to setup RT_SIGNAL_LEASE handler
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mark Dixon wrote: | 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 ---- | Failed to setup RT_SIGNAL_LEASE handler | ---- End of snippet ---- Best guess is that smbd knows the kernel supports oplocks but the failure is caused by the failure to register the signal handler (perhaps due to the mounted nfs file system). Ther relevant code is : struct kernel_oplocks *linux_init_kernel_oplocks(void) { ~ ... ~ act.sa_handler = NULL; ~ act.sa_sigaction = signal_handler; ~ act.sa_flags = SA_SIGINFO; ~ sigemptyset( &act.sa_mask ); ~ if (sigaction(RT_SIGNAL_LEASE, &act, NULL) != 0) { ~ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ~ DEBUG(0,("Failed to setup RT_SIGNAL_LEASE handler\n")); ~ return NULL; ~ } ~ .... } cheers, jerry - --------------------------------------------------------------------- Alleviating the pain of Windows(tm) ------- http://www.samba.org GnuPG Key ----- http://www.plainjoe.org/gpg_public.asc "If we're adding to the noise, turn off this song"--Switchfoot (2003) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFBIKxnIR7qMdg1EfYRAqIPAJ9jJxQ4VjIvfuI6lLqIl33KH8J8bgCgzOt9 gbpY3KVUrkRa43c2ItRp+c0=NvZs -----END PGP SIGNATURE-----