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
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"
> 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:5
- 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 beware'
> > > or 'you get both pieces' operation.
> >
> >
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/
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
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
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, which
"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
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 an
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 ☁☁☁
--
devel mailing list
devel@lists.fedoraproject.org
https://adm
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 mai
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.
And to establish if it does that, we need to know what the deceive
factor was of choosing rsyslog in the first place over syslog-
On Jul 19, 2013 2:11 PM, "Steve Clark" 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
>>
On Fri, Jul 19, 2013 at 1:28 PM, "Jóhann B. Guðmundsson" 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.
>>
>>
>>
> Per
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 against
On Wed, Jul 17, 2013 at 2:20 PM, "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 pa
On Fri, Jul 19, 2013 at 10:37 AM, Adam Williamson wrote:
> 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
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 d
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
- 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.
>
- 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
- 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.
> >
>
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. Th
- 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 Fedo
- 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?
> >
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 fo
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, regardles
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
larg
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.
--
de
On 18 July 2013 19:26, Nicolas Mailhot 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 spare USB pen
drive
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 extre
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 FUS
On 18 Jul 2013 18:42, "Eric Smith" 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 available on the machine,
On Thu, Jul 18, 2013 at 10:11 AM, James Hogarth 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 in the first place.
On Thu, Jul 18, 2013 at 9:54 AM, "Jóhann B. Guðmundsson"
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 want
to take th
On Thu, 18.07.13 17:11, James Hogarth (james.hoga...@gmail.com) wrote:
> On 18 July 2013 16:51, Eric Smith 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
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 t
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 an
On 18 July 2013 16:51, Eric Smith 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 it seems I
would say
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
https://ad
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 diffic
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 ab
On Thu, Jul 18, 2013 at 1:56 AM, James Hogarth 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 look at
On Thu, Jul 18, 2013 at 9:59 AM, 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. Y
> 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
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.
Lenn
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.
>
>
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 /v
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 b
Once upon a time, "Jóhann B. Guðmundsson" 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 guess depend
> 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 applicati
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 s
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 la
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
> > forev
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 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 thi
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
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 18 July 2013 10:17, Ralf Corsepius 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 the cases c
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 Fedor
> > 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
devel@lists
On Jul 18, 2013 12:22 AM, "James Hogarth" 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
https://admin.fedorapr
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.
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 the pioneer here. ArchLinux
> wen
On 07/17/2013 10:16 PM, Matthew Miller wrote:
On Wed, Jul 17, 2013 at 09:12:46PM +, "Jóhann B. Guðmundsson" wrote:
You do realize I filed for the exact same thing for F18 as is being
proposed here.
I know, at least. And, as I said earlier in a different subthread (I don't
think you replied)
- Original Message -
> On Wed, 17.07.13 21:00, Ding Yi Chen (dc...@redhat.com) wrote:
>
> > > The release notes addition we suggested in the feature page tells you
> > > what to do.
> > >
> > > The feature page also says we'll add /var/log/README explaining the
> > > situation.
> > >
>
- Original Message -
> 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 machin
- Original Message -
> On 07/17/2013 08:55 PM, Chris Adams wrote:
> > Once upon a time, "Jóhann B. Guðmundsson" said:
> >> >Cut that number by half if you like if it somehow makes you feel
> >> >more comfortable but the fact we have around 550 - 600
> >> >service/daemons components in th
- Original Message -
> On Wed, 17.07.13 21:00, Ding Yi Chen (dc...@redhat.com) wrote:
>
> > > If you never want any changes, then Fedora is simply not the
> > > distribution for you. Slackware might be.
> >
> > I want sane changes that does not break my system.
>
> Well, this won't "br
On Thu, Jul 18, 2013 at 12:28:10AM +0200, Lennart Poettering wrote:
> On Wed, 17.07.13 18:18, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
>
> > > > journalctl _COMM= works for me on F19.
> > > >
> > >
> > >
> > > As it does for me, but somewhere it got clipped that what I was
> > >
On Wed, 17.07.13 21:00, Ding Yi Chen (dc...@redhat.com) wrote:
> > The release notes addition we suggested in the feature page tells you
> > what to do.
> >
> > The feature page also says we'll add /var/log/README explaining the
> > situation.
> >
> > It would be useful actually if you raised th
- Original Message -
> 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 the
Once upon a time, Lennart Poettering said:
> So, maybe, instead of dropping the "Provides syslog" thing from
> journald, maybe we should add an explicit "syslog-files" dependency (or
> something named like that) and then make the classic syslog
> implementations provide that and the packages which
On Wed, 17.07.13 17:48, Denys Vlasenko (dvlas...@redhat.com) wrote:
> >> Except ... that would still keep duplicated logs on the FS. Removing
> >> the duplication is the primary reason for wanting to not install
> >> rsyslogd by default.
>
> > This seems like such a specious argument.
>
> Note t
On Wed, 17.07.13 12:24, Matthew Miller (mat...@fedoraproject.org) wrote:
> On Wed, Jul 17, 2013 at 12:10:35PM -0400, Bill Nottingham wrote:
> > I think it's more correct for packages that expect to work on a textual
> > /var/log/messages (or similar) to have a requirement on a meta 'syslog'
> > pa
On Wed, 17.07.13 11:41, Bill Nottingham (nott...@redhat.com) wrote:
> Matthew Miller (mat...@fedoraproject.org) said:
> > 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 /var/log/messages
> >
On Wed, 17.07.13 16:37, M A Young (m.a.yo...@durham.ac.uk) wrote:
> >I used to do something like this with vim ":g/NOISE/d" until I could see the
> >detail I wanted when the alternations for grep would have been tremendously
> >long. With journalctl's built-in filtering capabilities I'm glad I do
On Wed, 17.07.13 17:41, Reindl Harald (h.rei...@thelounge.net) wrote:
>
>
> Am 17.07.2013 17:21, schrieb john.flor...@dart.biz:
> >> From: scl...@netwolves.com
> >
> >> This seems like such a specious argument. Maybe it made sense when
> >> we were talking about disk drives
> >> that were megab
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 disk drives
> >> that were megabyt
On Wed, 17.07.13 18:18, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
> > > journalctl _COMM= works for me on F19.
> > >
> >
> >
> > As it does for me, but somewhere it got clipped that what I was
> > asking/wishing for was a convenient -C option (like ps) to do just this,
> This sur
On Wed, 17.07.13 12:09, john.flor...@dart.biz (john.flor...@dart.biz) wrote:
> > From: nott...@redhat.com
> >
> > 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
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 interpreted
> > languages (e.g., p
On Wed, 17.07.13 18:58, M A Young (m.a.yo...@durham.ac.uk) wrote:
> On Wed, 17 Jul 2013, Eric Smith wrote:
>
> >On Wed, Jul 17, 2013 at 8:39 AM, "Jóhann B. Guðmundsson"
> > wrote:
> >>Allowing editing of log files is a pure security risk...
> >
> >So is giving a sysadmin the root password, but we
On Wed, Jul 17, 2013 at 09:12:46PM +, "Jóhann B. Guðmundsson" wrote:
> You do realize I filed for the exact same thing for F18 as is being
> proposed here.
I know, at least. And, as I said earlier in a different subthread (I don't
think you replied), the rejection didn't seem to me (I wasn't i
On Wed, 17.07.13 15:04, M A Young (m.a.yo...@durham.ac.uk) wrote:
> On Wed, 17 Jul 2013, Lennart Poettering wrote:
>
> >"cat /var/log/messages" becomes "journalctl"
> >"tail -f /var/log/messages" becomes "journalctl -f"
> >"tail -n100 /var/log/messages" becomes "journalctl -n100"
> >"grep foobar
On Wed, Jul 17, 2013 at 4:28 PM, Chris Adams wrote:
> Once upon a time, Billy Crook said:
> > 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?
>
>
Once upon a time, Billy Crook said:
> 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?
While you could probably do something like this with FUSE, it would
On Wed, Jul 17, 2013 at 8:08 AM, Lennart Poettering wrote:
> The journal is not an implementation of syslog, we already have that in
> rsyslog. Also, the feature is about ending the duplicate storage of the
> log messages, so your suggestion is completely against what the feature
> is about.
>
Wh
On 07/17/2013 09:04 PM, Troy Dawson wrote:
I've read though most of the email on this thread, and would just like
to put in my $.02.
I think this "System Wide Change" is 1 to 2 releases too early.
I'm not totally against it. But I live with one foot in RHEL land,
and one foot in Fedora. It
On 07/17/2013 08:55 PM, Chris Adams wrote:
Once upon a time, "Jóhann B. Guðmundsson" said:
>Cut that number by half if you like if it somehow makes you feel
>more comfortable but the fact we have around 550 - 600
>service/daemons components in the distribution and still no policy
>or work being
On 07/15/2013 04:26 PM, Jonathan Masters wrote:
On Jul 15, 2013, at 5:11, Miroslav Suchý wrote:
On 07/15/2013 10:44 AM, Jaroslav Reznik wrote:
= Proposed System Wide Change: No Default Syslog =
https://fedoraproject.org/wiki/Changes/NoDefaultSyslog
Change owner(s): Lennart Poettering ,
Matth
Once upon a time, "Jóhann B. Guðmundsson" said:
> Cut that number by half if you like if it somehow makes you feel
> more comfortable but the fact we have around 550 - 600
> service/daemons components in the distribution and still no policy
> or work being done to properly package stuff that need/
On Wed, Jul 17, 2013 at 01:27:23PM -0700, Adam Williamson wrote:
> FWIW, FHS states[1]:
>
> "The following files, or symbolic links to files, must be in /var/log,
> if the corresponding subsystem is installed:
>
> File Description
> lastlog record of last login of each user
> messages
On 07/17/2013 08:41 PM, Rahul Sundaram wrote:
HI
On Wed, Jul 17, 2013 at 4:32 PM, "Jóhann B. Guðmundsson" wrote:
On 07/17/2013 08:23 PM, Matthew Miller wrote:
Are you suggesting we somehow need to patch all of these to
use the journal
instead of their own ad-hoc l
HI
On Wed, Jul 17, 2013 at 4:32 PM, "Jóhann B. Guðmundsson" wrote:
> On 07/17/2013 08:23 PM, Matthew Miller wrote:
>
>>
>> Are you suggesting we somehow need to patch all of these to use the
>> journal
>> instead of their own ad-hoc log file? Because that is Definitely Out of
>> Scope for this
On 07/17/2013 08:23 PM, Matthew Miller wrote:
On Wed, Jul 17, 2013 at 07:46:01PM +, "Jóhann B. Guðmundsson" wrote:
On Wed, Jul 17, 2013 at 05:42:21PM +, "Jóhann B. Guðmundsson" wrote:
yum whatprovides "/var/log/*" | grep Filename | wc -l
597
About that much
That's not so helpful. M
On Tue, 2013-07-16 at 21:13 -0400, Matthew Miller 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 /var/log/messages
>
> A) If someone is installing a program that expects this file, they
On Wed, Jul 17, 2013 at 07:46:01PM +, "Jóhann B. Guðmundsson" wrote:
> >On Wed, Jul 17, 2013 at 05:42:21PM +, "Jóhann B. Guðmundsson" wrote:
> >>yum whatprovides "/var/log/*" | grep Filename | wc -l
> >>597
> >>About that much
> >That's not so helpful. Most of these are things which pro
Once upon a time, "Jóhann B. Guðmundsson" said:
> On 07/17/2013 07:05 PM, Matthew Miller wrote:
> >On Wed, Jul 17, 2013 at 05:42:21PM +, "Jóhann B. Guðmundsson" wrote:
> >>yum whatprovides "/var/log/*" | grep Filename | wc -l
> >>597
> >>About that much
> >That's not so helpful. Most of th
1 - 100 of 410 matches
Mail list logo
