On Wed, Jul 17, 2013 at 01:39:30PM -0400, john.flor...@dart.biz wrote:
> > From: zbys...@in.waw.pl
> > On Wed, Jul 17, 2013 at 12:09:14PM -0400, 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 applications using interpreted
>
> > > > > languages (e.g., python). I want to match on the name of the
> python
> > > > > program, not python itself.
> > > >
> > > > 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.
>
> That would be suitable too, if not more so. Also, for whatever reason,
> I've noticed that "journalctl blah" is much, much slower than "journalctl
> _EXE=bla". Is that a bug or are they not exactly equivalents?
It only does an extra stat on the file do termine its kind, and then
adds "_EXE=..." match. There shouldn't be any speed difference.
Zbyszek
--
they are not broken. they are refucktored
-- alxchk
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
