[Wrapper-user] Exit codes/LSB compliance of Linux wrapper start script

[<chr...@ic...>]

Hi, 

while connecting the Linux wrapper start scripts to OCF resource agents 
for (optional) HA deployment of our application, I noticed that the exit 
codes to neither comply with LSB (Linux standard base) nor OCF specs. I'm 
referring to JSW 3.3.9. 
See 
http://refspecs.freestandards.org/LSB_3.1.1/LSB-Core-generic/LSB-Core-generic/iniscrptact.html
 for LSB. 

- running the script as another user (in check_user() function) drops the 
exit code and always returns 0. 
The exit code should be passed back to the caller. 

- status should exit with 3 if process not running (currently 1) 
- status should exit with 1 if process seems to be crashed (currently 1) 

In addition to straightforward success, the following situations are also 
to be considered successful: 
- running start on a service already running 
- running stop on a service already stopped or not running 
- running restart on a service already stopped or not running 

I wonder how a change of exit codes would affect the monitoring/restarting 
capabilities of JSW? 

regards 
Christian 






InterComponentWare AG:  
Vorstand: Peter Kirschbauer (Vors.), Jörg Stadler / Aufsichtsratsvors.: Prof. Dr. Christof Hettich  
Firmensitz: 69190 Walldorf, Industriestraße 41 / AG Mannheim HRB 351761 / USt.-IdNr.: DE 198388516