Bill S
2004-Dec-13 22:32 UTC
[Samba] "No locking available. Running Samba would be unsafe"
Hello Samba folks, A couple years ago I installed Samba 2.2.0 on our HP9000 running hpux 10.20. I am now trying to install it on a customer's HP9000 and am getting the error "No locking available. Running Samba would be unsafe" while executing the configure command. I got that error a couple years ago and resolved it by linking /usr/bin/cc and /opt/ansic/bin/cc but that is not working this time. I also tried linking /usr/bin/cc and /usr/ccs/bin/cc but that did not work either. Any ideas? - Bill
eric roseme
2004-Dec-14 16:27 UTC
[Samba] "No locking available. Running Samba would be unsafe"
1. What version of HP-UX? 2. What version of Samba (or HP CIFS Server)? 3. What is nflocks set to? 4. Do a "testparm | grep lock" and send in the results. Eric Roseme Hewlett-Packard Bill S wrote:> Hello Samba folks, > > A couple years ago I installed Samba 2.2.0 on our HP9000 running hpux > 10.20. > I am now trying to install it on a customer's HP9000 and am getting the > error > "No locking available. Running Samba would be unsafe" while executing the > configure command. I got that error a couple years ago and resolved it by > linking /usr/bin/cc and /opt/ansic/bin/cc but that is not working this time. > I also > tried linking /usr/bin/cc and /usr/ccs/bin/cc but that did not work either. > Any > ideas? > > - Bill
eric roseme
2004-Dec-14 23:43 UTC
[Samba] "No locking available. Running Samba would be unsafe"
Hi Bill, I am not sure if this is your problem, but 2.2 will take about 20 locks per client connection, so you will run out of locks at 10 connections with nflocks set at 200. You will need to bump that up, along with nfiles and nproc. Of course, you should not be on 10.20, or 2.2.0, but I suppose you know that. Eric Roseme Hewlett-Packard Bill S wrote:> Eric, > > Thanks for your response. Here are some answers to your questions. > 1- HPUX 10.20 > 2- Samba 2.2.0 > 3- nflocks = 200 > 4- There is no testparm command. I checked samba's source/bin > directory and the only command there was .cvsignore. On my > system the testparm and other commands, like smbd,nmbd and > smbclient, were in the bin directory. > > - Bill > > -----Original Message----- > From: eric roseme [mailto:eroseme@emonster.rose.hp.com] > Sent: Tuesday, December 14, 2004 8:27 AM > To: bspicuzza@dsbsi.com > Cc: samba@lists.samba.org > Subject: Re: [Samba] "No locking available. Running Samba would be unsafe" > > 1. What version of HP-UX? > 2. What version of Samba (or HP CIFS Server)? > 3. What is nflocks set to? > 4. Do a "testparm | grep lock" and send in the results. > > Eric Roseme > Hewlett-Packard > > Bill S wrote: > >>Hello Samba folks, >> >> A couple years ago I installed Samba 2.2.0 on our HP9000 running >>hpux 10.20. >>I am now trying to install it on a customer's HP9000 and am getting >>the error "No locking available. Running Samba would be unsafe" while >>executing the configure command. I got that error a couple years ago >>and resolved it by linking /usr/bin/cc and /opt/ansic/bin/cc but that >>is not working this time. >>I also >>tried linking /usr/bin/cc and /usr/ccs/bin/cc but that did not work > > either. > >>Any >>ideas? >> >>- Bill > >