On 2/13/18 6:29 PM, Felipe Sateler wrote:
> Changelog has this by Marco d'Itri:
>
>> * Do not install sysctl.d/50-default.conf because the systemd package
>>should not change kernel policies, at least until it will become
>>the only supported init system.
Thanks for pointing this out!
Package: systemd
Version: 237-2
Severity: normal
Dear Maintainer,
by default Debian uses the pfifo_fast network queuing algorithm:
# tc -s qdisc show
[...]
qdisc pfifo_fast 0: dev eth0 root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1
1 1 1 1 1 1
Sent 413728102 bytes 475015 pkt (dropped 0,
Package: systemd
Version: 233-5
Dear maintainer,
here are 2 DNS queries that illustrate the problem:
- when I query a "real" DNS server (bind) I get the expected answer
"irancy.iut2.upmf-grenoble.fr"
- when I query systemd-resolved I get the short answer "irancy"
root@irancy:~# host 192.16
Hi,
the problem is still there in this package version:
Package: libpam-systemd
Version: 232-18
Here is what happens when I su from root to a normal user:
févr. 28 15:01:36 irancy su[7313]: Successful su for bonnaudl by root
févr. 28 15:01:36 irancy su[7313]: + /dev/pts/0 root:bonnaudl
févr. 28
On 16/07/2016 16:47, Martin Pitt wrote:
> It is shown in log level debug. You can run the generator as user in
> debug mode in a running system, that's safe and unintrusive:
>
> mkdir /tmp/x
> SYSTEMD_LOG_LEVEL=debug
> /lib/systemd/system-generators/systemd-sysv-generator /tmp/x /tmp/x /tmp/
Hi,
this bug looks very much like this one:
https://bugs.launchpad.net/debian/+source/systemd/+bug/1426588
I tried the test case in a jessie system and systemctl crashes:
# cat > /etc/init.d/broken
#!/bin/sh
### BEGIN INIT INFO
# Provides: unknownservice
# Required-Start: localfs
# Required-S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 31/03/2015 11:24, Michael Biebl wrote:
> Works fine here with systemd 215-14.
> Can you please try to reproduce the bug with this version?
On this system I use experimental so systemd is now at version 219-5.
But similar crashes still exists. He
