Hi Michael,
On 07/15/2017 11:10 PM, Michael Biebl wrote:
> thanks a lot for your detailed reply!
>
> I've CCed the pkg-systemd-maintainers m-l and Wouter, as the maintainer
> of nbd.
>
> You raise some good points. Maybe this is something you could bring up
> on the upstream mailing list?
I ass
Control: tags -1 + moreinfo
Hi Michael,
On 07/15/2017 03:36 PM, Michael Biebl wrote:
> I'm currently investigating whether it would be possible to make
> fstab-decode non-essential and move it out of sysvinit-utils into the
> initscripts package where it is used by /etc/init.d/umountfs and
> /etc
Package: systemd
Version: 232-15
Severity: wishlist
Dear maintainers,
while helping out on debian-mentors@ with #854192 I noticed that systemd
doesn't appear to handle the case very well when dbus is installed but not
configured properly (this was due to a bug in the usbguard package that
missed
Control: severity -1 important
Control: clone -1 -2
Control: reassign -2 systemd 230-7
Control: affects -1 cryptsetup
Control: affects -2 open-iscsi cryptsetup
Control: retitle -1 open-iscsi: No support for disabling LUKS volumes on
shutdown
Control: retitle -2 systemd: cryptsetup-generator does n
On 12/29/2016 01:59 PM, Petter Reinholdtsen wrote:
> [Martin Pitt]
>> "service", not invoke-rc.d, but I do agree that it would be better to
>> completely drop that magic. This would be a nice way to gradually teach
>> people
>> about the init system neutral APIs, and also find/fix places which har
Hi Andreas,
Sorry for not replying earlier, but I wanted to mull this over some
before answering.
On 12/27/2016 10:49 AM, Andreas Henriksson wrote:
> On Sun, Dec 25, 2016 at 01:34:41PM +0100, Christian Seiler wrote:
>> Hi there,
>> (Cc'd a lot of people, so that hopefull
Hello Martin,
On 12/25/2016 09:18 PM, Martin Pitt wrote:
> Christian Seiler [2016-12-25 13:34 +0100]:
>> I think I have a solution to both issues - and my solution
>> does not require any change to any individual init script,
>> and best of all it doesn't even require
n to
the init script. One could detect this properly by adding
support to detect this to systemd's sysv-generator (or add an
additional new generator), but I don't think that is worth
the effort.
From 63b96c5399280c22f58eb69c8b5eb874d4a2b497 Mon Sep 17 00:00:00 2001
From: Christian Seiler
D
Version: 1.34
Control: tags -1 - moreinfo
On 12/21/2016 01:53 PM, Felipe Sateler wrote:
> Control: tags -1 moreinfo
> On Sun, 15 Mar 2015 15:23:38 +0100 Christian Seiler
> wrote:
>> Package: init-system-helpers
>> Version: 1.22
>> Severity: important
>> Tag
On 04/26/2016 10:09 AM, Martin Pitt wrote:
> Christian Seiler [2015-03-15 15:23 +0100]:
>> deb-systemd-helper doesn't handle drop-ins at all (only the main
>> service file is parsed) and it doesn't treat lists properly: when
>> creating links for Alias=, it doesn&#x
On 28.08.2015 04:39, Felipe Sateler wrote:
> On 27 August 2015 at 17:19, Christian Seiler wrote:
>> I've also attached a trivial package in two versions to test this.
>> They change all 3 options (WantedBy=, Also= and Alias=) to test
>> everything at the same tim
ii perl-base 5.20.2-6
init-system-helpers recommends no packages.
init-system-helpers suggests no packages.
-- no debconf information
From 38aa3cc8c1390a9ae5ba047faf4cae3b3674286c Mon Sep 17 00:00:00 2001
From: Christian Seiler
Date: Thu, 27 Aug 2015 22:13:15 +0200
Subject: [PATCH] deb-s
Thanks for taking care of this!
Am 2015-07-07 13:03, schrieb Jonas Meurer:
Am 2015-06-28 12:54, schrieb Michael Biebl:
I suggest to add this simple fix to Jessie by uploading it to
stable-proposed-updates. What do you think? Also, do you think
that
/etc/systemd/system/remote-fs-pre.target.d/nf
Control: severity -1 minor
Control: reassign -1 systemd 215-17
Control: retitle -1 systemd: sysv-generator overzealous with log level
Am 2015-05-19 14:50, schrieb Mathieu Malaterre:
Seems like there is something going on wrong with systemd and current
jessie package. My dmesg reveals:
[ 498.09
> - changing finger memory is difficult, so I keep entering
> 'halt' instead of 'poweroff' occasionally
I had the same problem, so I added the following to my /root/.bashrc on
Jessie so I can retrain my finger memory:
# Ma
On 04/11/2015 03:28 PM, Michael Biebl wrote:
Am 11.04.2015 um 12:14 schrieb Christian Seiler:
Package: systemd
Version: 215-15
Severity: minor
Tags: patch
Dear Maintainers,
with 215-13, hwclock-save.service was added to sync the system clock
with the hardware clock on shutdown. This will fail
Package: systemd
Version: 215-15
Severity: minor
Tags: patch
Dear Maintainers,
with 215-13, hwclock-save.service was added to sync the system clock
with the hardware clock on shutdown. This will fail in containers which
don't have the appropriate privileges (which is annoying, but not
really pro
On 03/31/2015 04:44 PM, Michael Biebl wrote:
Am 31.03.2015 um 15:52 schrieb Christian Seiler:
Package: systemd
Version: 215-12
Severity: normal
Dear Maintainers,
while I was trying to set a different log level for systemd via DBus, I
accidentally forgot that the 'Set' metho
Package: systemd
Version: 215-12
Severity: normal
Dear Maintainers,
while I was trying to set a different log level for systemd via DBus, I
accidentally forgot that the 'Set' method for DBus properties expects a
variant as a data type. So when using the following (wrong) command:
dbus-send --pr
(Sorry for the noise, pressed 'send' to soon...)
Am 2015-03-20 15:01, schrieb Raphael Hertzog:
On Sun, 15 Mar 2015, Christian Seiler wrote:
Control: severity -1 important
Control: tags -1 + patch
I'm tempted to raise the severity to serious as the current behaviour
is really b
Am 2015-03-20 15:01, schrieb Raphael Hertzog:
On Sun, 15 Mar 2015, Christian Seiler wrote:
Control: severity -1 important
Control: tags -1 + patch
I'm tempted to raise the severity to serious as the current behaviour
is really bad for packages that ship both native .service files and
Am 2015-03-20 06:25, schrieb Michael Biebl:
You can probably trigger this by putting 12 modules into
/etc/modules-load.d. Each one will generate a message for the
journal
and after the 11th the service will hang. Jupp, just tried it,
deadlocks. Will, kind-of, because after ~15s it will somehow
Am 2015-03-16 13:51, schrieb Michael Biebl:
It would be great, if Mateusz can confirm that this patch [1] does
indeed fix his issue.
Mateusz, if you are not versed in compiling packages yourself and you
would prefer if we provided you with a test package, please let us
know.
I can also provide
Note that this is not necessarily only #777601, there's also #777164.
The fix in systemd 215-12 fixes part of the problem, but the other
part still persists.
I have posted a backported patch to #777164 for this issue (it's
fixed in 219 upstream).
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug
Control: severity -1 important
Control: tags -1 + patch
Dear Maintainer,
(Cc systemd maintainers, because it's of interest to them.)
I have created a patch that implements the previously missing parts of
systemd integration into update-rc.d, following along the lines of the
patch I have written
Package: init-system-helpers
Version: 1.22
Severity: important
Tags: patch
Dear Maintainers,
deb-systemd-helper doesn't handle drop-ins at all (only the main
service file is parsed) and it doesn't treat lists properly: when
creating links for Alias=, it doesn't properly treat multiple entries
in
Control: severity -1 serious
Control: tags -1 + patch
Dear Maintainers,
this doesn't only affect libvirt/KVM somewhat, but it also breaks LXC,
which also uses its own cgropus. lxc-attach will stop working once
systemctl daemon-reload has been issued with a running LXC instance.
Since this breaks
Am 2015-03-03 16:26, schrieb Michael Biebl:
I did a couple more reboots and did indeed run into the problem, that
systemd-sysctl.service was started after syslog.socket, so I got the
"missed XXX messages" again.
Adding the After=systemd-sysctl.service ordering to syslog.socket
fixed
that. In [1]
Am 2015-03-03 15:33, schrieb Michael Biebl:
Am 02.03.2015 um 15:42 schrieb Christian Seiler:
- SOLUTION (mostly the same as before, but SendBuffer is set on a
different unit and a Condition is added to the service):
1. Increase max_dgram_qlen to a reasonable value. The easiest
I did some more tests on this and there is one key thing that I
misunderstood: SO_SNDBUF of the socket that is used to send the
datagrams is used as a limit in the kernel, not of the socket syslog
uses to receive them.
I actually tried setting SendBuffer=1 and ReceiveBuffer=1 on
syslog.socket (to
Small correction to my previous observations:
Am 2015-02-25 18:59, schrieb Christian Seiler:
- SendBuffer=8M will increase the max size of a single log message
that may be sent via this socket (8M is probably at bit much)
Actually that's not true. I've misread the kernel source
Am 2015-02-26 00:04, schrieb Michael Biebl:
Also: I'm not looking for a solution that solves this for any
possible amount of log messages, but I do think that the current
limit doesn't provide enough of a safety zone that one would like
to rely on.
If we can make the journald -> syslog forwardi
Am 2015-02-25 23:26, schrieb Michael Biebl:
If you need that kind of throughput, using the imjournal module might
possibly be the better choice (would need some testing, how mature
imjournal is). Unfortunately, it's not really possible to ship a
default
rsyslog configuration, which uses imjourna
Control: tags -1 - moreinfo
Am 2015-02-25 21:27, schrieb Michael Biebl:
Am 25.02.2015 um 18:59 schrieb Christian Seiler:
Control: severity -1 serious
Thoughts?
Those missing syslog messages (only) happen when systemd flushes the
initial boot kernel/messages to the syslog socket, right
s of systemd for Jessie could include it.
Thank you for considering!
Christian
[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759001
[1]
https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=106;filename=sysv-generator-add-support-for-etc-insserv-overrides.patch;att=1;bug=759001
From: Christian
Control: severity -1 serious
(justification for severity: breaks unrelated software, in this case
all syslog daemons on a default installation; could possibly be
considered grave or even criticial - data loss affecting nearly all
users)
This bug is actually much worse than it seems. In fact, on
four possible
combinations (w/ or w/o reload support, w/ or w/o override), it now
works as expected. I also looked at the function to see if there
were some other surprises in there, but the the rest just parses
headers.
I've attached an updated patch. Any objections to that?
Christian
From:
lable.
Author: Christian Seiler
Origin: backport
Applied-Upstream: 4d858e7d9f39038713f760d7acc64acf7bba2aa7, 11c6476a08af7a8a9ae6a2d0f8370587f7b31663
Last-Update: 2015-02-17
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/src/login/logind-user.c
+++ b/src/login/logind-u
Am 17.02.2015 um 13:04 schrieb Christian Seiler:
Thinking about it, perhaps we could use Documentation=? Just add a
Documentation=file:///etc/insserv/overrides/$NAME? Then at least
systemctl status will show the information. Not perfect, but
probably better than nothing...
Somehow I think we
Package: systemd
Version: 215-12
Severity: normal
Tags: fixed-upstream patch
Dear Maintainers,
please consider backporting the fixes in upstream that make logind
work if CAP_SYS_ADMIN is not set, namely:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=4d858e7d9f39038713f760d7acc64acf7bba
Am 2015-02-17 12:31, schrieb Michael Biebl:
Am 17.02.2015 um 01:08 schrieb Christian Seiler:
Only minor issue is that SourcePath= is a single-valued entry in
systemd, so I can't just add the override if it exists, and
FragmentPath= is only ever dynamically filled by systemd when
parsing,
c/insserv/overrides/$NAME as
SourcePath=, of course, I don't have a strong opinion on either one of
these solutions.)
We are pretty late into the freeze though, so this would
require an ack from our release managers.
Do you want me to ask for pre-approval?
Christian
From: Christian Seiler
Am 27.01.2015 um 15:39 schrieb Michael Biebl:
> Am 27.01.2015 um 13:07 schrieb Christian Seiler:
>> Am 27.01.2015 um 06:19 schrieb Michael Biebl:
>>> - Drop $remote_fs from the open-isci LSB header and replace it with
>>> $local_fs. That looks wrong anyway.
>>
Am 27.01.2015 um 06:19 schrieb Michael Biebl:
>> Of course, if you have a better idea of how to do this?
>
> Aside from shipping real native unit files, that's probably the least
> invasive change:
>
> - Drop $remote_fs from the open-isci LSB header and replace it with
> $local_fs. That looks wro
(Since I didn't get cc'd in the original reply, I'm replying here. Sorry
about that.)
Am 26.01.2015 um 16:12 schrieb Ritesh Raj Sarraf:
> On 01/26/2015 07:54 PM, Michael Biebl wrote:
>>> unblock open-iscsi/2.0.873+git0.3b4b4500-4
>> That patch doesn't look right.
>>
>> Calling systemctl from an in
Am 2015-01-25 17:16, schrieb Michael Biebl:
Am 25.01.2015 um 15:43 schrieb Ritesh Raj Sarraf:
I've still kept the systemd folks in the loop, hopefully they may be
able to shed some light.
I'd start by looking at the fedora package and see how the package is
integrated into the systemd boot pro
GPG key in Debian's keyring.
Thanks a lot for taking the time to investigate this so thoroughly!
Christian
Am 25. Januar 2015 10:32:21 MEZ, schrieb Ritesh Raj Sarraf
:
>On 01/23/2015 05:25 PM, Christian Seiler wrote:
>>
>>> Next, I'll verify your fix. Hopefully by this we
Hi Ritesh,
Am 2015-01-23 09:35, schrieb Ritesh Raj Sarraf:
I was able to reproduce the problem on my local setup. I've put up a
video just to be sure we are both referring to the same problem.
http://youtu.be/cwcnk00Hwk0 [1]
Yes, that's the same problem, that it waits 90s for the devices to
ay, since it also does the same thing if
the process has already exited).
.
With this patch, journald will no longer silently discard messages
that are supposed to be sent to syslog in these situations.
Author: Christian Seiler
---
This patch header follows DEP-3: http://dep.debia
49 matches
Mail list logo
