On Thu, Jul 18, 2013 at 12:28:10AM +0200, Lennart Poettering wrote:
> On Wed, 17.07.13 18:18, Zbigniew Jędrzejewski-Szmek (zbyszek@xxxxxxxxx) wrote:
>
> > > > journalctl _COMM=<blah> 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 surely could be done. But maybe it would be better to make
> > 'journalctl /path/to/program' smarter, so that it would look at _COMM when
> > program is not an executable. This way things would work
> > automagically.
>
> I must say, I don't like ambiguities. The thing about /path/to/program
> is that just by looking at the thing we can identify this as file system
> path, because it starts with a slash. comm names otoh are not that
> easily recognizable, there's no specific char they start with.
I mean that the other way around actually: if I say
journalctl /usr/bin/yum-builddep
where yum-buildep is a python script, journalctl would look at the file type
(looking for a #! line or whatever the way to detect that is), and
use _COMM=yum-builddep instead of _EXE=/usr/bin/yum-builddep, because
_EXE won't match anything in this context.
Zbyszek
--
they are not broken. they are refucktored
-- alxchk
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
