upstart

util: should include filename in errors

Bug #400241 reported by Scott James Remnant (Canonical)
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
upstart
Fix Released
Low
Scott James Remnant (Canonical)
upstart 0.6.1 "Born in the wagon of a travelling show"

Bug Description

Errors printed by things like runlevel, telinit, shutdown, etc. that involve a file like /var/run/utmp should include the filename that caused the error.

E.g.

   runlevel:/var/run/utmp: No such file or directory

Not.

  runlevel: No such file or directory

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

http://bazaar.launchpad.net/~scott/upstart/trunk/revision/1192

Changed in upstart:
status: Triaged → Fix Committed
Scott James Remnant (Canonical) (canonical-scott)
Changed in upstart:
assignee: nobody → Scott James Remnant (scott)
milestone: none → 0.6.1
Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Fixed in Upstart 0.6.1:

0.6.1 2009-07-16 "Born in the wagon of a travelling show"

        * D-Bus 1.2.16 is now required.

        * Updated ptrace() code to handle receiving the trapped stopped
          child _before_ we receive the trapped fork() syscall, which
          seems to be the most common way the race goes when running
          as init. This seems to make "expect fork/daemon" largely work.
          (Bug: #264711)

        * runlevel will now output "unknown" and exit with an error when
          called before the first telinit call. (Bug: #400248)

        * runlevel will prefix error messages with the utmp filename being
          used. (Bug: #400241)

Changed in upstart:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.