Bug 112623 - /etc/init.d/lsvpd not returning correct exit codes
Summary: /etc/init.d/lsvpd not returning correct exit codes
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Beta 1
Hardware: Other All
: P5 - None : Normal
Target Milestone: SUSE Linux 10.1
Assignee: Olaf Hering
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 97395
  Show dependency tree / graph
 
Reported: 2005-08-24 07:29 UTC by Martin Mrazik
Modified: 2005-11-07 12:38 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
lsvpd.runlevel-exitcodes.patch (611 bytes, patch)
2005-11-07 12:38 UTC, Olaf Hering 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Mrazik 2005-08-24 07:29:55 UTC 
the 
# /etc/init.d/lsvpd start 
command returns bad exit code if something with /sbin/update-lsvpd-db goes wrong. 

E.i. lsvpd should check the exit code of update-lsvpd-db and then return with
the appropriate exit code. Currently the implementation is such that "lsvpd
start" always exits with 0.
Comment 1 Olaf Hering 2005-08-26 09:28:34 UTC 
have notified the maintainers, the errors in beta3 are due to the not aborted
build. this part is fixed.
Comment 2 Olaf Hering 2005-11-07 12:38:06 UTC 
Created attachment 56581 [details]
lsvpd.runlevel-exitcodes.patch
Comment 3 Olaf Hering 2005-11-07 12:38:41 UTC 
I have added this patch now.