[Touch-packages] [Bug 1702063] Re: systemctl -n option ignores values greater than 10

2017-07-03 Thread Dimitri John Ledkov 
** Changed in: systemd (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1702063

Title:
  systemctl -n option ignores values greater than 10

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  The manpage for systemctl says that -n can be used to specify how many
  journal lines to show.

  It only works for values <= 10, there is no way to make it show more
  than 10 lines. For example 'systemctl -n 100 status SERVICE' shows 10
  lines, not 100. 'journalctl -n 100 -u SERVICE' does work as expected
  though.

  Its confusing if you are not aware of this and can make you miss
  important output from a failed program.

  systemd package version: 229-4ubuntu17
  systemctl version: systemd 229

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1702063/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Touch-packages] [Bug 1702063] Re: systemctl -n option ignores values greater than 10

2017-07-03 Thread Jon Forsberg 
yep that seems to be the reason. if the service is started it only shows
lines relevant to the current instance, if its not started it will show the
requested number of lines. maybe the manpage should include something about
this. it confused me. feel free to mark this as a feature request or close
it. thanks


2017-07-03 20:18 GMT+08:00 Dimitri John Ledkov :

> are there more than 10 lines of logs for the current /instance/ of the
> unit? E.g. has it produced more than 10 lines of output since it was
> started?
>
> For example, I launch a lxd container of xenial, and $ systemctl status
> -n 20 cloud-init -> displays 20 lines of logs.
>
> How long is the journal for that unit since boot? E.g. journalctl -b -u
> SERVICE | wc ?
>
>
> ** Changed in: systemd (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1702063
>
> Title:
>   systemctl -n option ignores values greater than 10
>
> Status in systemd package in Ubuntu:
>   Incomplete
>
> Bug description:
>   The manpage for systemctl says that -n can be used to specify how many
>   journal lines to show.
>
>   It only works for values <= 10, there is no way to make it show more
>   than 10 lines. For example 'systemctl -n 100 status SERVICE' shows 10
>   lines, not 100. 'journalctl -n 100 -u SERVICE' does work as expected
>   though.
>
>   Its confusing if you are not aware of this and can make you miss
>   important output from a failed program.
>
>   systemd package version: 229-4ubuntu17
>   systemctl version: systemd 229
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/
> 1702063/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1702063

Title:
  systemctl -n option ignores values greater than 10

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  The manpage for systemctl says that -n can be used to specify how many
  journal lines to show.

  It only works for values <= 10, there is no way to make it show more
  than 10 lines. For example 'systemctl -n 100 status SERVICE' shows 10
  lines, not 100. 'journalctl -n 100 -u SERVICE' does work as expected
  though.

  Its confusing if you are not aware of this and can make you miss
  important output from a failed program.

  systemd package version: 229-4ubuntu17
  systemctl version: systemd 229

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1702063/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1702063] Re: systemctl -n option ignores values greater than 10

2017-07-03 Thread Dimitri John Ledkov 
are there more than 10 lines of logs for the current /instance/ of the
unit? E.g. has it produced more than 10 lines of output since it was
started?

For example, I launch a lxd container of xenial, and $ systemctl status
-n 20 cloud-init -> displays 20 lines of logs.

How long is the journal for that unit since boot? E.g. journalctl -b -u
SERVICE | wc ?


** Changed in: systemd (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1702063

Title:
  systemctl -n option ignores values greater than 10

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  The manpage for systemctl says that -n can be used to specify how many
  journal lines to show.

  It only works for values <= 10, there is no way to make it show more
  than 10 lines. For example 'systemctl -n 100 status SERVICE' shows 10
  lines, not 100. 'journalctl -n 100 -u SERVICE' does work as expected
  though.

  Its confusing if you are not aware of this and can make you miss
  important output from a failed program.

  systemd package version: 229-4ubuntu17
  systemctl version: systemd 229

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1702063/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp