Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 302124 - Broken init script' config for 3.4.5
Summary: Broken init script' config for 3.4.5
Status: RESOLVED DUPLICATE of bug 302123
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL: http://www.samba.org
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-25 01:59 UTC by Igor Franchuk
Modified: 2010-01-25 06:31 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Igor Franchuk 2010-01-25 01:59:58 UTC
no pid --pidfile

3.4.5 config 

smbd_stop="start-stop-daemon --stop --exec /usr/sbin/smbd"
nmbd_stop="start-stop-daemon --stop --exec /usr/sbin/nmbd"

should be
smbd_stop="start-stop-daemon --stop --exec /usr/sbin/smbd --pidfile /var/run/samba/smbd.pid"

nmbd_stop="start-stop-daemon --stop --exec /usr/sbin/nmbd --pidfile /var/run/samba/nmbd.pid"



Reproducible: Always

Steps to Reproduce:
1./etc/init.d/samba start
2./etc/init.d/samba stop
3.

Actual Results:  
 # /etc/init.d/samba stop
 * samba -> stop: smbd ...                                                                                                                             [ ok ]
 * samba -> stop: nmbd ...                                                                                                                             [ !! ]

Expected Results:  
 # /etc/init.d/samba stop
 * samba -> stop: smbd ...                                                                                                                             [ ok ]
 * samba -> stop: nmbd ...                                                                                                                             [ ok ]
Comment 1 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev 2010-01-25 06:31:08 UTC

*** This bug has been marked as a duplicate of bug 302123 ***