initctl: debugging start should show commands run

There are no "log-priority" or "--debug" options for "start", I believe you have confused the man page.

There are separate commands to initctl, for example:

  initctl log-priority debug
  initctl start <service>

The first changes Upstart's logging priority, and the second starts the service; you'll see more verbose log messages in the log as a result

"man start" presented me with page initctl(8), I didn't realize my entry to that page. I was mixing the start command with initcl parameters.

I can see more verbose logging (syslog, debug and daemon.log), it looks to me initctl's view to all the services it it handling.

What I would like to see is a debugging session of the script being run when a service is starting. Like putting extra "-v -v -v" or "-x" to the line "#!/bin/sh -e" to the script (or shell process) starting a service to find out where it fails.

Maybe I missed some documentation in this direction?

Seem like a valid request to me, I'll add this as a wishlist to Upstart

Hi,

Not to rush anyone into anything, just to provide a possible solution and also, I don't know the complexity involved in the whole process.

Maybe it could be an idea to generate a script that in turn could be used for debugging in stead of debugging within upstart itself. upstart Collects all the basics from the /etc filesystem (e.g. sourcing of all the various scripts that come into play) to be printed over stdout. People can then debug that script using "-x -v".