If a service file in init.d contains an error, running it will generate output like this: sal@imelda bin $ sudo /etc/init.d/audiologger start * ERROR: "/etc/init.d/audiologger" has syntax errors in it; not executing... It would be good to have runscript reveal what line contained the syntax error that caused runscript not to run. Ideally it would also be nice to identify what the nature of the syntax error is.
since init scripts are just glorified bash scripts there isnt much we can do except dump the error bash gave us
fixed in rc-scripts cvs. It looks like this, which should be good enough for debugging purposes: /var/lib/init.d/vixie-cron-4244: line 25: syntax error near unexpected token `}' /var/lib/init.d/vixie-cron-4244: line 25: `}' * ERROR: "./vixie-cron" has syntax errors in it; not executing...
Yes, thats a perfect improvement; That should cut down the time taken to debug this class of error in future.
it's in baselayout-1.10.4, released today
