In attempting to install Samba on a Slackware implementation with a 400MB ext2fs partition, the configure script refused to proceed because the locking support would create an unsafe implementation of Samba. Has anyone run across this before, and if so, is it an issue with the limitations of Slackware or can I add packages to allow Samba to load? (The objective is to provide domain authentication and print services, not file sharing, so a disk filled to near the usable capacity would not be an issue.) Thanks in advance. Jeffrey A. Wu (mailto:jwu@claritasconsulting.com) Clarit?s, LLC (http://www.claritasconsulting.com)
Hi Jeffrey I'm running Samba 2.2 on Slackware 8, and have had no problems at all. What is the exact message you're getting, and what parameters are you passing to ./configure? Peter. On Mon, 14 Jan 2002, Wu, Jeffrey wrote:> In attempting to install Samba on a Slackware implementation with a > 400MB ext2fs partition, the configure script refused to proceed because > the locking support would create an unsafe implementation of Samba. Has > anyone run across this before, and if so, is it an issue with the > limitations of Slackware or can I add packages to allow Samba to load? > (The objective is to provide domain authentication and print services, > not file sharing, so a disk filled to near the usable capacity would not > be an issue.) > > Thanks in advance. > > Jeffrey A. Wu (mailto:jwu@claritasconsulting.com) > Clarit?s, LLC (http://www.claritasconsulting.com) > > >
Peter: Thanks for the prompt response. I trying to load Samba 2.2.2 onto Zipslack 8, which may be the issue. The end of the configure (with no options) output is as follows: checking whether to support ACLs... no checking whether to build winbind... no, no unix domain socket support on linux-gnu checking configure summary ERROR: No locking available. Running Samba would be unsafe configure: error: summary failure. Aborting config A grep for "lock" in the full output produces the following: checking for sigblock... yes checking for Linux kernel oplocks... no checking for IRIX kernel oplock type definitions... no checking for fcntl locking... no checking for broken (glibc2.1/x86) 64 bit fcntl locking... no checking for 64 bit fcntl locking... no ERROR: No locking available. Running Samba would be unsafe I have sent the full output to you personally, so as not to generate spurious list traffic. Jeffrey -----Original Message----- From: samba-admin@lists.samba.org [mailto:samba-admin@lists.samba.org]On Behalf Of Peter Hicks Sent: Monday, January 14, 2002 10:11 AM To: Wu, Jeffrey Cc: samba@lists.samba.org; cc@poggs.co.uk Subject: Re: Locking prevents install on Slackware Hi Jeffrey I'm running Samba 2.2 on Slackware 8, and have had no problems at all. What is the exact message you're getting, and what parameters are you passing to ./configure? Peter. On Mon, 14 Jan 2002, Wu, Jeffrey wrote:> In attempting to install Samba on a Slackware implementation with a > 400MB ext2fs partition, the configure script refused to proceedbecause> the locking support would create an unsafe implementation of Samba.Has> anyone run across this before, and if so, is it an issue with the > limitations of Slackware or can I add packages to allow Samba to load? > (The objective is to provide domain authentication and print services, > not file sharing, so a disk filled to near the usable capacity wouldnot> be an issue.) > > Thanks in advance. > > Jeffrey A. Wu (mailto:jwu@claritasconsulting.com) > Clarit?s, LLC (http://www.claritasconsulting.com) > > >-- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
On Mon, 14 Jan 2002, Wu, Jeffrey wrote:> Peter: > > Thanks for the prompt response. I trying to load Samba 2.2.2 onto > Zipslack 8, which may be the issue. The end of the configure (with no > options) output is as follows: > checking whether to support ACLs... no > checking whether to build winbind... no, no unix domain socket support > on linux-gnu > checking configure summary > ERROR: No locking available. Running Samba would be unsafe > configure: error: summary failure. Aborting configI think this is because your kernel headers are incomplete (the ones your libc uses anyway). At least that used to be the common reason for this on linux. But you should check what your config.log says and not listen to me. /Urban
Thanks to Peter and Urban for their comments. The configure script ran after installation of a number of development oriented packages and no longer complained about lack of locking support. This also cleared up problems with installation of Apache on a Zipslack version of Slackware 8. I hope this proves helpful to others. However, the make for Samba does not seem to run to completion and locks up the system. The symptom is that any tty session becomes non-responsive for dozens of minutes to hours. Some never regain foreground control and we are forced to reboot the system. Make ran through until it was compiling in the "lib" directory, with the last files being util_str.c, util_sid.c and util_unistr.c. There is plenty of free disk space and I am sure the CPU is racing as I cannot even get a "ps" to return output HOURS after issuing the command at a prompt. Typing into other session will echo characters minutes to hours after they are typed. Does anyone have any sage advice? Thanks in advance. -----Original Message----- From: Urban Widmark [mailto:urban@teststation.com] Sent: Monday, January 14, 2002 3:05 PM To: Wu, Jeffrey Cc: peter.hicks@poggs.co.uk; samba@lists.samba.org; cc@poggs.co.uk Subject: RE: Locking prevents install on Slackware On Mon, 14 Jan 2002, Wu, Jeffrey wrote:> Peter: > > Thanks for the prompt response. I trying to load Samba 2.2.2 onto > Zipslack 8, which may be the issue. The end of the configure (with no > options) output is as follows: > checking whether to support ACLs... no > checking whether to build winbind... no, no unix domain socket support > on linux-gnu > checking configure summary > ERROR: No locking available. Running Samba would be unsafe > configure: error: summary failure. Aborting configI think this is because your kernel headers are incomplete (the ones your libc uses anyway). At least that used to be the common reason for this on linux. But you should check what your config.log says and not listen to me. /Urban