On Fri, 19.07.13 20:12, Miloslav Trmač (m...@volny.cz) wrote:
On Wed, Jul 17, 2013 at 2:20 PM, Jóhann B. Guðmundsson
johan...@gmail.com wrote:
On 07/17/2013 12:05 PM, Richard W.M. Jones wrote:
On Wed, Jul 17, 2013 at 09:21:39AM +, Jóhann B. Guðmundsson wrote:
On 07/17/2013 12:58
On Sun, 2013-07-21 at 20:46 -0400, Ding Yi Chen wrote:
- Original Message -
On Thu, 2013-07-18 at 21:37 -0400, Ding Yi Chen wrote:
Exactly - adding to the minimal install is generally always a supported
operation. Removing from the minimal install is always a 'buyer
Le Jeu 18 juillet 2013 16:08, Lennart Poettering a écrit :
But anyway, I understand you like ISO, and think it is readable. I don't
agree, but we just have to agree to disagree on this one. It might
thrill you though to learn that I just commited a patch by Tomasz that
adds an ISO output
On Thu, 2013-07-18 at 21:37 -0400, Ding Yi Chen wrote:
Exactly - adding to the minimal install is generally always a supported
operation. Removing from the minimal install is always a 'buyer beware'
or 'you get both pieces' operation.
Didn't Jesse Keating said something like we don't
On Fri, Jul 19, 2013 at 10:37 AM, Adam Williamson awill...@redhat.comwrote:
On Thu, 2013-07-18 at 21:37 -0400, Ding Yi Chen wrote:
Exactly - adding to the minimal install is generally always a supported
operation. Removing from the minimal install is always a 'buyer
beware'
or 'you
On Wed, Jul 17, 2013 at 2:20 PM, Jóhann B. Guðmundsson
johan...@gmail.com wrote:
On 07/17/2013 12:05 PM, Richard W.M. Jones wrote:
On Wed, Jul 17, 2013 at 09:21:39AM +, Jóhann B. Guðmundsson wrote:
On 07/17/2013 12:58 AM, Ding Yi Chen wrote:
You still have not addressed the third party
On 07/19/2013 06:12 PM, Miloslav Trmač wrote:
Progress does not that frequently depend on removing older
functionality. Specifically in this case, removing rsyslog does not
make journal in any way better.
Perhaps not that' s a matter of opinion but to we should be able to
compare it
On Fri, Jul 19, 2013 at 1:28 PM, Jóhann B. Guðmundsson johan...@gmail.com
wrote:
On 07/19/2013 06:12 PM, Miloslav Trmač wrote:
Progress does not that frequently depend on removing older
functionality. Specifically in this case, removing rsyslog does not
make journal in any way better.
On Jul 19, 2013 2:11 PM, Steve Clark scl...@netwolves.com wrote:
On 07/19/2013 02:56 PM, Jóhann B. Guðmundsson wrote:
On 07/19/2013 06:45 PM, Billy Crook wrote:
I haven't seen anyone asking to ship two sysloggers.
I perhaps should have been clearer and say two logging systems which
we
On 07/19/2013 07:11 PM, Steve Clark wrote:
This might have merit if the one you want to keep could do everything
it does
plus what the one you want to remove does.
And to establish if it does that, we need to know what the deceive
factor was of choosing rsyslog in the first place over
On 07/19/2013 02:56 PM, Jóhann B. Guðmundsson wrote:
On 07/19/2013 06:45 PM, Billy Crook wrote:
I haven't seen anyone asking to ship two sysloggers.
I perhaps should have been clearer and say two logging systems which
we currently are doing and one of those cannot be disabled or removed so
On 07/19/2013 07:11 PM, Steve Clark wrote:
This might have merit if the one you want to keep could do everything
it does
plus what the one you want to remove does.
If the intent was to obsolete rsyslog then yes that would be relevant
but since it's not, that's not the case.
JBG
--
devel
On Fri, Jul 19, 2013 at 02:16:13PM -0500, Billy Crook wrote:
Well put. This is exactly why NoSyslog is premature.
And that's exactly why it's NoDefaultSyslog, not NoSyslog.
--
Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ mat...@fedoraproject.org
--
devel mailing list
On 07/19/2013 06:45 PM, Billy Crook wrote:
I haven't seen anyone asking to ship two sysloggers.
I perhaps should have been clearer and say two logging systems which
we currently are doing and one of those cannot be disabled or removed so
the logical choice is to remove the one that can and
Jóhann B. Guðmundsson (johan...@gmail.com) said:
On 07/19/2013 07:11 PM, Steve Clark wrote:
This might have merit if the one you want to keep could do
everything it does
plus what the one you want to remove does.
And to establish if it does that, we need to know what the deceive
factor
Hi Lennart,
I suppose someone should mention small flash-disk-only computers.
There traditionally we fling syslog messages to the serial console or a LRU
buffer in RAM (often the dmesg buffer). The point is to avoid I/O on the flash
memory. Syslog daemons tend to do a lot of fsync-ed I/O,
On Sat, Jul 20, 2013 at 08:15:11AM +0930, Glen Turner wrote:
Hi Lennart,
I suppose someone should mention small flash-disk-only computers.
There traditionally we fling syslog messages to the serial console or a LRU
buffer in RAM (often the dmesg buffer). The point is to avoid I/O on the
Billy Crook (billycr...@gmail.com) said:
Perhaps there should be a Least Possible Bootable install for situations
like this. I would agree Syslog should be missing from such an install.
Just not from Default -- Not until journalctl and systemd attain ubiquity..
The installation only has a
On Sat, Jul 20, 2013 at 01:02:00AM +0200, Zbigniew Jędrzejewski-Szmek wrote:
- Is is possible to run journald without writing to disk; that is: to
serial as text, or as binary to a ring buffer which can then by used
by journalctl?
Yes, it's possible to keep journal completely in /run/ by
Oh come on you are really reaching now. The below two points are especially
ridiculous.
1. What if they update the system like this:
Backed up user data/script - Fresh install - Restore user data/script
For that, it won't work.
This is called a fresh install and not an upgrade. In
On Jul 18, 2013 12:22 AM, James Hogarth james.hoga...@gmail.com wrote:
Oh how do you get your logs to read in windows from your lvm/ext4/btrfs
filesystems currently in a disk boot scenario?
Using ext2fsd:
http://www.ext2fsd.com
Eric
--
devel mailing list
devel@lists.fedoraproject.org
Oh how do you get your logs to read in windows from your lvm/ext4/btrfs
filesystems currently in a disk boot scenario?
Using ext2fsd:
http://www.ext2fsd.com
... I'd suggest you read that page and then look at my question and think
real hard...
--
devel mailing list
On 07/18/2013 06:36 AM, Michael Catanzaro wrote:
On Wed, 2013-07-17 at 14:58 +0200, Lennart Poettering wrote:
We ask this constantly on Fedora. Because Fedora is where innovation is
supposed to take place, not where things are stay frozen in carbonite
forever.
(And let's never forget that
On 18 July 2013 10:17, Ralf Corsepius rc040...@freenet.de wrote:
Is this of any importance? May be you should think about the reasons we
are using Fedora and are not using openSUSE.
That said Fedora should draw its own decisions and not try to be an
imitation cult.
Well given that one of
On 07/17/2013 06:49 PM, Jóhann B. Guðmundsson wrote:
On 07/17/2013 03:48 PM, Denys Vlasenko wrote:
Note that the argument comes from the same group of people
who pushed for mounting tmpfs on /run and /tmp.
So you prefer to have a fragile boot code to empty /run and do you want to be
On 07/18/2013 12:40 AM, Lennart Poettering wrote:
On Wed, 17.07.13 17:50, Denys Vlasenko (dvlas...@redhat.com) wrote:
On 07/17/2013 05:21 PM, john.flor...@dart.biz wrote:
From: scl...@netwolves.com
This seems like such a specious argument. Maybe it made sense when
we were talking about
On Wed, 17.07.13 22:08, Ding Yi Chen (dc...@redhat.com) wrote:
Well, this won't break systems as the change is only for new
installations. Existing systems will stay exactly as they are, rsyslog
stays installed, and will work as always.
1. What if they update the system like this:
On Wed, 17.07.13 22:35, Ding Yi Chen (dc...@redhat.com) wrote:
This should be simpler than forcing those stubborn mind (such as me) to
change,
No?
We don't force anyone. You can just install rsyslog and you have
everything as you love it.
Lennart
--
Lennart Poettering - Red Hat, Inc.
--
On Wed, 17.07.13 23:36, Michael Catanzaro (mike.catanz...@gmail.com) wrote:
On Wed, 2013-07-17 at 14:58 +0200, Lennart Poettering wrote:
We ask this constantly on Fedora. Because Fedora is where innovation is
supposed to take place, not where things are stay frozen in carbonite
forever.
On Thu, 2013-07-18 at 14:17 +0200, Lennart Poettering wrote:
I believe openSUSE 12.3 does not install syslog anymore either. (I
think
they decided they did not want to log everything twice? :) Fedora's
following this time.
Hm OK. They definitely dropped it from the default install late
Le Mar 16 juillet 2013 18:42, Lennart Poettering a écrit :
On Tue, 16.07.13 18:09, Till Maas (opensou...@till.name) wrote:
On Tue, Jul 16, 2013 at 01:43:04PM +0200, Lennart Poettering wrote:
On Tue, 16.07.13 09:42, Till Maas (opensou...@till.name) wrote:
journalctl only supports local
From: mzerq...@0pointer.de
On Wed, 17.07.13 11:48, Bill Nottingham (nott...@redhat.com) wrote:
john.flor...@dart.biz (john.flor...@dart.biz) said:
You can provide binary path (_EXE=) by ”journalctl
/usr/sbin/sshd”.
Yes, but that's of little help with applications using
Once upon a time, Jóhann B. Guðmundsson johan...@gmail.com said:
Currently we are shipping around 550 - 600 components that ship
services/daemons most but probably not all can use syslog but may
not be configured to do so which may or may not be affect by the act
of changing to binary logger I
On 07/17/2013 03:35 PM, Chuck Anderson wrote:
On Wed, Jul 17, 2013 at 03:30:20PM +0200, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Jul 17, 2013 at 08:56:45AM -0400, Chuck Anderson wrote:
Is there a way to read binary journals from non-Linux OSes?
Compiling journalctl on UINXy OSes should not
On 07/18/2013 01:30 PM, Chris Adams wrote:
However, as I've said repeatedly, your yum whatprovides check is flat
wrong, and so is your repeated 550-600 components claim. If you look at
the number of packages that provide something in /var/log (rather than
your bogus number of entries under
On Thu, 18.07.13 14:56, Nicolas Mailhot (nicolas.mail...@laposte.net) wrote:
In the default output we stay true to the formatting that has been used
in /var/log/messages since always.
We currently do not use the ISO date format anywhere, it's not really
readable, I think.
It's not
On 07/18/2013 08:09 AM, Lennart Poettering wrote:
On Wed, 17.07.13 22:35, Ding Yi Chen (dc...@redhat.com) wrote:
This should be simpler than forcing those stubborn mind (such as me) to change,
No?
We don't force anyone. You can just install rsyslog and you have
everything as you love it.
From: scl...@netwolves.com
On 07/18/2013 08:09 AM, Lennart Poettering wrote:
On Wed, 17.07.13 22:35, Ding Yi Chen (dc...@redhat.com) wrote:
This should be simpler than forcing those stubborn mind (such as me)to
change,
No?
We don't force anyone. You can just install rsyslog and you
On Thu, Jul 18, 2013 at 9:59 AM, Steve Clark scl...@netwolves.com wrote:
On 07/18/2013 08:09 AM, Lennart Poettering wrote:
On Wed, 17.07.13 22:35, Ding Yi Chen (dc...@redhat.com) wrote:
This should be simpler than forcing those stubborn mind (such as me) to
change,
No?
We don't
On Thu, Jul 18, 2013 at 1:56 AM, James Hogarth james.hoga...@gmail.com wrote:
Oh how do you get your logs to read in windows from your lvm/ext4/btrfs
filesystems currently in a disk boot scenario?
Using ext2fsd:
http://www.ext2fsd.com
... I'd suggest you read that page and then
On Thu, Jul 18, 2013 at 09:51:32AM -0600, Eric Smith wrote:
What I thought you asked was how to read Linux log files from a
Windows installation, e.g., when Linux fails to boot. In the past
I've been able to do that using ext2fsd without much difficulty. I
used that method when I wasn't able
On 07/18/2013 03:55 PM, Matthew Miller wrote:
On Thu, Jul 18, 2013 at 09:51:32AM -0600, Eric Smith wrote:
What I thought you asked was how to read Linux log files from a
Windows installation, e.g., when Linux fails to boot. In the past
I've been able to do that using ext2fsd without much
On Thu, Jul 18, 2013 at 12:23:33PM +0200, Denys Vlasenko wrote:
What's inappropriate is giving instructions to others what they can,
or can not say.
Even better would be to take this sort of stuff off list asap.
--
Regards,
Olav
--
devel mailing list
devel@lists.fedoraproject.org
On 18 July 2013 16:51, Eric Smith brouh...@fedoraproject.org wrote:
Maybe your question is poorly stated, then.
What I thought you asked was how to read Linux log files from a
Windows installation, e.g., when Linux fails to boot.
This is indeed the question - so given you understood it so
On Thu, Jul 18, 2013 at 03:54:49PM +, Jóhann B. Guðmundsson wrote:
I've been able to do that using ext2fsd without much difficulty. I
used that method when I wasn't able to boot a rescue or live CD, and
the last resort would have been to pull the hard drive from the
machine and use a
On 07/18/2013 04:23 PM, Matthew Miller wrote:
On Thu, Jul 18, 2013 at 03:54:49PM +, Jóhann B. Guðmundsson wrote:
I've been able to do that using ext2fsd without much difficulty. I
used that method when I wasn't able to boot a rescue or live CD, and
the last resort would have been to pull
On Thu, 18.07.13 17:11, James Hogarth (james.hoga...@gmail.com) wrote:
On 18 July 2013 16:51, Eric Smith brouh...@fedoraproject.org wrote:
Maybe your question is poorly stated, then.
What I thought you asked was how to read Linux log files from a
Windows installation, e.g., when
On Thu, Jul 18, 2013 at 9:54 AM, Jóhann B. Guðmundsson
johan...@gmail.com wrote:
Why not read this files on another Fedora host ( or some other distro that
uses systemd )?
What's the reason for this hard dependency on Windows?
Because I was about six hundred miles away from my office, didn't
On Thu, Jul 18, 2013 at 10:11 AM, James Hogarth james.hoga...@gmail.com wrote:
Then you were not using it with a default installed Fedora anyway which has
a default of LVM in place
I don't remember why there wasn't LVM. I don't remember whether I was
the one that installed Linux on that machine
On 18 Jul 2013 18:42, Eric Smith brouh...@fedoraproject.org wrote:
Because I was about six hundred miles away from my office, didn't want
to take the user's computer apart if I could avoid it, and didn't have
a drive dock to hook up the user's drive to my laptop. The user had
Windows
On Wed, Jul 17, 2013 at 04:23:54PM -0500, Billy Crook wrote:
What about a special filesystem mounted at /var/log or filesystem trickery
therein that presents contents similar to what everyone expects, backed out
of journalctl and its storage then?
It's probably straightforward to write a FUSE
Le Jeu 18 juillet 2013 19:56, James Hogarth a écrit :
Without sounding too blunt I hope this does sound like we're entering the
territory of lack of planning on your part does not constitute and
emergency on mine as I have to occasionally remind people at work...
This is such an extreme use
On 18 July 2013 19:26, Nicolas Mailhot nicolas.mail...@laposte.net wrote:
Without sounding too blunt, this is business as usual from a repair
end-user system point of view. I had dozens of such oh btw can you fix my
system experiences
Yeah I've been there in the past ... which is why I have
On Wed, Jul 17, 2013 at 12:31:56PM -0400, Steve Clark wrote:
What about scripts that use /usr/bin/logger? Do messages generated by this
utility
end up in the journal? Or php scripts, or programs using syslog(3).
Yes, everything using standard syslog facilities ends up in the journal.
--
Le Jeu 18 juillet 2013 20:34, James Hogarth a écrit :
I've also been there with dodgy hacky workarounds to deal with strange
stuff - but I wouldn't expect it to weight in an argument for something
like this ...
Why not? In the imperfect world we live in, I'm quite sure they comprise a
large
john.flor...@dart.biz (john.flor...@dart.biz) said:
Or you can de-install rsyslog and have everything as you love it.
Which makes more sense: take a default and modify it via composition ...
or take a default and modify it via decomposition?
I'd always choose the former, regardless of
On Thu, 2013-07-18 at 10:59 -0400, Steve Clark wrote:
On 07/18/2013 08:09 AM, Lennart Poettering wrote:
On Wed, 17.07.13 22:35, Ding Yi Chen (dc...@redhat.com) wrote:
This should be simpler than forcing those stubborn mind (such as me) to
change,
No?
We don't force anyone. You
- Original Message -
john.flor...@dart.biz (john.flor...@dart.biz) said:
Or you can de-install rsyslog and have everything as you love it.
Which makes more sense: take a default and modify it via composition ...
or take a default and modify it via decomposition?
I'd
- Original Message -
On Wed, 2013-07-17 at 14:58 +0200, Lennart Poettering wrote:
We ask this constantly on Fedora. Because Fedora is where innovation is
supposed to take place, not where things are stay frozen in carbonite
forever.
(And let's never forget that Fedora is not
Hi
On Thu, Jul 18, 2013 at 9:43 PM, Ding Yi Chen wrote:
http://doc.opensuse.org/documentation/html/openSUSE/opensuse-tuning/cha.tuning.logfiles.html
Looks like they either still have /var/log/messages,
or their documentation team are lazy.
Be careful about such assumptions. There are
- Original Message -
On Wed, 17.07.13 22:08, Ding Yi Chen (dc...@redhat.com) wrote:
Well, this won't break systems as the change is only for new
installations. Existing systems will stay exactly as they are, rsyslog
stays installed, and will work as always.
1. What if
- Original Message -
On Wed, 17.07.13 22:35, Ding Yi Chen (dc...@redhat.com) wrote:
This should be simpler than forcing those stubborn mind (such as me) to
change,
No?
We don't force anyone. You can just install rsyslog and you have
everything as you love it.
And we don't
- Original Message -
Hi
On Thu, Jul 18, 2013 at 9:43 PM, Ding Yi Chen wrote:
http://doc.opensuse.org/documentation/html/openSUSE/opensuse-tuning/cha.tuning.logfiles.html
Looks like they either still have /var/log/messages,
or their documentation team are lazy.
Be
On Tue, Jul 16, 2013 at 09:26:22PM -0700, Eric Smith wrote:
On Tue, Jul 16, 2013 at 6:13 PM, Matthew Miller
mat...@fedoraproject.org wrote:
On Tue, Jul 16, 2013 at 08:58:40PM -0400, Ding Yi Chen wrote:
You still have not addressed the third party programs and scripts
that monitor
On Tue, Jul 16, 2013 at 11:08 PM, Ding Yi Chen dc...@redhat.com wrote:
Don't tell me that you have not seen people writing multiple platform
scripts like this:
case $OS)
Windows* )
some_windows_scripts
..
Linux* )
grep /var/log/messages
.
For them:
On 07/17/2013 12:58 AM, Ding Yi Chen wrote:
You still have not addressed the third party programs and scripts
that monitor /var/log/messages
We honestly cant keep progress and cleanup in the distribution back out
of fear of breaking some third party programs.
JBG
--
devel mailing list
On Wednesday 17 July 2013 03:20:42 Lennart Poettering wrote:
As mentioned before, if people run programs that require
/var/log/messages they should simply install rsyslog and be done with
it.
That terribly sounds like my way or the high way.
Many people have raised concerns not only about
On Wed, Jul 17, 2013 at 09:21:39AM +, Jóhann B. Guðmundsson wrote:
On 07/17/2013 12:58 AM, Ding Yi Chen wrote:
You still have not addressed the third party programs and scripts
that monitor /var/log/messages
We honestly cant keep progress and cleanup in the distribution back
out of fear
On 07/17/2013 12:05 PM, Richard W.M. Jones wrote:
On Wed, Jul 17, 2013 at 09:21:39AM +, Jóhann B. Guðmundsson wrote:
On 07/17/2013 12:58 AM, Ding Yi Chen wrote:
You still have not addressed the third party programs and scripts
that monitor /var/log/messages
We honestly cant keep progress
On 07/15/2013 11:53 PM, Jóhann B. Guðmundsson wrote:
On 07/15/2013 09:26 PM, Jonathan Masters wrote:
On Jul 15, 2013, at 5:11, Miroslav Suchý msu...@redhat.com wrote:
On 07/15/2013 10:44 AM, Jaroslav Reznik wrote:
= Proposed System Wide Change: No Default Syslog =
On Wed, Jul 17, 2013 at 12:06 PM, Marc Deop i Argemí m...@marcdeop.com wrote:
On Wednesday 17 July 2013 03:20:42 Lennart Poettering wrote:
As mentioned before, if people run programs that require
/var/log/messages they should simply install rsyslog and be done with
it.
That terribly
On 07/17/2013 12:36 PM, Denys Vlasenko wrote:
You guys aren't administrators who are dealing with
these problems every day. You don't feel the pain
you create for other people.
Well my job description for the last 10 years and my pay check says
otherwise so I dont know what you are getting
On Wed, Jul 17, 2013 at 2:36 PM, Denys Vlasenko dvlas...@redhat.com wrote:
On 07/15/2013 11:53 PM, Jóhann B. Guðmundsson wrote:
On 07/15/2013 09:26 PM, Jonathan Masters wrote:
On Jul 15, 2013, at 5:11, Miroslav Suchý msu...@redhat.com wrote:
On 07/15/2013 10:44 AM, Jaroslav Reznik wrote:
=
On 07/17/2013 02:41 PM, Jóhann B. Guðmundsson wrote:
On 07/17/2013 12:36 PM, Denys Vlasenko wrote:
You guys aren't administrators who are dealing with
these problems every day. You don't feel the pain
you create for other people.
Well my job description for the last 10 years
and my pay
On 07/17/2013 12:06 PM, Marc Deop i Argemí wrote:
On Wednesday 17 July 2013 03:20:42 Lennart Poettering wrote:
As mentioned before, if people run programs that require
/var/log/messages they should simply install rsyslog and be done with
it.
That terribly sounds like my way or the
On Wed, Jul 17, 2013 at 02:52:40PM +0200, Ralf Corsepius wrote:
On 07/17/2013 12:06 PM, Marc Deop i Argemí wrote:
On Wednesday 17 July 2013 03:20:42 Lennart Poettering wrote:
As mentioned before, if people run programs that require
/var/log/messages they should simply install rsyslog
Once upon a time, Marc Deop i Argemí m...@marcdeop.com said:
On Wednesday 17 July 2013 03:20:42 Lennart Poettering wrote:
As mentioned before, if people run programs that require
/var/log/messages they should simply install rsyslog and be done with
it.
That terribly sounds like my way or
On 07/17/2013 02:45 PM, drago01 wrote:
instead of administrators simply adding rsyslog or syslog-ng manually
at install time or to their ks snippets.
And this too was answered several times already.
The machine in question may be already borked.
Our support people will need to figure out -
On Wed, 17.07.13 00:08, Ding Yi Chen (dc...@redhat.com) wrote:
that monitor /var/log/messages
A) If someone is installing a program that expects this file, they can also
install rsyslog.
a) From what command they know they need to install rsyslog if they want
yum -y whatprovides
On Wed, Jul 17, 2013 at 2:57 PM, Denys Vlasenko dvlas...@redhat.com wrote:
On 07/17/2013 02:45 PM, drago01 wrote:
instead of administrators simply adding rsyslog or syslog-ng manually
at install time or to their ks snippets.
And this too was answered several times already.
The machine in
On Wed, 17.07.13 01:53, Billy Crook (billycr...@gmail.com) wrote:
On Tue, Jul 16, 2013 at 11:08 PM, Ding Yi Chen dc...@redhat.com wrote:
Don't tell me that you have not seen people writing multiple platform
scripts like this:
case $OS)
Windows* )
some_windows_scripts
On 07/17/2013 03:00 PM, drago01 wrote:
On Wed, Jul 17, 2013 at 2:57 PM, Denys Vlasenko dvlas...@redhat.com wrote:
On 07/17/2013 02:45 PM, drago01 wrote:
instead of administrators simply adding rsyslog or syslog-ng manually
at install time or to their ks snippets.
And this too was answered
On Wed, 17.07.13 07:57, Chris Adams (li...@cmadams.net) wrote:
Once upon a time, Marc Deop i Argemí m...@marcdeop.com said:
On Wednesday 17 July 2013 03:20:42 Lennart Poettering wrote:
As mentioned before, if people run programs that require
/var/log/messages they should simply install
On 07/17/2013 12:50 PM, Denys Vlasenko wrote:
On 07/17/2013 02:41 PM, Jóhann B. Guðmundsson wrote:
On 07/17/2013 12:36 PM, Denys Vlasenko wrote:
You guys aren't administrators who are dealing with
these problems every day. You don't feel the pain
you create for other people.
Well my job
Once upon a time, Lennart Poettering mzerq...@0pointer.de said:
On Wed, 17.07.13 07:57, Chris Adams (li...@cmadams.net) wrote:
Once upon a time, Marc Deop i Argemí m...@marcdeop.com said:
That terribly sounds like my way or the high way.
That is Lennart's standard behavior.
And the
On Wed, Jul 17, 2013 at 03:14:09PM +0200, Lennart Poettering wrote:
On Wed, 17.07.13 07:57, Chris Adams (li...@cmadams.net) wrote:
That terribly sounds like my way or the high way.
That is Lennart's standard behavior.
And the thread just went ugly.
Not sure what the trigger for
On 07/17/2013 01:08 PM, Denys Vlasenko wrote:
Engineer does not know what version of OS that server runs,
what is installed there and how it is configured.
So it needs to be investigated. Quite a typical situation.
Perhaps for you but for us here on top of the world we dont grant root
access
On 07/17/2013 03:21 PM, Jóhann B. Guðmundsson wrote:
On 07/17/2013 01:08 PM, Denys Vlasenko wrote:
Engineer does not know what version of OS that server runs,
what is installed there and how it is configured.
So it needs to be investigated. Quite a typical situation.
Perhaps for you but for
Le Mar 16 juillet 2013 13:54, Lennart Poettering a écrit :
On Tue, 16.07.13 11:49, Nicolas Mailhot (nicolas.mail...@laposte.net)
wrote:
Le Lun 15 juillet 2013 20:09, Till Maas a écrit :
Also it is sad that journalctl does not directly accept ISO 8601
time specifications (I can open a
On Wed, 17.07.13 15:08, Lennart Poettering (mzerq...@0pointer.de) wrote:
How about this idea. Before No Defualt Syslog, systemd needs to
completely replicate all functionality provided by syslog, including
/var/log/messages, by default. Syslog emulation would be an option, and if
people
On 07/17/2013 01:21 PM, Chris Adams wrote:
Once upon a time, Lennart Poettering mzerq...@0pointer.de said:
On Wed, 17.07.13 07:57, Chris Adams (li...@cmadams.net) wrote:
Once upon a time, Marc Deop i Argemí m...@marcdeop.com said:
That terribly sounds like my way or the high way.
That is
On 07/17/2013 02:56 PM, Chuck Anderson wrote:
On Wed, Jul 17, 2013 at 02:52:40PM +0200, Ralf Corsepius wrote:
On 07/17/2013 12:06 PM, Marc Deop i Argemí wrote:
On Wednesday 17 July 2013 03:20:42 Lennart Poettering wrote:
As mentioned before, if people run programs that require
On Wed, Jul 17, 2013 at 08:56:45AM -0400, Chuck Anderson wrote:
On Wed, Jul 17, 2013 at 02:52:40PM +0200, Ralf Corsepius wrote:
On 07/17/2013 12:06 PM, Marc Deop i Argemí wrote:
On Wednesday 17 July 2013 03:20:42 Lennart Poettering wrote:
As mentioned before, if people run programs
On Wed, Jul 17, 2013 at 03:08:59PM +0200, Denys Vlasenko wrote:
Then engineer asks to run tail /var/log/messages.
Customer says: I see
cannot open ‘/var/log/messages’: No such file or directory
message.
And this happens every time in, say, Debian. Great, isn't it?
Engineer asks to run
On Wed, Jul 17, 2013 at 03:30:20PM +0200, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Jul 17, 2013 at 08:56:45AM -0400, Chuck Anderson wrote:
Is there a way to read binary journals from non-Linux OSes?
Compiling journalctl on UINXy OSes should not be too much of a problem.
You'd need dbus =
Engineer does not know what version of OS that server runs,
what is installed there and how it is configured.
So it needs to be investigated. Quite a typical situation.
Perhaps for you but for us here on top of the world we dont grant root
access to people that cant event tell which OS and
On Wed, 17.07.13 14:36, Denys Vlasenko (dvlas...@redhat.com) wrote:
instead of administrators simply adding rsyslog or syslog-ng manually
at install time or to their ks snippets.
And this too was answered several times already.
The machine in question may be already borked.
Our support
On 07/17/2013 03:36 PM, Alexey I. Froloff wrote:
On Wed, Jul 17, 2013 at 03:08:59PM +0200, Denys Vlasenko wrote:
Then engineer asks to run tail /var/log/messages.
Customer says: I see
cannot open ‘/var/log/messages’: No such file or directory
message.
And this happens every time in, say,
On 07/17/2013 08:20 AM, Jóhann B. Guðmundsson wrote:
On 07/17/2013 12:05 PM, Richard W.M. Jones wrote:
On Wed, Jul 17, 2013 at 09:21:39AM +, Jóhann B. Guðmundsson wrote:
On 07/17/2013 12:58 AM, Ding Yi Chen wrote:
You still have not addressed the third party programs and scripts
that
I don't understand why you are on a crusade to remove stuff
which works, even after people conceded to your desire
to have binary logs.
Because that is how progress happens? Of backwards compatibility was held
on forever it would be insane... Eventually things change and as Lennart
pointed
1 - 100 of 406 matches
Mail list logo
