[Bug 328881] Re: init: support logging of job output

[Steve Langasek]

upstart 1.4 has landed in Ubuntu precise.

** Changed in: upstart (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/328881

Title:
  init: support logging of job output

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/328881/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 328881] Re: init: support logging of job output

[James Hunt]

@Ankur: Do you mean the job only starts if you comment out the "console
log"? Have you manually created /var/log/upstart/ ?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/328881

Title:
  init: support logging of job output

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/328881/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 328881] Re: init: support logging of job output

[James Hunt]

...and: http://upstart.ubuntu.com/cookbook/#stanzas-by-category

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/328881

Title:
  init: support logging of job output

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/328881/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 328881] Re: init: support logging of job output

[James Hunt]

Upstart 1.4 introduces "console log". See init(5) and:

  http://upstart.ubuntu.com/cookbook/#console-log

** Changed in: upstart
   Status: Triaged => Fix Released

** Changed in: upstart (Ubuntu)
 Assignee: (unassigned) => James Hunt (jamesodhunt)

** Changed in: upstart (Ubuntu)
   Status: Invalid => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/328881

Title:
  init: support logging of job output

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/328881/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 328881] Re: init: support logging of job output

[James Hunt]

** Changed in: upstart
 Assignee: (unassigned) => James Hunt (jamesodhunt)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/328881

Title:
  init: support logging of job output

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/328881/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 328881] Re: init: support logging of job output

[Peter Funk]

Clint Byrum wrote 11.03.2011 10:05:
> Peter, have you tried piping the output of the executed command to
> logger?
> 
> As in
> 
> exec /usr/sbin/foobard | logger -t foobard

Not yet:  This is a clever idea.  I will try this.
Thank you very much.

Best regards, Peter
-- 
Peter Funk, home: ✉Oldenburger Str.86, D-2 Ganderkesee
mobile:+49-179-640-8878 phone:+49-421-20419-0 
office: ArtCom GmbH, ✉Haferwende 2, D-28357 Bremen, Germany

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/328881

Title:
  init: support logging of job output

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 328881] Re: init: support logging of job output

[Clint Byrum]

On Fri, 2011-03-11 at 07:12 +, Peter Funk wrote:
> This is a question from a third party software developer:  I've to support a 
> legacy application 
> package which used to add an entry to /etc/inittab on traditional Unix/Linux 
> systems to 
> start (and respawn) a certain demon.
>   
> When Ubuntu moved to upstart I added a /etc/event.d/-file template.  Later I 
> was forced to
> add an additional *.conf template for /etc/init directory.  My question is: 
> What do I have to put
> into these files to get the stderr  output of this demon into the syslog on 
> all versions of 
> Ubuntu?  (we have a lot of 8.04 LTS still in use in the field; moving slowly 
> to 10.04 LTS)
> For me it is very difficult to figure this out.  Thanks in advance.
> Is installing a backported upstart package a viable option? How much risk is 
> that?
> 

Peter, have you tried piping the output of the executed command to
logger?

As in

exec /usr/sbin/foobard | logger -t foobard

?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/328881

Title:
  init: support logging of job output

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 328881] Re: init: support logging of job output

[Peter Funk]

This is a question from a third party software developer:  I've to support a 
legacy application 
package which used to add an entry to /etc/inittab on traditional Unix/Linux 
systems to 
start (and respawn) a certain demon.
  
When Ubuntu moved to upstart I added a /etc/event.d/-file template.  Later I 
was forced to
add an additional *.conf template for /etc/init directory.  My question is: 
What do I have to put
into these files to get the stderr  output of this demon into the syslog on all 
versions of 
Ubuntu?  (we have a lot of 8.04 LTS still in use in the field; moving slowly to 
10.04 LTS)
For me it is very difficult to figure this out.  Thanks in advance.
Is installing a backported upstart package a viable option? How much risk is 
that?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/328881

Title:
  init: support logging of job output

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 328881] Re: init: support logging of job output

[Launchpad Bug Tracker]

** Branch linked: lp:~beehock/upstart/upstart.fix-328881

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/328881

Title:
  init: support logging of job output

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 328881] Re: init: support logging of job output

[Scott James Remnant]

For sanity's sake, I'm closing the Ubuntu tasks for upstream Upstart
bugs.  I've experimented with having both, but it is just making bugs
hard to find now.  Will use the policy whereby bugs on the Ubuntu
package exist in the Ubuntu packaging or patches only, any bugs in the
Upstart code are Upstream bugs.

** Changed in: upstart (Ubuntu)
   Status: Triaged => Invalid

-- 
init: support logging of job output
https://bugs.launchpad.net/bugs/328881
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 328881] Re: init: support logging of job output

[Austriaco]

> The way to fix that is for another developer (e.g. a community one) to
> pick it up.


I'm so annoyed of not having boot logging that I might give it a shot at doing 
some C programming myself, but after "bzr branch lp:upstar", i didn't know 
where to start hacking :-). That might mean I'm not the proper person to 
attempt this, however if anyone can point out where I can start losing my time 
in the source code, I might get a little encouraged and try again :-)

One idea I had, for instance: I see that boot messages are sent to tty8,
so my first idea would be to look at the code that does that and add
functionality there to redirect a copy of this output to a file in
/var/log/ or something like that. Maybe I'm completely clueless? Any
pointers

-- 
init: support logging of job output
https://bugs.launchpad.net/bugs/328881
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 328881] Re: init: support logging of job output

[Scott James Remnant]

On Fri, 2009-11-27 at 12:56 +, Jarl wrote:

> Scott James Remnant wrote in comment 19:
> > What makes you think that this isn't getting attention? 
> > Clearly the bug is open and not simply closed.
> > Clearly a developer is subscribed to it (hi!)
> 
> Are you also asigned the bug, if so, could you please update the
> assigned to field.
> 
I am not assigned to the bug - I tend to prefer not to mark bugs that
I'm not actively working on as assigned to me, because it discourages
anybody else from picking it up.

> > Fixing boot logging is on my TODO list, but it's about item 246 right
> now and probably in the karmic+2 timeframe.
> 
> That's sad.
> 
The way to fix that is for another developer (e.g. a community one) to
pick it up.

Scott
-- 
Have you ever, ever felt like this?
Had strange things happen?  Are you going round the twist?

-- 
init: support logging of job output
https://bugs.launchpad.net/bugs/328881
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 328881] Re: init: support logging of job output

[Jarl]

Scott James Remnant wrote in comment 19:
> What makes you think that this isn't getting attention? 
> Clearly the bug is open and not simply closed.
> Clearly a developer is subscribed to it (hi!)

Are you also asigned the bug, if so, could you please update the
assigned to field.

> Fixing boot logging is on my TODO list, but it's about item 246 right
now and probably in the karmic+2 timeframe.

That's sad.

-- 
init: support logging of job output
https://bugs.launchpad.net/bugs/328881
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 328881] Re: init: support logging of job output

[Scott James Remnant]

Note that bootlogd is now in the Ubuntu sysvinit-utils package, so the
brave can have a go at running that.  I'm still convinced it won't work
though ;-) but if you can make it work, please do document it for
others.

** Also affects: upstart (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: upstart (Ubuntu)
   Importance: Undecided => Medium

** Changed in: upstart (Ubuntu)
   Status: New => Triaged

-- 
init: support logging of job output
https://bugs.launchpad.net/bugs/328881
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs