On Thu, 11.10.12 01:48, Lennart Poettering (mzerq...@0pointer.de) wrote:
On Wed, 10.10.12 16:50, Kevin Fenzi (ke...@scrye.com) wrote:
My laptop started acting up last tuesday, I should see whats in the
logs from then
I'd like to run a daily report on my logs
These two are much
On Tue, 09.10.12 23:24, Lennart Poettering (mzerq...@0pointer.de) wrote:
I am not generally against adding time-based rotation, but really, this
is much less of a necessity than other things the journal provides,
which syslog does not: for example per-service rate limits, and
unfakable
On Wed, Oct 17, 2012 at 02:13:35PM +0200, Lennart Poettering wrote:
This is implemented now, but I called it --since= and --until=. I'll
push this into F18 as well, sicne it's actually a minor change only, and
just too useful.
Thanks Lennart. This is great stuff.
--
Matthew Miller ☁☁☁
On Fri, Oct 12, 2012 at 9:29 PM, Bill Nottingham nott...@redhat.com wrote:
Konstantin Ryabitsev (i...@fedoraproject.org) said:
So, in other words, all our existing log analysis tools have to be
modified if they are to be of any use in Fedora 18?
Right, you'll have to port them to understand
On Sat, Oct 13, 2012 at 1:36 AM, Lennart Poettering
mzerq...@0pointer.de wrote:
On Fri, 12.10.12 15:29, Bill Nottingham (nott...@redhat.com) wrote:
And we've got a lot of technology going around. journald - that's
technology. rsyslog - that's technology. libumberlog ceelog - that's
Konstantin Ryabitsev (i...@fedoraproject.org) said:
Not sure I can parse this, but IIUC you are wondering whether logwatch
is compatible with the journal. Not to my knowledge, no. But adding this
should be fairly easy as the output of journalctl is a pixel-perfect
copy of the original
On Fri, 12.10.12 15:29, Bill Nottingham (nott...@redhat.com) wrote:
Heya,
And we've got a lot of technology going around. journald - that's
technology. rsyslog - that's technology. libumberlog ceelog - that's
technology.
THis really makes me wonder where CEE actually belongs in this. Is
On 10/09/2012 09:42 PM, Matthew Miller wrote:
On Tue, Oct 09, 2012 at 11:59:08AM -0400, Simo Sorce wrote:
In current versions .service is implied if no extension is provided:
https://bugs.freedesktop.org/show_bug.cgi?id=39386
About time :-)
Awesome.
And I want to take a moment to thank
On 09/10/12 15:16, Lennart Poettering wrote:
journalctl -D pathtothejournalfiles
Lennart
Can journalctl send the logs via logwatch?
--
Regards,
Frank
Jack of all, fubars
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Lennart Poettering wrote:
On Tue, 09.10.12 09:09, Chris Adams (cmad...@hiwaay.net) wrote:
How do you read this log when the system is not running (e.g.
mounting filesystems of a drive on another system, running from a
rescue image, etc.)?
journalctl -D pathtothejournalfiles
So the
On Wed, Oct 10, 2012 at 09:50:43AM +0200, Björn Persson wrote:
Lennart Poettering wrote:
On Tue, 09.10.12 09:09, Chris Adams (cmad...@hiwaay.net) wrote:
How do you read this log when the system is not running (e.g.
mounting filesystems of a drive on another system, running from a
On Wed, Oct 10, 2012 at 09:54:28AM +0100, Richard W.M. Jones wrote:
On Wed, Oct 10, 2012 at 09:50:43AM +0200, Björn Persson wrote:
Lennart Poettering wrote:
On Tue, 09.10.12 09:09, Chris Adams (cmad...@hiwaay.net) wrote:
How do you read this log when the system is not running (e.g.
Richard W.M. Jones wrote:
I checked out the code, and it does seem as if the format is intended
to be backwards compatible. It uses a set of filesystem-like
compatible and incompatible flags, so presumably a sufficiently
recent journalctl would be able to read any previous version of the
On Wed, Oct 10, 2012 at 12:00:41PM +0200, Björn Persson wrote:
Richard W.M. Jones wrote:
I checked out the code, and it does seem as if the format is intended
to be backwards compatible. It uses a set of filesystem-like
compatible and incompatible flags, so presumably a sufficiently
On 10/10/2012 08:54 AM, Richard W.M. Jones wrote:
This would be essential for libguestfs tools to parse logs out of
guests (we do it now by reading /var/log/messages etc which has all of
the properties you state).
I'm not sure how you are doing this currently but for shutdown guest I
assume
On 10/10/2012 07:54 AM, Frank Murphy wrote:
On 09/10/12 15:16, Lennart Poettering wrote:
journalctl -D pathtothejournalfiles
Lennart
Can journalctl send the logs via logwatch?
As far as I know logwatch has not been patched to parse and use journal.
Try filing an RFE against logwatch
On Wed, Oct 10, 2012 at 10:11:03AM +, Jóhann B. Guðmundsson wrote:
On 10/10/2012 08:54 AM, Richard W.M. Jones wrote:
This would be essential for libguestfs tools to parse logs out of
guests (we do it now by reading /var/log/messages etc which has all of
the properties you state).
I'm
Daniel P. Berrange wrote:
On Wed, Oct 10, 2012 at 12:00:41PM +0200, Björn Persson wrote:
So if my Fedora box won't boot, and I take the disk out and mount it
in a CentOS box, I might not be able to read the log because
journalctl in CentOS might be too old? Not fun.
You can easily just
On Wed, 10.10.12 09:50, Björn Persson (bjorn@rombobjörn.se) wrote:
Lennart Poettering wrote:
On Tue, 09.10.12 09:09, Chris Adams (cmad...@hiwaay.net) wrote:
How do you read this log when the system is not running (e.g.
mounting filesystems of a drive on another system, running from a
On Wed, Oct 10, 2012 at 12:12:26PM +0530, Rahul Sundaram wrote:
About time :-)
Awesome.
And I want to take a moment to thank everyone for listening to these
concerns. I'm optimistic that we can make this all work very nicely.
Is this documented in the relevant man pages as well?
In fact, I
On Wed, Oct 10, 2012 at 12:49 PM, Richard W.M. Jones rjo...@redhat.com wrote:
On Wed, Oct 10, 2012 at 10:11:03AM +, Jóhann B. Guðmundsson wrote:
On 10/10/2012 08:54 AM, Richard W.M. Jones wrote:
This would be essential for libguestfs tools to parse logs out of
guests (we do it now by
On Wed, Oct 10, 2012 at 02:54:13PM +0200, drago01 wrote:
On Wed, Oct 10, 2012 at 12:49 PM, Richard W.M. Jones rjo...@redhat.com
wrote:
On Wed, Oct 10, 2012 at 10:11:03AM +, Jóhann B. Guðmundsson wrote:
On 10/10/2012 08:54 AM, Richard W.M. Jones wrote:
This would be essential for
I apologize, I'm ill and not generally up to providing detailed
responses. So just some sourced facts to counter [1] untruths.
For education on what current syslogs do,
http://blog.gerhards.net/2012/10/main-advantages-of-rsyslog-v7-vs-v5.html
is a possible start and
On Wed, Oct 10, 2012 at 5:05 PM, Miloslav Trmač m...@volny.cz wrote:
On Tue, Oct 9, 2012 at 11:24 PM, Lennart Poettering mzerq...@0pointer.de
wrote:
which syslog does not: for example per-service rate limits,
False. http://www.rsyslog.com/doc/imuxsock.html, There is input rate
limiting
On Wed, Oct 10, 2012 at 6:13 PM, Kay Sievers k...@vrfy.org wrote:
and
unfakable meta-data for log messages.
False: http://www.rsyslog.com/doc/imuxsock.html, trusted syslog
properties are available (and in v7 they can be enabled in the Fedora
configuration by default)
It's well meant, but
On Tue, 09.10.12 22:30, Simo Sorce (s...@redhat.com) wrote:
logrotate has time based policies for very good reasons.
Yeah, because Unix doesn't really allow much else...
Oh come on, stop bashing unix, logrotate could certainly grow a size
checking policy if people felt the need, unix
On Wed, 10 Oct 2012, Lennart Poettering wrote:
On Tue, 09.10.12 22:30, Simo Sorce (s...@redhat.com) wrote:
logrotate has time based policies for very good reasons.
Yeah, because Unix doesn't really allow much else...
Oh come on, stop bashing unix, logrotate could certainly grow a size
On Wed, 10.10.12 17:05, Miloslav Trmač (m...@volny.cz) wrote:
On Tue, Oct 9, 2012 at 11:24 PM, Lennart Poettering
mzerq...@0pointer.de wrote:
I am not generally against adding time-based rotation, but really, this
is much less of a necessity than other things the journal provides,
which
On Wed, 10.10.12 14:16, Seth Vidal (skvi...@fedoraproject.org) wrote:
On Tue, 09.10.12 22:30, Simo Sorce (s...@redhat.com) wrote:
logrotate has time based policies for very good reasons.
Yeah, because Unix doesn't really allow much else...
Oh come on, stop bashing unix, logrotate could
On Wed, 10 Oct 2012, Lennart Poettering wrote:
On Wed, 10.10.12 14:16, Seth Vidal (skvi...@fedoraproject.org) wrote:
On Tue, 09.10.12 22:30, Simo Sorce (s...@redhat.com) wrote:
logrotate has time based policies for very good reasons.
Yeah, because Unix doesn't really allow much else...
On Wed, 10.10.12 08:54, Frank Murphy (frankl...@gmail.com) wrote:
On 09/10/12 15:16, Lennart Poettering wrote:
journalctl -D pathtothejournalfiles
Lennart
Can journalctl send the logs via logwatch?
Not sure I can parse this, but IIUC you are wondering whether logwatch
is compatible
On Wed, 10.10.12 09:54, Richard W.M. Jones (rjo...@redhat.com) wrote:
On Wed, Oct 10, 2012 at 09:50:43AM +0200, Björn Persson wrote:
Lennart Poettering wrote:
On Tue, 09.10.12 09:09, Chris Adams (cmad...@hiwaay.net) wrote:
How do you read this log when the system is not running (e.g.
On Wed, 10.10.12 10:12, Richard W.M. Jones (rjo...@redhat.com) wrote:
On Wed, Oct 10, 2012 at 09:54:28AM +0100, Richard W.M. Jones wrote:
On Wed, Oct 10, 2012 at 09:50:43AM +0200, Björn Persson wrote:
Lennart Poettering wrote:
On Tue, 09.10.12 09:09, Chris Adams (cmad...@hiwaay.net)
On Wed, Oct 10, 2012 at 2:32 PM, Lennart Poettering
mzerq...@0pointer.de wrote:
Can journalctl send the logs via logwatch?
Not sure I can parse this, but IIUC you are wondering whether logwatch
is compatible with the journal. Not to my knowledge, no. But adding this
should be fairly easy as
On Wed, Oct 10, 2012 at 8:37 PM, Konstantin Ryabitsev
i...@fedoraproject.org wrote:
On Wed, Oct 10, 2012 at 2:32 PM, Lennart Poettering
mzerq...@0pointer.de wrote:
Can journalctl send the logs via logwatch?
Not sure I can parse this, but IIUC you are wondering whether logwatch
is compatible
On Wed, Oct 10, 2012 at 02:37:05PM -0400, Konstantin Ryabitsev wrote:
So, in other words, all our existing log analysis tools have to be
modified if they are to be of any use in Fedora 18?
No, not in the even slightest. I don't think that's even up for discussion.
--
Matthew Miller ☁☁☁
On Wed, 10 Oct 2012, Kay Sievers wrote:
So, in other words, all our existing log analysis tools have to be
modified if they are to be of any use in Fedora 18?
What part of Run the syslog daemon like you always did, if you need
syslog files. did you not understand?
Kay,
This is not an
On Wed, Oct 10, 2012 at 2:39 PM, Kay Sievers k...@vrfy.org wrote:
So, in other words, all our existing log analysis tools have to be
modified if they are to be of any use in Fedora 18?
What part of Run the syslog daemon like you always did, if you need
syslog files. did you not understand?
On Wed, Oct 10, 2012 at 8:44 PM, Konstantin Ryabitsev
i...@fedoraproject.org wrote:
On Wed, Oct 10, 2012 at 2:39 PM, Kay Sievers k...@vrfy.org wrote:
So, in other words, all our existing log analysis tools have to be
modified if they are to be of any use in Fedora 18?
What part of Run the
On Wed, Oct 10, 2012 at 02:44:53PM -0400, Konstantin Ryabitsev wrote:
Well, hang on, Kay. My understanding was that we're trying to make
syslog an optional install in Fedora 18 (or is it 19?). If that is the
The suggestion was to propose this as a feature for F19. I think there's
some
On Wed, Oct 10, 2012 at 3:01 PM, Matthew Miller
mat...@fedoraproject.org wrote:
Additionally, it _would_ be cool for log monitoring and analysis tools to
gain journald support, so that users of those tools can take advantage of
all the features Lennart lists. If we could have some of those in
On Wed, 2012-10-10 at 15:01 -0400, Matthew Miller wrote:
On Wed, Oct 10, 2012 at 02:44:53PM -0400, Konstantin Ryabitsev wrote:
case, then even if I require rsyslog for a package, that won't work
unless rsyslog is started and running. So, sysadmin's experience
changes:
Was: Install
On Wed, Oct 10, 2012 at 9:01 PM, Matthew Miller
mat...@fedoraproject.org wrote:
Additionally, it _would_ be cool for log monitoring and analysis tools to
gain journald support, so that users of those tools can take advantage of
all the features Lennart lists. If we could have some of those in
On Tue, Oct 9, 2012 at 5:24 PM, Lennart Poettering mzerq...@0pointer.de wrote:
I am not generally against adding time-based rotation, but really, this
is much less of a necessity than other things the journal provides,
which syslog does not: for example per-service rate limits, and
unfakable
On Wed, Oct 10, 2012 at 9:31 PM, Konstantin Ryabitsev
i...@fedoraproject.org wrote:
On Tue, Oct 9, 2012 at 5:24 PM, Lennart Poettering mzerq...@0pointer.de
wrote:
I am not generally against adding time-based rotation, but really, this
is much less of a necessity than other things the journal
On Wed, 2012-10-10 at 21:44 +0200, Kay Sievers wrote:
On Wed, Oct 10, 2012 at 9:31 PM, Konstantin Ryabitsev
i...@fedoraproject.org wrote:
On Tue, Oct 9, 2012 at 5:24 PM, Lennart Poettering mzerq...@0pointer.de
wrote:
I am not generally against adding time-based rotation, but really, this
On Wed, Oct 10, 2012 at 9:49 PM, Simo Sorce s...@redhat.com wrote:
On Wed, 2012-10-10 at 21:44 +0200, Kay Sievers wrote:
On Wed, Oct 10, 2012 at 9:31 PM, Konstantin Ryabitsev
i...@fedoraproject.org wrote:
On Tue, Oct 9, 2012 at 5:24 PM, Lennart Poettering mzerq...@0pointer.de
wrote:
I am
On Wed, Oct 10, 2012 at 3:44 PM, Kay Sievers k...@vrfy.org wrote:
I think you overestimate how much a sysadmin cares about fake
messages. The thing that's really important to a sysadmin is to make
sure that none of the REAL messages are lost. If someone fakes root
login entries by using
On Wed, Oct 10, 2012 at 03:49:11PM -0400, Simo Sorce wrote:
So make it really better and support time-based rotation. You don't need
to make time-based rotation the default, but you'll make a lot of people
happy to have the option.
Journald will rotate logs when signalled with SIGUSR2. So
On Oct 10, 2012, at 2:02 PM, Kay Sievers wrote:
Syslog is by fact today already an add-on, and not a
required component, it is just installed by default today. I don't use
or run syslog on any of my boxes since quite a while.
How is rsyslog properly disabled?
sockets.target syslog.target
On Wed, 10.10.12 22:19, Tomasz Torcz (to...@pipebreaker.pl) wrote:
On Wed, Oct 10, 2012 at 03:49:11PM -0400, Simo Sorce wrote:
So make it really better and support time-based rotation. You don't need
to make time-based rotation the default, but you'll make a lot of people
happy to have the
On Wed, 10.10.12 14:39, Chris Murphy (li...@colorremedies.com) wrote:
On Oct 10, 2012, at 2:02 PM, Kay Sievers wrote:
Syslog is by fact today already an add-on, and not a
required component, it is just installed by default today. I don't use
or run syslog on any of my boxes since quite
On Oct 10, 2012, at 2:54 PM, Lennart Poettering wrote:
On Wed, 10.10.12 14:39, Chris Murphy (li...@colorremedies.com) wrote:
How is rsyslog properly disabled?
sockets.target syslog.target rsyslog.service all seem related.
systemctl disable rsyslog.service should suffice.
I did that
On Wed, 10 Oct 2012 22:02:26 +0200
Kay Sievers k...@vrfy.org wrote:
On Wed, Oct 10, 2012 at 9:49 PM, Simo Sorce s...@redhat.com wrote:
...snip...
So make it really better and support time-based rotation. You don't
need to make time-based rotation the default, but you'll make a lot
of
Once upon a time, Matthew Miller mat...@fedoraproject.org said:
On Wed, Oct 10, 2012 at 02:44:53PM -0400, Konstantin Ryabitsev wrote:
Well, hang on, Kay. My understanding was that we're trying to make
syslog an optional install in Fedora 18 (or is it 19?). If that is the
The suggestion was
On Wed, 10.10.12 16:50, Kevin Fenzi (ke...@scrye.com) wrote:
My laptop started acting up last tuesday, I should see whats in the
logs from then
I'd like to run a daily report on my logs
These two are much better implemented via explicit time seeks. The
journal APIs support that just fine,
On Thu, Oct 11, 2012 at 01:48:07AM +0200, Lennart Poettering wrote:
My laptop started acting up last tuesday, I should see whats in the
logs from then
I'd like to run a daily report on my logs
These two are much better implemented via explicit time seeks. The
journal APIs support that just
On Wed, 2012-10-10 at 14:37 -0400, Konstantin Ryabitsev wrote:
On Wed, Oct 10, 2012 at 2:32 PM, Lennart Poettering
mzerq...@0pointer.de wrote:
Can journalctl send the logs via logwatch?
Not sure I can parse this, but IIUC you are wondering whether logwatch
is compatible with the journal.
On Thu, 11 Oct 2012 01:48:07 +0200
Lennart Poettering mzerq...@0pointer.de wrote:
These two are much better implemented via explicit time seeks. The
journal APIs support that just fine, journalctl currently
doesn't. However it's trivial to add that based on the lower level
APIs, the only
On Tue, Oct 09, 2012 at 10:58:45AM +, Jóhann B. Guðmundsson wrote:
Like to me rsyslog since the journal is an integrated part of systemd.
Because a huge change like replacing traditional logging with journald needs
to happen as part of a process, not just because another core program adds
On 10/09/2012 11:53 AM, Matthew Miller wrote:
Because a huge change like replacing traditional logging with journald needs
to happen as part of a process, not just because another core program adds
similar-but-different functionality.
Nobody is talking about removing rsyslog or syslog-ng from
From: Jóhann B. Guðmundsson johan...@gmail.com
I personally want to see the documentation releng/fesco has about what
the default minimal set, what the process is to have something
include,excluded from it and why the packages that exist in it are there
in the first place.
I too would
On Tue, 09.10.12 07:53, Matthew Miller (mat...@fedoraproject.org) wrote:
(Not that I actually already wanted this discussion now, but heck...)
On Tue, Oct 09, 2012 at 10:58:45AM +, Jóhann B. Guðmundsson wrote:
Like to me rsyslog since the journal is an integrated part of systemd.
Once upon a time, Lennart Poettering mzerq...@0pointer.de said:
If people want some pixel-perfect copy of the traditional
/var/log/messages, then they should just run journalctl without any
args. It's much better than /var/log/messages:
How do you read this log when the system is not running
On Tue, 09.10.12 09:09, Chris Adams (cmad...@hiwaay.net) wrote:
Once upon a time, Lennart Poettering mzerq...@0pointer.de said:
If people want some pixel-perfect copy of the traditional
/var/log/messages, then they should just run journalctl without any
args. It's much better than
On 09/10/12 15:04, Lennart Poettering wrote:
h) It's much shorter to type: journalctl than less
/var/log/messages. journalctl -n is shorter than tail
/var/log/messages. And journalctl -f is shorter than tail -f
/var/log/messages.
While less helpfully wraps your log lines at the
On 10/09/2012 03:19 PM, Tom Hughes wrote:
While less helpfully wraps your log lines at the edge of your terminal
journalctl unhelpfully truncates them or, if -a is used, makes you use
left/right cursor to scroll back and forth in an attempt to read the
lines. Especially since it fully
Once upon a time, Lennart Poettering mzerq...@0pointer.de said:
On Tue, 09.10.12 09:09, Chris Adams (cmad...@hiwaay.net) wrote:
Once upon a time, Lennart Poettering mzerq...@0pointer.de said:
If people want some pixel-perfect copy of the traditional
/var/log/messages, then they should
Once upon a time, Bryn M. Reeves b...@redhat.com said:
Agreed: I find this irritating too (and the default SYSTEMD_PAGER _is_
less so I'm not sure how it's being run).
Setting PIPE or piping to a pager is even worse - the lines are
truncated at 77 chars regardless of the term width so for
2012/10/9 Lennart Poettering mzerq...@0pointer.de:
On Tue, 09.10.12 09:09, Chris Adams (cmad...@hiwaay.net) wrote:
Once upon a time, Lennart Poettering mzerq...@0pointer.de said:
If people want some pixel-perfect copy of the traditional
/var/log/messages, then they should just run
On Tue, Oct 09, 2012 at 04:04:05PM +0200, Lennart Poettering wrote:
args. It's much better than /var/log/messages:
[many nice things snipped; only responding to ones I have real concerns
about.]
c) it auto-pages if run on a tty
Hmmm. That's not necessarily what people are expecting, but okay.
On 09/10/12 15:35, Bryn M. Reeves wrote:
On 10/09/2012 03:19 PM, Tom Hughes wrote:
More importantly though, what is the equivalent of fgrep xxx
/var/log/messages which is certainly pretty much the most common thing
I do on my logs... I can't see any sort of searching in journalctl?
On 09/10/12 15:35, Bryn M. Reeves wrote:
Agreed: I find this irritating too (and the default SYSTEMD_PAGER _is_
less so I'm not sure how it's being run).
I think I understand this now - because I am sudoing to root in order to
get journalctl to produce output my LESS environment variable is
On Tue, Oct 09, 2012 at 10:45:24AM -0400, Matthew Miller wrote:
c) it auto-pages if run on a tty
Hmmm. That's not necessarily what people are expecting, but okay.
To expand on this: there is a general expectation that non-interactive
console tools will return control to the user immediately.
On Tue, Oct 09, 2012 at 03:45:46PM +0100, Tom Hughes wrote:
Sure, though having just tried that is took 33s to search about a
months worth of logs instead of the 0.05s that greping the last
months messages took ;-)
That's not insignificant (again, goes to sysadmin user experience). Can you
On 10/09/2012 05:00 PM, Matthew Miller wrote:
On Tue, Oct 09, 2012 at 10:45:24AM -0400, Matthew Miller wrote:
c) it auto-pages if run on a tty
Hmmm. That's not necessarily what people are expecting, but okay.
To expand on this: there is a general expectation that non-interactive
console
On Tue, Oct 09, 2012 at 05:24:42PM +0200, Richard Marko wrote:
Compared to the other things I mentioned this is less important (because
hey, sysadmins can learn new ways!), but I wanted to elaborate on where this
is coming from.
+1. For example swapping action and name parameters for
On 10/09/2012 04:45 PM, Tom Hughes wrote:
On 09/10/12 15:35, Bryn M. Reeves wrote:
journalctl | fgrep?
This one is pretty fine by me tbh.
Sure, though having just tried that is took 33s to search about a months
worth of logs instead of the 0.05s that greping the last months messages
took ;-)
On 10/09/2012 03:30 PM, Matthew Miller wrote:
On Tue, Oct 09, 2012 at 05:24:42PM +0200, Richard Marko wrote:
Compared to the other things I mentioned this is less important (because
hey, sysadmins can learn new ways!), but I wanted to elaborate on where this
is coming from.
+1. For example
On 10/09/2012 05:30 PM, Matthew Miller wrote:
Yes. Again, you're not the first person I've heard this from. Likewise,
needing to fill out the .service extension.
In current versions .service is implied if no extension is provided:
https://bugs.freedesktop.org/show_bug.cgi?id=39386
Michal
--
On Tue, 2012-10-09 at 15:38 +, Jóhann B. Guðmundsson wrote:
On 10/09/2012 03:30 PM, Matthew Miller wrote:
On Tue, Oct 09, 2012 at 05:24:42PM +0200, Richard Marko wrote:
Compared to the other things I mentioned this is less important (because
hey, sysadmins can learn new ways!), but I
On Tue, 2012-10-09 at 17:42 +0200, Michal Schmidt wrote:
On 10/09/2012 05:30 PM, Matthew Miller wrote:
Yes. Again, you're not the first person I've heard this from. Likewise,
needing to fill out the .service extension.
In current versions .service is implied if no extension is provided:
On Tue, Oct 09, 2012 at 03:38:42PM +, Jóhann B. Guðmundsson wrote:
Probably changing this is not doable since you have multiple types
of units that can have the same name foo.path foo.target foo.service
foo.timer etc.
But can we tell which the user wants?
As I have set from the get go
On 10/09/2012 03:58 PM, Simo Sorce wrote:
Oh come on, you just use a default when it is missing (.service) and
require it fully formed for the others.
It apparently does that now with [1]
And is included in systemd 188 which is in F18+
Michal will need to comment if this one will be
On Tue, Oct 09, 2012 at 11:59:08AM -0400, Simo Sorce wrote:
In current versions .service is implied if no extension is provided:
https://bugs.freedesktop.org/show_bug.cgi?id=39386
About time :-)
Awesome.
And I want to take a moment to thank everyone for listening to these
concerns. I'm
On 10/09/2012 04:11 PM, Matthew Miller wrote:
Probably changing this is not doable since you have multiple types
of units that can have the same name foo.path foo.target foo.service
foo.timer etc.
But can we tell which the user wants?
But ever since 188 it's defaulted to an unit of type
Am 09.10.2012 17:38, schrieb Jóhann B. Guðmundsson:
On 10/09/2012 03:30 PM, Matthew Miller wrote:
On Tue, Oct 09, 2012 at 05:24:42PM +0200, Richard Marko wrote:
Compared to the other things I mentioned this is less important (because
hey, sysadmins can learn new ways!), but I wanted to
On Tue, Oct 09, 2012 at 04:12:48PM +, Jóhann B. Guðmundsson wrote:
alike to forget all they know of the legacy sysv init stuff and
approach systemd with a fresh mind and as a*new* technology
That's expensive.
No more than for example someone study and learning cloud
Sure, a fine example.
On Tue, 09.10.12 15:19, Tom Hughes (t...@compton.nu) wrote:
On 09/10/12 15:04, Lennart Poettering wrote:
h) It's much shorter to type: journalctl than less
/var/log/messages. journalctl -n is shorter than tail
/var/log/messages. And journalctl -f is shorter than tail -f
On Tue, 09.10.12 15:35, Bryn M. Reeves (b...@redhat.com) wrote:
On 10/09/2012 03:19 PM, Tom Hughes wrote:
While less helpfully wraps your log lines at the edge of your terminal
journalctl unhelpfully truncates them or, if -a is used, makes you use
left/right cursor to scroll back and
On 10/09/2012 04:40 PM, Matthew Miller wrote:
Sure, a fine example. That's an tech-industry-wide disruptive shift.
Companies_are_ spending money on investing in it, because they expect to
get significant returns, savings, and a competitive advantage. Many of the
companies and products springing
On Tue, 09.10.12 09:41, Chris Adams (cmad...@hiwaay.net) wrote:
Once upon a time, Bryn M. Reeves b...@redhat.com said:
Agreed: I find this irritating too (and the default SYSTEMD_PAGER _is_
less so I'm not sure how it's being run).
Setting PIPE or piping to a pager is even worse - the
On Tue, Oct 09, 2012 at 05:19:48PM +, Jóhann B. Guðmundsson wrote:
Out of which of the ca 500 linux distributions which contain wide
variety of init system are they trying to minimize their transition
from?
Okay. Sure, let's just pick two:
Fedora
RHEL
This sample of your makes
On Tue, Oct 09, 2012 at 04:16:16PM +0200, Lennart Poettering wrote:
On Tue, 09.10.12 09:09, Chris Adams (cmad...@hiwaay.net) wrote:
Once upon a time, Lennart Poettering mzerq...@0pointer.de said:
If people want some pixel-perfect copy of the traditional
/var/log/messages, then they
On Tue, 09.10.12 15:45, Tom Hughes (t...@compton.nu) wrote:
On 09/10/12 15:35, Bryn M. Reeves wrote:
On 10/09/2012 03:19 PM, Tom Hughes wrote:
More importantly though, what is the equivalent of fgrep xxx
/var/log/messages which is certainly pretty much the most common thing
I do on my
On Tue, Oct 9, 2012 at 7:30 PM, Richard W.M. Jones rjo...@redhat.com wrote:
On Tue, Oct 09, 2012 at 04:16:16PM +0200, Lennart Poettering wrote:
On Tue, 09.10.12 09:09, Chris Adams (cmad...@hiwaay.net) wrote:
Once upon a time, Lennart Poettering mzerq...@0pointer.de said:
If people want
On Tue, 09.10.12 09:38, Chris Adams (cmad...@hiwaay.net) wrote:
Once upon a time, Lennart Poettering mzerq...@0pointer.de said:
On Tue, 09.10.12 09:09, Chris Adams (cmad...@hiwaay.net) wrote:
Once upon a time, Lennart Poettering mzerq...@0pointer.de said:
If people want some
On Tue, Oct 09, 2012 at 07:34:50PM +0200, drago01 wrote:
On Tue, Oct 9, 2012 at 7:30 PM, Richard W.M. Jones rjo...@redhat.com wrote:
On Tue, Oct 09, 2012 at 04:16:16PM +0200, Lennart Poettering wrote:
On Tue, 09.10.12 09:09, Chris Adams (cmad...@hiwaay.net) wrote:
Once upon a time,
On Tue, 09.10.12 18:37, Richard W.M. Jones (rjo...@redhat.com) wrote:
On Tue, Oct 09, 2012 at 07:34:50PM +0200, drago01 wrote:
On Tue, Oct 9, 2012 at 7:30 PM, Richard W.M. Jones rjo...@redhat.com
wrote:
On Tue, Oct 09, 2012 at 04:16:16PM +0200, Lennart Poettering wrote:
On Tue,
On Tue, Oct 09, 2012 at 07:27:19PM +0200, Lennart Poettering wrote:
That all said, the color and autopaging is disabled automatically if you
pipe the tools to something that is not a tty. You can also enable this
via command line args, and env vars. This is similar to man or git. If
As long as
1 - 100 of 132 matches
Mail list logo
