From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1b) Gecko/20020721 Description of problem: [peterve@limbo-pc init.d]$ ./smb start Starting SMB services: [ OK ] Starting NMB services: [ OK ] touch: creating `/var/lock/subsys/smb': Toegang geweigerd [peterve@limbo-pc init.d]$ ./smb start Starting SMB services: [ OK ] Starting NMB services: [ OK ] touch: creating `/var/lock/subsys/smb': Toegang geweigerd [peterve@limbo-pc init.d]$ ./smb stop Shutting down SMB services: [FAILED] Shutting down NMB services: [FAILED] [peterve@limbo-pc init.d]$ Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. "smb start" as normal user 2. 3. Actual Results: [peterve@limbo-pc init.d]$ ./smb start Starting SMB services: [ OK ] Starting NMB services: [ OK ] touch: creating `/var/lock/subsys/smb': Toegang geweigerd [peterve@limbo-pc init.d]$ ./smb start Starting SMB services: [ OK ] Starting NMB services: [ OK ] touch: creating `/var/lock/subsys/smb': Toegang geweigerd [peterve@limbo-pc init.d]$ ./smb stop Shutting down SMB services: [FAILED] Shutting down NMB services: [FAILED] [peterve@limbo-pc init.d]$ Expected Results: [peterve@limbo-pc init.d]$ ./smb start Starting SMB services: [FAILED] Starting NMB services: [FAILED] touch: creating `/var/lock/subsys/smb': Toegang geweigerd [peterve@limbo-pc init.d]$ ./smb start Starting SMB services: [FAILED] Starting NMB services: [FAILED] touch: creating `/var/lock/subsys/smb': Toegang geweigerd [peterve@limbo-pc init.d]$ ./smb stop Shutting down SMB services: [FAILED] Shutting down NMB services: [FAILED] [peterve@limbo-pc init.d]$ Additional info: Source RPM: samba-2.2.5-6.src.rpm
Samba forks before it attemptes privilages operations, and so it's very hard for the init scripts to pick this up correctly. It's been on my 'I should fix someday' list for a long time. Posting patches often helps get these items off that list ;-) Andrew Bartlett
Fixed in smb.init script (not checking status of the daemons, but by checking if you're have the necesarry access rights. Will need fixing when capabilities get more extensively used, but should work until then) 2.2.5-8