Re: logcheck rules for systemd
On 28/08/14 12:37, Ondřej Surý wrote: Hey all, I have started to collect logcheck/ignore.d.server/systemd rules for systemd: https://wiki.debian.org/systemd/logcheck I think it might be a good idea to fine tune the rules before submitting them for inclusion into logcheck default ruleset... Hi Ondřej, You may find it easier to bundle the logcheck rules with systemd itself rather than as part of logcheck-database. Debhelper has a dh_installlogcheck tool that you may find useful. In my opinion, packaging the logcheck rules with the program that generates the log messages makes more sense, as the rules can be more easily kept up to date with the generating program. HTH, Chris -- Chris Boot deb...@bootc.net GPG: 8467 53CB 1921 3142 C56D C918 F5C8 3C05 D9CE ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Re: logcheck rules for systemd
Am 28.08.2014 13:52, schrieb Chris Boot: On 28/08/14 12:37, Ondřej Surý wrote: Hey all, I have started to collect logcheck/ignore.d.server/systemd rules for systemd: https://wiki.debian.org/systemd/logcheck I think it might be a good idea to fine tune the rules before submitting them for inclusion into logcheck default ruleset... Hi Ondřej, You may find it easier to bundle the logcheck rules with systemd itself rather than as part of logcheck-database. Debhelper has a dh_installlogcheck tool that you may find useful. In my opinion, packaging the logcheck rules with the program that generates the log messages makes more sense, as the rules can be more easily kept up to date with the generating program. I'm not sure if anyone in the systemd team is actively using logcheck, I don't. So from my pov I'd prefer if it was maintained by someone who actually does. And do we really want to install those logcheck rules files (conffiles) on everyones system, if only a small percentage of users actually install logcheck. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Re: logcheck rules for systemd
On Thu, Aug 28, 2014, at 13:52, Chris Boot wrote: On 28/08/14 12:37, Ondřej Surý wrote: Hey all, I have started to collect logcheck/ignore.d.server/systemd rules for systemd: https://wiki.debian.org/systemd/logcheck I think it might be a good idea to fine tune the rules before submitting them for inclusion into logcheck default ruleset... Hi Ondřej, You may find it easier to bundle the logcheck rules with systemd itself rather than as part of logcheck-database. I don't care - that's up to the respective maintainers to decide. But generally I concur with Michael - the systemd is a default init and we probably don't want to ship the logcheck file from withing default init package, so logcheck-database might be a better place. I will be happy with collaboratively updated wiki page for the moment. Ondrej -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
[bts-link] source package systemd
# # bts-link upstream status pull for source package systemd # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #758392 (http://bugs.debian.org/758392) # Bug title: systemd: Assertion caused by journalctl --listboots # * https://bugs.freedesktop.org/show_bug.cgi?id=82894 # * remote status changed: NEW - RESOLVED # * remote resolution changed: (?) - FIXED # * closed upstream tags 758392 + fixed-upstream usertags 758392 - status-NEW usertags 758392 + status-RESOLVED resolution-FIXED thanks ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: [bts-link] source package systemd
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package systemd # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #758392 (http://bugs.debian.org/758392) # Bug title: systemd: Assertion caused by journalctl --listboots # * https://bugs.freedesktop.org/show_bug.cgi?id=82894 # * remote status changed: NEW - RESOLVED # * remote resolution changed: (?) - FIXED # * closed upstream tags 758392 + fixed-upstream Bug #758392 [systemd] systemd: Assertion caused by journalctl --listboots Added tag(s) fixed-upstream. usertags 758392 - status-NEW Usertags were: status-NEW. Usertags are now: . usertags 758392 + status-RESOLVED resolution-FIXED There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. thanks Stopping processing here. Please contact me if you need assistance. -- 758392: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758392 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Re: Failed at step NAMESPACE errors
On 28.08.2014 10:34, Michael Stapelberg wrote: Hi Wouter, Wouter Van Hemel wouter-deb...@publica.duodecim.org writes: Problematic daemons include colord and rtkit-daemon: Failed at step NAMESPACE spawning /usr/lib/colord/colord: Operation not permitted Can you strace systemd to see which syscall exactly is failing? systemctl restart colord.service strace -f -o /tmp/strace.log -s 2048 -p 1 Cancel after a second, then, provide strace.log (compress it before emailing). Here are traces of rtkit-daemon and colord. Thanks for your help, Wouter Van Hemel strace-rtkit-daemon.log.gz Description: GNU Zip compressed data strace-colord.log.gz Description: GNU Zip compressed data ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#759609: marked as done (dpkg: warning: unable to delete old directory '/etc/systemd/system/sockets.target.wants': Directory not empty)
Your message dated Fri, 29 Aug 2014 01:54:50 +0200 with message-id 53ffc14a.8050...@debian.org and subject line Re: Bug#759609: dpkg: warning: unable to delete old directory '/etc/systemd/system/sockets.target.wants': Directory not empty has caused the Debian Bug report #759609, regarding dpkg: warning: unable to delete old directory '/etc/systemd/system/sockets.target.wants': Directory not empty to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 759609: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759609 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: systemd Preparing to unpack .../acpid_1%3a2.0.23-1_i386.deb ... Unpacking acpid (1:2.0.23-1) over (1:2.0.22-3) ... dpkg: warning: unable to delete old directory '/etc/systemd/system/sockets.target.wants': Directory not empty Preparing to unpack .../apt-show-versions_0.22.4_all.deb ... Unpacking apt-show-versions (0.22.4) over (0.22.3) ... ---End Message--- ---BeginMessage--- Am 29.08.2014 01:41, schrieb 積丹尼 Dan Jacobson: Package: systemd Preparing to unpack .../acpid_1%3a2.0.23-1_i386.deb ... Unpacking acpid (1:2.0.23-1) over (1:2.0.22-3) ... dpkg: warning: unable to delete old directory '/etc/systemd/system/sockets.target.wants': Directory not empty Preparing to unpack .../apt-show-versions_0.22.4_all.deb ... Unpacking apt-show-versions (0.22.4) over (0.22.3) ... Not a systemd issue and not a problem. The statically shipped symlink has been replaced by proper usage of dh-systemd/i-s-h. Closing the bug report. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ---End Message--- ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#759609: dpkg: warning: unable to delete old directory '/etc/systemd/system/sockets.target.wants': Directory not empty
Package: systemd Preparing to unpack .../acpid_1%3a2.0.23-1_i386.deb ... Unpacking acpid (1:2.0.23-1) over (1:2.0.22-3) ... dpkg: warning: unable to delete old directory '/etc/systemd/system/sockets.target.wants': Directory not empty Preparing to unpack .../apt-show-versions_0.22.4_all.deb ... Unpacking apt-show-versions (0.22.4) over (0.22.3) ... ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
