Bug 8405 - init.d scripts does no work
init.d scripts does no work
Status: VERIFIED WORKSFORME
Product: Samba 3.6
Classification: Unclassified
Component: Build environment
3.6.0
x64 Linux
: P5 major
: ---
Assigned To: Lars Müller
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-08-25 15:50 UTC by Thiago Silva
Modified: 2011-08-29 13:55 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thiago Silva 2011-08-25 15:50:53 UTC
After upgrade for version 3.6.0 using packages of opensuse build service the init.d scripts does not work anymore.

The error is in starproc sintax see below:

HOST:~ # /etc/init.d/smb start
Starting Samba SMB daemon startproc: Usage:
        startproc [-f] [+/-<prio>] [-s] [-u uid] [-g gid] [-v] [-l log_file|-q] /full/path/to/program
                                                                      done

although it shows that the start was successful the process is not running

HOST:~ # ps aux |grep smb
root      4080  0.0  0.0   3028   708 pts/2    S+   12:47   0:00 grep smb

Stop, and status option are working fine
Comment 1 Thiago Silva 2011-08-25 16:16:05 UTC
I think i have found the issue, in startproc sintax there a "-W" flag with the PID of daemon, but the "-W" flag is not valid for startproc, i've removed the flag and the init.d scripts are working again.
Comment 2 Björn Jacke 2011-08-26 09:14:43 UTC
which distribution, which samba binary packages?
Comment 3 Björn Jacke 2011-08-26 09:15:59 UTC
ups, sorry, you wrote opensuse buildservice I see :-). Reassigning to Lars as he maintains the suse rpms
Comment 4 Lars Müller 2011-08-26 09:20:34 UTC
We need to know to which openSUSE/ SUSE Linux version this issue applies.

Please clear the needinfo status after you provided the requested information.
Comment 5 Thiago Silva 2011-08-26 19:41:02 UTC
(In reply to comment #4)
> We need to know to which openSUSE/ SUSE Linux version this issue applies.
> 
> Please clear the needinfo status after you provided the requested information.

This issue apply to packages for SLES 10, the server is running service pack 2.
Comment 6 Lars Müller 2011-08-29 13:50:00 UTC
Thanks for closing.  In particular as I had not been able to reproduce the issue on a SUSE Linux Enterprise 10 SP 4 system.

If possible please be so nice and explain what the actual issue was as this might be of help to other users.
Comment 7 Thiago Silva 2011-08-29 13:55:22 UTC
After i have removed the "-W" flag in options for startproc the issue does not occur anymore.

There is no "-W" flag for startproc in SLES10 SP2.