Bug#893014: systemd: journalctl -g and --grep fail (in different ways)

2018-03-15 Thread Daniel Kahn Gillmor
Package: systemd Version: 237-4 Severity: normal journalctl(1) says: -g, --grep= Filter output to entries where the MESSAGE= field matches the specified regular expression. PERL-compatible regular expressions are used, see pcre2pattern(3) for a detailed des

Bug#879216: /lib/systemd/system/systemd-resolved.service:22: Executable path is not absolute: !!/lib/systemd/systemd-resolved

2017-10-20 Thread Daniel Kahn Gillmor
Package: systemd Version: 235-2 Severity: normal Something about the service configuration for systemd-resolved doesn't match what the service manager expects. What does it mean to start an executable path with "!!" ? 0 dkg@alice:~$ systemctl status systemd-resolved ● systemd-resolved.service

Bug#870747: update-rc.d: enabling a default-disabled service fails: "foo Default-Start contains no runlevels, aborting."

2017-08-04 Thread Daniel Kahn Gillmor
mmends no packages. init-system-helpers suggests no packages. Versions of packages init-system-helpers is related to: ii insserv 1.14.0-5.4+b1 -- no debconf information From 743df08123f386f8a04cad68121de83fc1d17c9d Mon Sep 17 00:00:00 2001 From: Daniel Kahn Gillmor Date: Fri, 4 Aug 2017 13:

Bug#854421: systemd: "systemctl --user cat dirmngr.socket" produced garbage beyond # /dev/null

2017-02-07 Thread Daniel Kahn Gillmor
rade, but i don't know whether that means the underlying problem has been robustly fixed or just somehow hidden. Regards, --dkg #!/usr/bin/make -f # wants hd from bsdmainutils # Author: Daniel Kahn Gillmor test: splicenull uname -a for x in $$(seq 1 20); do ./splicenull | hd;

Bug#854421: systemd: "systemctl --user cat dirmngr.socket" produced garbage beyond # /dev/null

2017-02-06 Thread Daniel Kahn Gillmor
On Mon 2017-02-06 17:18:59 -0500, Daniel Kahn Gillmor wrote: > I've masked the user service dirmngr.socket on one user. Out of > curiosity i tried to see what it looked like, and i got some crazy > spew. > > then i tried unmasking and re-masking and it to try to capture t

Bug#854421: systemd: "systemctl --user cat dirmngr.socket" produced garbage beyond # /dev/null

2017-02-06 Thread Daniel Kahn Gillmor
Package: systemd Version: 232-15 Severity: normal I've masked the user service dirmngr.socket on one user. Out of curiosity i tried to see what it looked like, and i got some crazy spew. then i tried unmasking and re-masking and it to try to capture the problem, and it didn't come back. Then i

Bug#854102: systemd-logind fails to update session's Display property after `startx` from VT

2017-02-04 Thread Daniel Kahn Gillmor
On Sat 2017-02-04 08:11:34 -0500, Felipe Sateler wrote: > From a quick read at the source, the display property appears to only > be settable at session creation time. That's the conclusion i came to also from my digging around in there. > I don't know if this is deliberate or not. Any suggestio

Bug#854102: systemd-logind fails to update session's Display property after `startx` from VT

2017-02-03 Thread Daniel Kahn Gillmor
Package: systemd Version: 232-14 Severity: normal i start my login on this system on a text-mode console (a "VT") and then do "exec startx" to transition to a graphical X11 session. >From within this graphical session, if i query logind about the Display for the login session, it is the empty str

Bug#843310: systemd-journald: user service logs are not available to normal users unless persistent Storage is used.

2016-11-05 Thread Daniel Kahn Gillmor
Package: systemd Version: 232-1 Severity: normal Dear systemd and journald maintainers, User services generate output and that output is logged by the user's systemd session manager. journalctl(1) says: All users are granted access to their private per-user journals. However, this isn't

Bug#834524: Bug#833854: sks: no longer logs to /var/log/sks/

2016-08-29 Thread Daniel Kahn Gillmor
Control: affects 834524 + sks charybdis Over on https://bugs.debian.org/833854, On Fri 2016-08-19 17:49:52 -0400, anarcat wrote: > On Tue, Aug 09, 2016 at 09:23:51PM +0200, Christoph Anton Mitterer wrote: >> On Tue, 2016-08-09 at 12:06 -0400, Daniel Kahn Gillmor wrote: >> > it

Bug#833559: systemd user service standard output is not line-buffered

2016-08-05 Thread Daniel Kahn Gillmor
Package: systemd Version: 230-7 Severity: normal I've tested the following short-lived "daemon" as a systemd user service: --- #include #include int main(int argc, char **argv) { sleep(5); printf("a test\n"); sleep(10); return 0; } --- the "a test" line doesn't show up in the

Bug#764678: dh-systemd: Please support systemd user services

2016-06-28 Thread Daniel Kahn Gillmor
On Fri 2014-10-10 03:30:07 -0400, Michael Vogt wrote: > It would be very nice if dh-systemd would support systemd user > units (both for detecting them during build time and to add > something like "systemctl --global enable my-user-unit" to the > debian/postinst). > > My use case is that the pack

Bug#823980: udev: setting udev_log="debug" in /etc/udev/udev.conf == 90 second hang during boot

2016-05-10 Thread Daniel Kahn Gillmor
Package: udev Version: 229-5 Severity: normal I put udev_log="debug" into /etc/udev/udev.conf to try to understand part of what udev is doing. Then i needed to reboot my computer (for other reasons). Normal bootup is quite fast. But right when the transition from the initramfs to the regular sy

Re: Bug#816391: tor: "systemctl status tor" does not provide useful output

2016-04-13 Thread Daniel Kahn Gillmor
On Wed 2016-04-13 18:52:23 -0400, Michael Biebl wrote: > Am 14.04.2016 um 00:46 schrieb Michael Biebl: >> Am 13.04.2016 um 21:45 schrieb Daniel Kahn Gillmor: >>> is there a reason to have a "tor.service" that is distinct from the >>> tor@*.service files?

Re: Bug#816391: tor: "systemctl status tor" does not provide useful output

2016-04-13 Thread Daniel Kahn Gillmor
On Tue 2016-04-12 18:57:06 -0400, Michael Biebl wrote: > I'm missing a bit of context here. > But if you have templated services and you want to list the status for > all of them, you can use > systemctl status tor@*.service > > Is this is what you are looking for? at the moment, i see this: 0 dk

Re: Bug#816391: tor: "systemctl status tor" does not provide useful output

2016-04-12 Thread Daniel Kahn Gillmor
On Tue 2016-04-12 17:31:51 -0400, Peter Palfrader wrote: > On Tue, 01 Mar 2016, Daniel Kahn Gillmor wrote: > >> Because of the systemd generator approach for tor services, i don't >> seem to be able to do "systemctl status tor" and get any report about >>