On 09/22/2014 02:25 PM, Miloslav Trmač wrote:
(stripping systemd-devel)
----- Original Message -----
>Am 22.09.2014 um 14:44 schrieb Jóhann B. Guðmundsson:
> >This is simply untrue as "journalctl -o export" will show you.
>
>where is it in the message?
>the process is "systemd"
>
>how to distinct between user sessions and systemn boot?
>":programname" don't work and ":msg, startswith" don't work
>
>Mar 18 23:01:01 rawhide systemd[577]: Stopped target Default.
>Mar 18 23:01:01 rawhide systemd[577]: Stopping Basic System.
>Mar 18 23:01:01 rawhide systemd[577]: Stopped target Basic System.
>Mar 18 23:01:01 rawhide systemd[577]: Stopping Paths.
In Fedora’s default configuration, in addition to the traditional rsyslog fields, all journal fields are available in rsyslog. Would filtering for $_PID being, or not being, 1, help?
For the journal you always keep all log history in it's original state
since you never know what the users and administrator prefers ( some
like all messages other just want error or critical and there might two
or more administrators administrating the machine etc ) hence you should
always use the powerful built in filtering capability in the journal to
provide you with the exact output when you need it as opposed to be
fiddling with syslog priority or finding and grepping through text files
located somewhere on the filesystem and have to worry about log rotation
( which implimentation is also broken for components in Fedora ).
For example if you want to see just error messages in the journal you
use "journalctl -p 3" or "journalctl -b -p 3" if you want it only from
last boot ( add boot id if you want to from specific boot ) or you add
"journalctl -b -p 3 -u httpd.service" if you want only the error
messages for the apache daemon so fourth or so on.
If I was continuing to contribute to Fedora and I was continuing with my
efforts cleaning up the log implementation in Fedora I would ( still )
be recommending that each service/daemon would provide it's own
rsyslog.d and syslog-ng configuration files which would be packed and
supplied in a separately log sub-package for a component ( and that
sub-package depend on either rsyslog or syslog-ng and or had a virtual
dependency ).
I would recommend that rsyslog and syslog-ng would ship with it's
default configuration tailored for secure remote logging for centralized
logging server ( for audit compliance, etc ) and have local file logging
disabled by default.
I would also recommend that none of the WG's ship rsyslog by default (
since the administrator would have to configure rsyslog or syslog-ng to
point to the centralized logging server so he can just as well install
it the same time ).
But you go ahead and do what you think is best since I was not allowed
to do this ( this and other related daemon/service components would not
have been an issue for me since I had to go through all the components
for the cleanup process I had in place so this would not have been such
an added load for me to do at the same time ).
I suggest at the same time someone decided to fix this, he fixes the
log-rotation implementation in the project in the process ( if I can
recall correctly it was only implemented for 50 to 100 component out of
600 )
JBG
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
