#28 initscript standarts
Closed: Fixed None Opened 14 years ago by zmraz.

Please use correct exit codes and status in sssd initscript according to LSB standarts. ( http://intranet.corp.redhat.com/ic/intranet/InitscriptsSpec.html )

Example:
[root@becks sssd]# service sssd start
Starting sssd: [ OK ]
[root@becks sssd]# [sssd] [confdb_init_db] (0): Parse error reading configuration file [/etc/sssd/sssd.conf]
Parsing errors and warnings in file: /etc/sssd/sssd.conf
Warning (5) on line 1: Equal sign is missing.
[sssd] [monitor_process_init] (0): ConfDB initialization has failed [Input/output error]

[root@becks sssd]# echo $?
0
[root@becks sssd]# ps -e | grep sss
[root@becks sssd]#


Sorry for that formatting.

[root@becks sssd]# service sssd start
Starting sssd:                                             [  OK  ]
[root@becks sssd]# [sssd] [confdb_init_db] (0): Parse error reading configuration file [/etc/sssd/sssd.conf]
Parsing errors and warnings in file: /etc/sssd/sssd.conf
Warning (5) on line 1: Equal sign is missing.
[sssd] [monitor_process_init] (0): ConfDB initialization has failed [Input/output error]

[root@becks sssd]# echo $?
0
[root@becks sssd]# ps -e | grep sss
[root@becks sssd]#

Jakub, please take a look at this.

owner: somebody => jhrozek

The initscript issue was fixed in r3624d766f6098b998a6b60f89285f18faaf8dc61 but also this bug revealed more serious bugs concerning startup and daemonization (for instance r9df9359312ebb29e0a9b5c6db0cb0a195194f49e and rb348e98e47d3ef287fed4d2e272bbf08540e0295)

So thanks for the bug report!

resolution: => fixed
status: new => closed

Fields changed

rhbz: => 0

Metadata Update from @zmraz:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.0

7 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/1070

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata