Am 24.10.2016 um 22:04 schrieb Charles D. Van Dusen:
> Hi,
>
> I have a rpi3 running raspbian wheezy.
raspbian wheezy is too old to use systemd in a reasonable way.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Am 23.10.2016 um 01:18 schrieb luke:
> Oct 22 23:41:42 donbot systemd[1087]: Starting GNOME Terminal Server...
> Oct 22 23:41:42 donbot dbus-daemon[20090]: Successfully activated service
> 'org.gnome.Terminal'
> Oct 22 23:43:12 donbot systemd[1087]: gnome-terminal-server.service: Start
> operatio
Am 23.10.2016 um 01:18 schrieb luke:
> Package: systemd
> Version: 231-9
> Severity: critical
> Justification: breaks unrelated software
Adjusted to normal
> Dear Maintainer,
>
> systemd is periodically killing a bunch of userspace daemons
> (including gnome terminal sessions, and gvfs)
Do you
Am 22.10.2016 um 22:46 schrieb Bill Gribble:
> On 10/22/2016 02:13 PM, Michael Biebl wrote:
>>
>> Does /lib/systemd/systemd-sleep hibernate
>> work?
>
> Ah, interesting! That works fine, display resumes as expected. Works
> only as root.
This is exactly the c
Am 22.10.2016 um 18:23 schrieb Bill Gribble:
> To answer your question in the other followup, yes, I made a mistake
> titling this bug.
> This is a hibernate-related problem, not suspend.
>
> On 10/22/2016 11:12 AM, Michael Biebl wrote:
>> This is what "systemctl hiber
Am 22.10.2016 um 18:23 schrieb Bill Gribble:
> On 10/22/2016 11:12 AM, Michael Biebl wrote:
>> This is what "systemctl hibernate" uses.
>> Can you run this command and see if that works?
>
> "systemctl hibernate", as either root or a non-root user, res
Control: severity -1 + moreinfo
Am 22.10.2016 um 16:35 schrieb Bill Gribble:
>
> I am entering hibernate by pressing the power button, which I have
> mapped to
> the "hibernate" action in Gnome. I believe this uses the systemd hibernate
> action.
>
> No combination of switching VTs, keyboard/mo
Am 22.10.2016 um 16:35 schrieb Bill Gribble:
> I am entering hibernate by pressing the power button, which I have
> mapped to
> the "hibernate" action in Gnome. I believe this uses the systemd hibernate
> action.
I assume the subject of this bug report is incorrect, which talks about
suspend, whi
Am 27.07.2016 um 02:59 schrieb John Pearson:
> Hello Michael,
>
> After the problem first occurred I reviewed bug #767468 and purged both
> cgmanager and sytemd-shim, but the problem remained. And, of course,
> /proc shows systemd-machined (and only systemd-machined) still "thought"
> /nfs/home w
Am 13.09.2016 um 11:21 schrieb Vektor:
> Package: systemd
> Version: 215-17+deb8u4
> Severity: important
>
> Dear Maintainer,
>
> systemd-journald is deleting log messages when it shouldn't, it is not
> respecting SystemMaxUse and SystemKeepFree as configured in
> /etc/systemd/journald.conf
>
Am 22.07.2016 um 00:28 schrieb Yuri D'Elia:
> On Fri, Jul 22 2016, Michael Biebl wrote:
>> So, this is the main reason I'm worried about enabling lz4 support.
>> Afair, it's not runtime configurable, so each new journal entry would be
>> lz4 compressed, which e
Am 01.02.2016 um 16:41 schrieb Josh Triplett:
> On Mon, Feb 01, 2016 at 04:24:21PM +0100, Ondřej Surý wrote:
>> Hi Michael,
>>
>> I never bothered to implement more than 'd', but I am happy to
>> contribute my sysvrc shell snippet I use as replacement for systems
>> without systemd-tmpfiles install
Control: reassign -1 zsh 5.2-5
Am 26.09.2016 um 23:11 schrieb Martin Steigerwald:
> Am Montag, 26. September 2016, 13:53:21 CEST schrieb Josh Triplett:
>> On Mon, Sep 26, 2016 at 10:27:40PM +0200, Martin Steigerwald wrote:
>>> Am Montag, 26. September 2016, 13:08:07 CEST schrieb Josh Triplett:
>>>
Control: tags -1 - moreinfo
Control: forwarded -1 https://github.com/systemd/systemd/issues/4124
Am 11.07.2016 um 14:33 schrieb Pavel Kosina:
> Its ssh, putty,
>
> dady@linuxbox:~$ systemctl poweroff
> AUTHENTICATING FOR org.freedesktop.login1.set-wall-message ===
> Authentication is require
Control: forcemerge 839607 -1
Am 11.10.2016 um 23:43 schrieb Keller Fuchs:
> Package: systemd
> Version: 215-17+deb8u4
> Severity: important
> File: systemd-logind
>
> Dear maintainers,
>
> On a shell server I co-administer (to1.hashbang.sh), systemd-logind got
> stuck in a restart loop, forcing
Control: tags -1 + moreinfo unreproducible
Am 26.08.2016 um 02:53 schrieb Jean-Philippe MENGUAL:
> Package: udev
> Version: 231-4
> Severity: important
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate ***
>
>* What led up to the situation?
Control: reassign -1 initscripts
On Wed, 8 Apr 2015 13:33:54 +0200 (CEST) Santiago Vila
wrote:
> Package: systemd
> Version: 215-14
>
> After a recent upgrade in a lab where I use NFS, I see messages like this:
>
> ifup[370]: mount.nfs: /home/nfs is busy or already mounted
That hook is shipped
Am 21.10.2016 um 15:31 schrieb Salvo Tomaselli:
> Hello,
>
> me neither. I don't know when it 1st happened. I just wanted to see
> something in the logs and there were no logs besides the ones
> generated by the kernel in /var/log/syslog
/var/log/syslog is not generated by the kernel, but your s
Control: severity -1 important unreproducible
Control: tags -1 moreinfo
Am 21.10.2016 um 15:02 schrieb Salvo Tomaselli:
> severity 793116 critical
> thanks
>
> I am experiencing the same problem, but upon reboot journald won't
> start, so I have no logging whatsoever.
>
> For this reason I'm ra
Thank You!
>
> On 10/13/16, Kirill Sutulo wrote:
>> Yes. restarting service is very fast.
>>
>> On 10/13/16, Michael Biebl wrote:
>>> Control: tags -1 + moreinfo
>>>
>>> Hi
>>> Am 13.10.2016 um 10:33 schrieb kirill:
>>>
>>>&
Package: debhelper
Version: 10.2.2
Severity: normal
In the network-manager package, I have a unit file NetworkManager.service
containing:
...
[Install]
Also=NetworkManager-dispatcher.service
As a result, dh_systemd_start is generating code to (re)start this
service, even though I used
dh_systemd
Control: tags -1 = moreinfo
On Sat, 15 Oct 2016 08:13:27 +0700 Theppitak Karoonboonyanan
wrote:
> Control: reassign -1 udev 231-9
> Control: tag -1 + patch
>
> On Mon, Oct 10, 2016 at 10:03 AM, Theppitak Karoonboonyanan
> wrote:
>
> > With this patch to /etc/init.d/udev, my machine (using sysv
Am 14.10.2016 um 14:47 schrieb Felipe Sateler:
> (We should add dracut and initramfs-tools install state to the
> reportbug template...)
Sounds like a reasonable idea.
Do we want the state of dracut and initramfs-tools or
dracut-core and initramfs-tools-core. I assume the former?
--
Why is it
Am 14.10.2016 um 11:22 schrieb Joel Cross:
> Package: systemd
> Version: 231-9
> Severity: normal
> File: systemd-sleep
>
> Dear Maintainer,
>
> Since the latest upgrade, I have been consistently having problems resuming
> from hibernate (I was successfully hibernating/resuming on a daily basis
Am 13.10.2016 um 18:08 schrieb Michael Biebl:
> Am 13.10.2016 um 17:56 schrieb Michael Biebl:
>> Am 13.10.2016 um 17:47 schrieb Felipe Sateler:
>>> On 13 October 2016 at 12:36, Michael Biebl wrote:
>>>>
>>>> With compat level 9 and older, --no-start di
restarting service is very fast.
>>
>> On 10/13/16, Michael Biebl wrote:
>>> Control: tags -1 + moreinfo
>>>
>>> Hi
>>> Am 13.10.2016 um 10:33 schrieb kirill:
>>>
>>>> systemd-analyze blame | head -8
>>>>
Control: tags -1 + moreinfo
Hi
Am 13.10.2016 um 10:33 schrieb kirill:
> systemd-analyze blame | head -8
> 22.026s nmbd.service
> 6.217s systemd-tmpfiles-setup.service
> 4.462s networking.service
> 3.521s alsa-restore.service
> 3.474s pppd-dns.servi
Am 10.10.2016 um 23:41 schrieb Petter Reinholdtsen:
> [Felipe Sateler]
>> Unfortunately, it appears not. Michael filed an issue upstream[1] to
>> document this better, but I have not found any alternative document.
>>
>> [1] https://github.com/systemd/systemd/issues/4288
>
> Right. I worry that u
Control: forcemerge 839607 -1
Am 05.10.2016 um 12:24 schrieb Mark Bain:
> Package: systemd
> Version: 215-17+deb8u5
> Severity: important
> The following command (run by any user) effects a dos attack on the system:
>
> while true; do NOTIFY_SOCKET=/run/systemd/notify systemd-notify ""; done
Dup
Hi,
thanks for contacting us.
Am 04.10.2016 um 23:53 schrieb Balint Reczey:
> Hello dear maintainer(s),
>
> the Debian LTS team would like to fix the security issues which are
> currently open in the Wheezy version of systemd:
> https://security-tracker.debian.org/tracker/CVE-2016-7796
>
> Woul
Grr, should have proof-read my message :-/
Am 03.10.2016 um 13:31 schrieb Jonathan Wiltshire:
> Hi,
>
> On 2016-10-02 21:36, Michael Biebl wrote:
>> While v215 is not directly affected by this crash (the code to access
>> messages of length=0 was added in v21), the vers
Am 03.10.2016 um 12:11 schrieb Michael Biebl:
> Am 03.10.2016 um 08:22 schrieb Wolfgang Karall:
>> Hello Michael,
>>
>> On 16-10-02 22:36:00, Michael Biebl wrote:
>>> The news about systemd crashing when getting a zero sized message
>>> on the notification
Am 03.10.2016 um 12:11 schrieb Michael Biebl:
> Am 03.10.2016 um 08:22 schrieb Wolfgang Karall:
>> Hello Michael,
>>
>> On 16-10-02 22:36:00, Michael Biebl wrote:
>>> The news about systemd crashing when getting a zero sized message
>>> on the notification
Am 03.10.2016 um 08:22 schrieb Wolfgang Karall:
> Hello Michael,
>
> On 16-10-02 22:36:00, Michael Biebl wrote:
>> The news about systemd crashing when getting a zero sized message
>> on the notification socket made the rounds recently. While v215 is
>> not directly
Control: fixed -1 231-9
Am 02.10.2016 um 22:36 schrieb Michael Biebl:
> Package: systemd
> Version: 215-17+deb8u5
> Severity: important
> User: pkg-systemd-maintainers@lists.alioth.debian.org
> Usertags: jessie-backport
>
> The news about systemd crashing when getting a zero
Package: systemd
Version: 215-17+deb8u5
Severity: important
User: pkg-systemd-maintainers@lists.alioth.debian.org
Usertags: jessie-backport
The news about systemd crashing when getting a zero sized message on the
notification socket made the rounds recently.
While v215 is not directly affected by
Package: init-system-helpers
Version: 1.45
Severity: important
debian/copyright currently lists Michael Stapelberg as the sole
copyright holder and the license as BSD-3-Clause.
dh_systemd_* moved to debhelper. The remaining bits from Michael S are
script/deb-systemd-* and t/.
invoke-rc.d, update
Version: 231-8
Am 29.09.2016 um 23:18 schrieb Michael Biebl:
> Am 29.09.2016 um 20:43 schrieb Dietz Proepper:
>> Package: systemd
>> Version: 215-17+deb8u5
>> Severity: important
>>
>> Dear Maintainer,
>>
>> see the details of the p
Am 29.09.2016 um 20:43 schrieb Dietz Proepper:
> Package: systemd
> Version: 215-17+deb8u5
> Severity: important
>
> Dear Maintainer,
>
> see the details of the problem at
> https://www.agwa.name/blog/post/how_to_crash_systemd_in_one_tweet
>
> I can reproduce it without any problems. And it is
Control: tags -1 + pending
Am 27.09.2016 um 16:29 schrieb Antonio Ospite:
> Package: systemd
> Version: 231-7
> Followup-For: Bug #838191
>
> Dear Maintainer,
>
> I am attaching the patch to
> debian/patches/debian/Adjust-systemd-user-pam-config-file-for-Debian.patch
Committed as 9709b3
Thanks
Am 18.09.2016 um 11:16 schrieb Antonio Ospite:
> After a precious suggestion by Mantas Mikulėnas (grawity in
> #debian-systemd) I verified that this is happening because
> /etc/pam.d/systemd-user does not load pam_limits.so.
>
> The following change fixes the issue:
> -
Control: fixed -1 229-4
Am 22.09.2016 um 16:18 schrieb Michael Biebl:
> There is a related followup change from 230-3 [1]:
>
>> * debian/extra/init-functions.d/40-systemd: Do not call systemctl
>> daemon-reload if the script is called as user (like reportbug does). Als
Control: fixed -1 230-3
Am 22.09.2016 um 15:04 schrieb Felipe Sateler:
> Control: user pkg-systemd-maintainers@lists.alioth.debian.org
> Control: usertags -1 jessie-backport
>
>
> On 20 September 2016 at 19:27, Paul Tagliamonte wrote:
>> found 774153 215-17+deb8u5
>
>
>
>> FWIW, this seems l
Am 21.09.2016 um 15:06 schrieb Michael Biebl:
> Am 21.09.2016 um 14:10 schrieb Martin Pitt:
>> Hello Dmitry,
>>
>> Dmitry Bogatov [2016-09-21 14:47 +0300]:
>>> Since 'runit-init' package, which provides /sbin/init is in testing, I
>>> ask include &
Am 21.09.2016 um 14:10 schrieb Martin Pitt:
> Hello Dmitry,
>
> Dmitry Bogatov [2016-09-21 14:47 +0300]:
>> Since 'runit-init' package, which provides /sbin/init is in testing, I
>> ask include 'runit-init' into Pre-Depends: of this metapackage.
>
> Does that need any adjustment in invoke-rc.d, s
Am 21.09.2016 um 06:29 schrieb Michael Biebl:
> Control: tags -1 moreinfo unreproducible
> Control: severity -1 important
>
> Am 21.09.2016 um 05:31 schrieb Grond:
>> Setting up systemd (215-17+deb8u5) ...
>> addgroup: The group `systemd-journal' alr
Control: tags -1 moreinfo unreproducible
Control: severity -1 important
Am 21.09.2016 um 05:31 schrieb Grond:
> Setting up systemd (215-17+deb8u5) ...
> addgroup: The group `systemd-journal' already exists as a system group.
> Exiting.
> dpkg: error processing package systemd (-
Hi Jon,
thanks for your efforts.
Am 20.09.2016 um 03:26 schrieb Jon DeVree:
> The attached patches are about as clean as I can make it. The first one
> fixes the initial problem I found during git-bisect. The second one
> fixes the part of the problem that upstream pointed out in the issue/PR.
G
Am 15.09.2016 um 06:25 schrieb 積丹尼 Dan Jacobson:
> Maybe instead test if the group exists via other means, and then only if
> it doesn't, use addgroup to add it.
No, as said this is a bug in adduser/addgroup.
The root cause should be fixed and not worked around in individual packages.
Michael
Control: block -1 by 763055
Am 15.09.2016 um 01:56 schrieb 積丹尼 Dan Jacobson:
> Package: udev
> Version: 231-6
> Severity: wishlist
>
> Perhaps on upgrade instead of saying
> addgroup: The group `input' already exists as a system group. Exiting.
> say nothing, and instead just say
>
Control: tags -1 + pending
Am 07.09.2016 um 18:31 schrieb Michal Schmidt:
> systemd-fsckd's event loop terminates if nothing happens for 30 seconds
> (IDLE_TIME_SECONDS). Usually fsck writes progress updates more frequently
> than that, but the interval is not guaranteed. So systemd-fsckd may exit
Package: systemd-bootchart
Version: 231-1
Severity: wishlist
It would be nice if systemd-bootchart would also be able to profile the
initramfs stage. We should investigate if this is doable via
initramfs-tools hooks or if this needs direkt support from
initramfs-tools.
dracut seems to be covered
Am 10.09.2016 um 17:45 schrieb Felipe Sateler:
> Control: forwarded -1 https://github.com/systemd/systemd/issues/4122
>
> On 9 September 2016 at 19:36, Michael Biebl wrote:
>> Upstream's position on this is, that masks apply only on that particular
>> name and no
Am 10.09.2016 um 15:16 schrieb Michael Biebl:
> On Wed, 7 Sep 2016 18:31:12 +0200 Michal Schmidt
> wrote:
>> systemd-fsckd's event loop terminates if nothing happens for 30 seconds
>> (IDLE_TIME_SECONDS). Usually fsck writes progress updates more frequently
>> than
On Wed, 7 Sep 2016 18:31:12 +0200 Michal Schmidt
wrote:
> systemd-fsckd's event loop terminates if nothing happens for 30 seconds
> (IDLE_TIME_SECONDS). Usually fsck writes progress updates more frequently
> than that, but the interval is not guaranteed. So systemd-fsckd may exit
> by itself while
Am 10.09.2016 um 02:27 schrieb Andreas Kloeckner:
> Package: systemd
> Version: 231-4
> Severity: normal
>
> Dear Maintainer,
>
> on my system, the following happens (from journalctl -e) on trying to start
> the
> services in the subject.
>
> --
> Sep 09 19:0
Am 10.09.2016 um 00:26 schrieb Michael Biebl:
> So, you'll also need to mask that name, i.e
> dbus-org.freedesktop.resolve1.service
https://github.com/systemd/systemd/issues/1873
is somewhat related.
Upstream's position on this is, that masks apply only on that particular
name
Am 10.09.2016 um 00:20 schrieb Brian Kroth:
> Michael Biebl 2016-09-09 23:33:
>> Am 09.09.2016 um 22:47 schrieb Brian Kroth:
>>> Package: systemd
>>> Version: 230-7~bpo8+2
>>> Severity: normal
>>> Tags: security
>>>
>>> Dear Maintaine
Thanks for the hint, Michal.
Seems like someone else already came to the same conclusion:
https://gist.github.com/ebautistabar/82811d492231700ab2471dd9048502b7
Am 07.09.2016 um 18:31 schrieb Michal Schmidt:
> systemd-fsckd's event loop terminates if nothing happens for 30 seconds
> (IDLE_TIME_SEC
Am 09.09.2016 um 22:47 schrieb Brian Kroth:
> Package: systemd
> Version: 230-7~bpo8+2
> Severity: normal
> Tags: security
>
> Dear Maintainer,
>
> systemd appears to start systemd-resolved, even when it's been masked,
> in the background even when an unprivileged user calls systemd-resolve.
>
>
Control: tags -1 + pending
Am 09.09.2016 um 13:37 schrieb Dimitri John Ledkov:
> Package: systemd
> Version: 231-5
> Severity: wishlist
>
> Hello,
>
> I'm looking to modify debian/rules and I've noticed that some common
> variables are re-invented, instead using things that are provided by a
> s
Control: forwarded -1 https://github.com/systemd/systemd/issues/2913
Hi
Am 05.09.2016 um 12:23 schrieb Tomas Crhonek:
> But journalctl -u add.service (or journalctl -f -u add.service) shows
> only some records, not complete output from program. In journalctl
> (without -u) are all messages.
This
Control: tags -1 - moreinfo
Am 28.08.2016 um 17:51 schrieb Michael Biebl:
> It is odd though indeed, that systemd marks your nfs share as mounted
> when it actually isn't. It seems I can reproduce that issue with v231 as
> well. I've created a test share on a server, stopped the
Am 28.08.2016 um 17:24 schrieb Tero Marttila:
> The fstab entry for this specific mount:
>
>> nfs.test.pvl:mail /srv/mail nfs4
>> defaults,auto,nodev,nosuid,noatime,x-systemd.automount 0 0
I think you really want "noauto" instead of "auto" here, so the share is
only mounted
Package: watchdog
Version: 5.15-1
Severity: normal
Hi,
thanks for shipping a service file for wd_keepalive [1]
There are some changes I think should be done:
1/ the sendsigs.omit.d interface is not supported under systemd, so
please drop
ExecStartPost=/bin/sh -c 'ln -s /var/run/wd_keepalive.pi
Hi
On Mon, 10 Aug 2015 09:15:58 -0400 Jon DeVree wrote:
> As far as the shutdown problem is concerned, just putting udevd's pid
> into /run/sendsigs.omit.d/udevd fixes the problem without causing any
> new ones.
>
> Thats probably a good fix for debian rather than trying to patch udevd
> itself
Control: found -1 231-2
Am 15.08.2016 um 00:17 schrieb Rick Thomas:
> Sorry, it’s not fixed in 231-2… Please see attached boot log.
Yeah, the revert was incomplete.
The service files in systemd use
MemoryDenyWriteExecute=yes
which is implemented using seccomp. So we need to revert
40652ca4791fc3
Control: tags -1 + confirmed
Am 05.08.2016 um 04:33 schrieb Matthias Urlichs:
> Package: systemd
> Version: 230-1
> Severity: serious
> Justification: Missing Replaces:
>
> Unpacking systemd (231-1) over (230-1) ...
> dpkg: error processing archive
> /var/cache/apt/archives/systemd_231-1_amd64.d
Am 03.08.2016 um 17:26 schrieb Felipe Sateler:
> Control: forwarded -1 https://github.com/systemd/systemd/issues/3882
> Control: severity -1 serious
> Yes, I'd like upstream's opinion on this first. However, I think this
> bug should be bumped to RC to prevent migration to testing, as this
> makes
Am 01.08.2016 um 23:40 schrieb Felipe Sateler:
> So I think the kernel should enable SECCOMP.
I agree, unless SECCOMP on arm has some unwanted side-effects.
Felipe, can you file a bug report against the linux package accordingly?
> However, I think systemd should also simply (warn and) ignore sec
Am 30.07.2016 um 20:47 schrieb Michael Biebl:
> Am 30.07.2016 um 19:52 schrieb Felipe Sateler:
>> On 29 July 2016 at 17:05, Michael Biebl wrote:
>>> Am 29.07.2016 um 22:44 schrieb Michael Biebl:
>>>> Package: init-system-helpers
>>>> Version: 1.4
Am 30.07.2016 um 19:52 schrieb Felipe Sateler:
> On 29 July 2016 at 17:05, Michael Biebl wrote:
>> Am 29.07.2016 um 22:44 schrieb Michael Biebl:
>>> Package: init-system-helpers
>>> Version: 1.41
>>> Severity: serious
>>>
>>> Running
&g
Am 29.07.2016 um 23:10 schrieb Felipe Sateler:
> I was going to ask this. I think we should register interest in
> insserv in the reportbug configuration.
Good idea. Added a bug-control script and pushed to master.
--
Why is it that all of the instruments seeking intelligent life in the
universe
Am 29.07.2016 um 23:29 schrieb Rick Thomas:
> Hmmm… Curiouser and curiouser!
>
> I upgraded a VM (amd64) to latest Sid (with systemd version 231-1). The
> problem is *not* present there.
>
> The problem may be specific to arm hardware? I’ll try it on a PowerPC G4
> (Apple Mac PPC) machine la
Am 29.07.2016 um 22:44 schrieb Michael Biebl:
> Package: init-system-helpers
> Version: 1.41
> Severity: serious
>
> Running
> update-rc.d foo disable
> update-rc.d foo defaults
> will create start symlinks although this should not happen for a
> disabled service.
T
Package: init-system-helpers
Version: 1.41
Severity: serious
Running
update-rc.d foo disable
update-rc.d foo defaults
will create start symlinks although this should not happen for a
disabled service.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable-debug
APT policy: (
Am 29.07.2016 um 14:42 schrieb Michael Biebl:
> Am 29.07.2016 um 14:08 schrieb Marc Haber:
>> [ 113.379297] systemd[1]: Failed to start Network Service.
>> [ 113.444174] systemd[1565]: systemd-networkd.service: Failed at step
>> SECCOMP spawning /lib/systemd/systemd-netwo
Am 29.07.2016 um 14:08 schrieb Marc Haber:
> systemd 231-1 on Banana Pi fails with a bunch of "Failed at step
> SECCOMP spawning systemd-food: Invalid Argument". This at least
> applies to logind and networkd. Here is the output of trying to restart
> systemd-networkd:
>
> [ 113.060755] systemd[1
Am 29.07.2016 um 09:17 schrieb Michael Biebl:
> That's not a bug in systemd but in your service file.
> If you want to run in early boot, you'll need to use
> DefaultDependencies=yes and specify your dependencies/orderings carefully.
I've filed an upstream RFE bug at [1].
Am 28.07.2016 um 22:01 schrieb Rick Thomas:
> No. This is a stock kernel. It’s available from both testing and unstable
> repos. The machine itself is a SheevaPlug. Nothing custom about it.
>
> What makes you think it’s custom?
This was more of a question then a statement.
I wanted to rule o
Am 28.07.2016 um 16:39 schrieb Michael Biebl:
> Maybe Felipe's helper could be generalized and added to gbp pq, like
> gbp pq cherry-pick
Or more generally gbp pq cherry-pick --before|after
This will cherry-pick a given commit after (or before) all patches with
the give topi
Hi Guido
Am 22.07.2016 um 10:50 schrieb Guido Günther:
> On Mon, Jun 27, 2016 at 08:41:18PM +0200, Michael Biebl wrote:
>> as discussed offline, in pkg-systemd we typically have two type of
>> patches: upstream cherrry-picks and Debian specific patches. Upstream
>> cherry-p
control: tags -1 + moreinfo
Am 28.07.2016 um 12:08 schrieb Rick Thomas:
> Main PID: 477 (code=exited, status=228/SECCOMP)
...
> Kernel: Linux 4.6.0-1-marvell
That looks like you are using a custom kernel. Is the problem
reproducible with the default Debian Linux kernel?
--
Why is it that all o
Am 27.07.2016 um 11:17 schrieb Arturo Borrero Gonzalez:
> Thanks Michael,
>
> just uploaded to mentors a new version with all of this changes.
>
> Would you please review and sponsor?
I've uploaded the package as-is. It will have to go through NEW, so
might take a while.
Something which you mi
Package: init-system-helpers
Version: 1.40
Severity: serious
In the latest upload, we dropped the insserv dependency and added some
fallback code for SysV init scripts for the case where insserv is not
installed [1].
Unfortunately, the disable case is not handled correctly. It removes all
symlink
Control: tags -1 + moreinfo
Am 27.07.2016 um 01:37 schrieb John Pearson:
> This appears to be fundamentally similar to Debian bug #767468i, assigned to
> cgmanager.
Do you have cgmanager installed? Is it running?
Please attach your fstab and autofs configuration files.
A journalctl -alb log migh
Source: glibc
Version: 2.19-18+deb8u4
Severity: normal
Tags: patch
Hi,
while working on a backport of systemd v230 for jessie, we ran into
issues. Our test-suite was failing on i386, specifically test-tmpfiles.
It turns out, the files created wit O_TMPFILE had broken permissions and
were unreadab
stly helps LXC containers, which don't
have a real VC subsystem but start some pseudo-ttys on tty1-tty4. So the
check for /dev/tty2 was wrong. We had a discussion with systemd upstream
who recommends to test for /dev/tty0 as indicator for a working VC
subsystem.
-- Michael Biebl Sun, 2
Control: tags -1 + moreinfo
Am 21.07.2016 um 19:03 schrieb Yuri D'Elia:
> On Thu, Jul 21 2016, Michael Biebl wrote:
>>>> LZ4 is the default compression method according to upstream since systemd
>> If we build against liblz4, what happens with existing journal file
Am 21.07.2016 um 18:46 schrieb Michael Biebl:
> Am 21.07.2016 um 18:32 schrieb Felipe Sateler:
>> On 21 July 2016 at 06:28, Yuri D'Elia wrote:
>>> Package: systemd-coredump
>>> Version: 230-7
>>> Severity: wishlist
>>>
>>> LZ4 compres
Am 21.07.2016 um 18:32 schrieb Felipe Sateler:
> On 21 July 2016 at 06:28, Yuri D'Elia wrote:
>> Package: systemd-coredump
>> Version: 230-7
>> Severity: wishlist
>>
>> LZ4 compression makes a huge difference in terms of performance impact when
>> compressing core files, but it's currently not ena
Am 20.07.2016 um 17:37 schrieb Wang Jian:
> # diff -u /lib/systemd/system/getty@.service
> /etc/systemd/system/getty@.service
> --- /lib/systemd/system/getty@.service 2016-04-25 17:32:15.0 +0800
> +++ /etc/systemd/system/getty@.service 2015-05-17 20:28:50.253964583 +0800
> @@ -21,7 +21,
Am 20.07.2016 um 12:22 schrieb Peter Pentchev:
> So... right now, it seems to me that the proper thing to do as a
> maintainer of a package that has both a SysV init script and a systemd
> service file would be to disable the systemd sequence and let
> dh_installinit do its job. This would mean th
Hi
Am 19.07.2016 um 19:28 schrieb Niels Thykier:
> Thanks for the report - at first glance it sounds like #830208 (Cc'ed
> accordingly).
>
> Peter's message quoted in full (for those not subscribed to
> debhelper-devel):
>
>> Hi,
>>
>> Now that dh_systemd_start and dh_systemd_enable are part of
Am 19.07.2016 um 14:12 schrieb Michael Biebl:
> On Sat, 16 Jul 2016 15:34:20 +0200 Martin Pitt wrote:
> Given Lennarts explanation at [1], I would suggest that we replace that
> condition with ConditionPathExists=/dev/tty0
There is an interesting follow-up by Lennart regarding LXC
On Sat, 16 Jul 2016 15:34:20 +0200 Martin Pitt wrote:
> Control: tag -1 pending
>
> Wang Jian [2016-05-19 23:59 +0800]:
> > getty-static.service starts getty on tty2-6, but container has only 4
> > ttys (1-4) at default. getty will exit and be respawned for tty5-tty6.
> > This leads to high cpu u
On Sat, 16 Jul 2016 15:34:20 +0200 Martin Pitt wrote:
> Control: tag -1 pending
>
> Wang Jian [2016-05-19 23:59 +0800]:
> > getty-static.service starts getty on tty2-6, but container has only 4
> > ttys (1-4) at default. getty will exit and be respawned for tty5-tty6.
> > This leads to high cpu u
On Mon, 18 Jul 2016 11:05:12 +0200 Michael Biebl wrote:
> Am 18.07.2016 um 07:56 schrieb Evgeni Golov:
> > Hi again,
> >
> > On Mon, Jul 18, 2016 at 12:30:34AM +0200, Michael Biebl wrote:
> > wrt SIGPWR: iirc lxc-stop will issue SIGPWR to the container to stop it,
Am 19.07.2016 um 02:52 schrieb Laurent Bonnaud:
> This file belongs to package root-system-proofd that has been removed from
> Debian. I purged this package from my system, and now the error message is
> not displayed any more.
Do you still have a copy of the /etc/init.d/root-system-proofd sys
Am 18.07.2016 um 19:01 schrieb Martin von Wittich:
> So as far as I'm concerned, this update can be released.
Thanks a lot Martin for the very thorough testing.
Very much appreciated.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed
801 - 900 of 2654 matches
Mail list logo
