Hi Julian,
thanks for the detailed bug report.
Am 18.11.2015 um 16:01 schrieb Julian Brost:
> I was also able to fully reproduce this on sid with systemd 227-3. With about
> 700 leaked scope units, list-unit-files took about 1.2 seconds instead of the
> normal 0.1 seconds.
On a first glance this
Am 15.11.2015 um 20:17 schrieb Felipe Sateler:
> systemd-analyze is rather large. Perhaps there is scope for a
> systemd-tools or something that covers things that will probably not
> be needed on production containers (systemd-{analyze,cgls,cgtop,delta}).
I'm a bit torn on this. Those four tools
Am 18.11.2015 um 20:53 schrieb Michael Biebl:
> Am 15.11.2015 um 20:17 schrieb Felipe Sateler:
>> systemd-analyze is rather large. Perhaps there is scope for a
>> systemd-tools or something that covers things that will probably not
>> be needed on production containers (system
Hi Daniel
Am 18.11.2015 um 21:07 schrieb Daniel Baumann:
> the current systemd package needs at least libseccomp 2.2.1-2 due to the
> move to /lib of libseccomp. It would be nice if you could update the
> versioned build-depends to libseccomp accordingly.
In theory, I agree with you. Unfortunatel
Am 18.11.2015 um 09:57 schrieb Singer Michael:
> Package: systemd
> Version: 227-3
> Severity: normal
>
> Dear Maintainer,
>
> When changing the target you will be logged out automatically, for example,
> with the following command on a text console:
>
> # systemctl isolate multi-user.target
>
Hi
Am 19.11.2015 um 02:32 schrieb Daniel Baumann:
> On 11/18/2015 09:22 PM, Michael Biebl wrote:
>> Unfortunately, bumping the build-depends on
>> libseccomp-dev has no effect. The generated dependency on libseccomp2
>> would still be the same.
>
> True, but when b
Am 19.11.2015 um 08:21 schrieb Martin Pitt:
> Control: tag -1 pending
>
> Hello Daniel,
>
> Daniel Baumann [2015-11-19 2:32 +0100]:
>> True, but when building systemd on a system with too old libseccomp,
>> e.g. when backporting systemd to jessie, it FTBFS.
>
> Ah, that's a good reason to bump
Am 19.11.2015 um 10:35 schrieb Daniel Baumann:
> On 11/19/2015 10:18 AM, Michael Biebl wrote:
>> I don't expect the failure is because the lib was moved to /lib.
>
> it does. dh_shlibdeps bails with 'something is depending on /usr' which
> in that case is l
Am 19.11.2015 um 11:20 schrieb Martin Pitt:
> Just to conclude this for the mail archives: This has been resolved
> upstream in 228. networkd now only enables forwarding, never disables
> it, so the global control is back working:
>
> https://github.com/poettering/systemd/commit/765afd5c4dbc
\
Am 19.11.2015 um 14:29 schrieb Felipe Sateler:
> Control: tags -1 moreinfo
>
> On 19 November 2015 at 09:59, Lorenz Hübschle-Schneider
> wrote:
>> Package: systemd
>> Version: 228-1
>> Severity: critical
>> Justification: breaks the whole system
>>
>> Dear Maintainer,
>>
>> after the upgrade to s
Am 19.11.2015 um 14:54 schrieb Lorenz Hübschle-Schneider:
> I will try re-upgrading later this afternoon and let it run for a longer
> time, but the message was "$x sec / no limit".
>
> Felipe, are you referring to /usr/lib/tmpfiles.d/home.conf? I will try that
> out as well.
>
> With a normal mo
Am 19.11.2015 um 15:16 schrieb Michael Biebl:
> I can confirm, that with 227, "v /home" does not trigger a mount request
> and with 228 "Q /home" does.
Both q and Q trigger a mount request.
--
Why is it that all of the instruments seeking intelligent life in the
univ
Control: forwarded -1 https://github.com/systemd/systemd/issues/1959
Am 19.11.2015 um 15:18 schrieb Michael Biebl:
> Am 19.11.2015 um 15:16 schrieb Michael Biebl:
>> I can confirm, that with 227, "v /home" does not trigger a mount request
>> and with 228 "Q /home"
Control: severity -1 important
Am 19.11.2015 um 15:16 schrieb Michael Biebl:
> Btw, how do you configure your network? NetworkManager or ifupdown?
I tried with NetworkManager.
This resulted in systemd-tmpfiles-setup.service and srv.mount failing
during boot (I setup /srv as NFS automo
Am 19.11.2015 um 15:42 schrieb Michael Biebl:
> The boot did continue after 90 seconds though
> https://people.debian.org/~biebl/Debian%20Stretch.webm
>
> Given that, I'm downgrading the severity.
I just realized, that you use systemd-networkd and
systemd-networkd-wait-online.
Control: forwarded -1 https://github.com/systemd/systemd/issues/1961
Am 19.11.2015 um 16:13 schrieb Julian Brost:
> I've built systemd 228-1 with that patch removed and I could still
> reproduce the problem.
>
> I could also reproduce it on Arch Linux with systemd 227, so the issue
> isn't specif
Am 19.11.2015 um 17:16 schrieb Singer Michael:
> Reproducible steps (variant 1):
> 1. system is booted into the grahical.target (including login on KDE desktop)
> 2. With the key combination CTRL-ALT-F1 switch to the text console (tty)
> 3. Login as root on the system
> 4. "systemctl isolate multi-
Am 19.11.2015 um 18:22 schrieb Singer Michael:
> What else can I do to turn-off this behavior? It had until a few days ago
> still works, ie I was not logged out of the execution of the command
> "systemctl isolate multi-user.target".
With which systemd version did it still work?
--
Why is it
Hi Zbigniew,
just saw [1].
I don't think we are going to rename the udev package in Debian, but
once the package split is done in Fedora, I'll add a
Provides: systemd-udev
to th Debian udev package to improve the cross-distro experience.
Regards,
Michael
[1]
https://lists.fedoraproject.org/pipe
Am 20.11.2015 um 10:44 schrieb Andreas Krüger:
> Package: systemd
> Version: 215-17+deb8u2
> Severity: normal
>
> Dear maintainers,
>
> summary: Permission problem with files created
> below /var/log/journal, systemd-journal group
> cannot read.
>
> Details:
>
> On this Jessie system, as a user
Am 20.11.2015 um 12:39 schrieb Arturo Borrero Gonzalez:
> nov 20 12:16:31 cfdev02 systemd[1]: conntrackd.service: Main process
> exited, code=killed, status=6/ABRT
> nov 20 12:16:31 cfdev02 systemd[1]: conntrackd.service: Changed
> stop-sigabrt -> failed
It seems your process aborted and you don't
Am 20.11.2015 um 13:13 schrieb Michael Biebl:
> Am 20.11.2015 um 12:39 schrieb Arturo Borrero Gonzalez:
>> nov 20 12:16:31 cfdev02 systemd[1]: conntrackd.service: Main process
>> exited, code=killed, status=6/ABRT
>> nov 20 12:16:31 cfdev02 systemd[1]: conntrackd.service: Ch
Am 20.11.2015 um 12:52 schrieb Michael Biebl:
>
> How exactly did you create the /var/log/journal directory?
Can you also send us the output of
ls -la /var/log/journal
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from
Am 20.11.2015 um 13:16 schrieb Arturo Borrero Gonzalez:
> On 20 November 2015 at 13:13, Michael Biebl wrote:
>> Am 20.11.2015 um 12:39 schrieb Arturo Borrero Gonzalez:
>>> nov 20 12:16:31 cfdev02 systemd[1]: conntrackd.service: Main process
>>> exited, code=killed, sta
Am 20.11.2015 um 12:39 schrieb Arturo Borrero Gonzalez:
> I've noticed some inconsistend behaviour when a service is using
> Restart=on-watchdog.
Btw, please consider raising this issue upstream either as a question on
the mailing list or via the bug tracker
https://github.com/systemd/systemd/iss
Control: forwarded -1 https://github.com/systemd/systemd/issues/1969
Am 19.11.2015 um 19:32 schrieb Singer Michael:
> Hi Michael,
> the new version 228-2 has the error unfortunately not changed.
I looked into this a bit further.
Afaics, this is a regression that was introduced in v227 by commit
8
Am 23.10.2015 um 17:43 schrieb Stephan Sürken:
> So yes, for a non-existing script, that's (changed behaviour) but
> correct.
>
> For the example wicd service however, it should ignore the call like
> before, afaiu.
I think so as well. Could you please raise this issue upstream at
https://github.
Control: tags -1 pending
Am 20.11.2015 um 13:46 schrieb John Paul Adrian Glaubitz:
> Thus, src:systemd should build-depend on elfutils >= 0.158, the last
> successful
> build of elfutils on sparc64 was 0.157-3 which is why the missing versioned
> build dependency became visible.
http://anonscm.d
Am 20.11.2015 um 12:52 schrieb Michael Biebl:
>
> How exactly did you create the /var/log/journal directory?
Fwiw, I will clarify the documentation in /usr/share/doc/README.Debian,
that the /var/log/journal directory should be created 2755
root:systemd-journal
The set-group ID ensure
Hi,
kdbus has recently been removed from Fedora [1].
Upstream wants to rethink kdbus. Aiui, plans are to move more
functionality (and old dbus1 compat) into userspace.
I suggest we remove the kdbus-dkms package from experimental until we
know more and there is actually new code.
Objections/thoug
Am 27.10.2015 um 21:54 schrieb Cyril Brulebois:
> Michael Biebl (2015-10-27):
>> I've CCed debian-b...@lists.debian.org, debia...@lists.debian.org and
>> pkg-systemd-maintainers@lists.alioth.debian.org . Please CC them on
>> replies.
>>
>> I especially wou
Control: tags -1 + moreinfo
Am 21.11.2015 um 06:30 schrieb Brian Minton:
> Package: systemd
> Version: 228-2
> Severity: normal
>
> Dear Maintainer,
>
> When my system starts up, it starts up mdadm RAID devices, then seems to
> shut down some of them (at least I see something like that as the
> m
Am 21.11.2015 um 06:30 schrieb Brian Minton:
> Package: systemd
> Version: 228-2
> Severity: normal
>
> Dear Maintainer,
>
> When my system starts up, it starts up mdadm RAID devices, then seems to
> shut down some of them (at least I see something like that as the
> messages scroll by), then tri
Control: severity -1 wishlist
Control: tags -1 moreinfo
Am 21.11.2015 um 23:22 schrieb Denis Danilov:
> Package: systemd
> Version: 227-2
> Severity: normal
>
> Dear Maintainer,
>
> please add the binaries from ntpdate package to the "list of another NTP
> daemon installed"
> in the systemd-tim
Am 22.11.2015 um 00:31 schrieb Denis Danilov:
> Dear Michael
>
> during the boot I see that both timesyncd and ntpdate do the sync almost at
> the same time, like
>
> Nov 21 22:39:40 debian systemd-timesyncd[599]: Synchronized to time server
> 82.197.188.130:123 (3.debian.pool.ntp.org).
> Nov 2
Hi
Am 22.11.2015 um 14:20 schrieb Denys:
> systemd-nspawn[2798]: Failed to open root file system: Too many levels of
> symbolic links
..
> It have becomes after i install linux-image-4.3.0-trunk-amd64
Are you saying, this worked with older kernel versions?
--
Why is it that all of the instrume
Am 22.11.2015 um 21:13 schrieb Nikita Youshchenko:
> System uses fakeraid (configured in BIOS) - two disks in a mirror.
> In linux it is enabled via dmraid.
> Partitions are visible as /dev/mapper/jmicron_Main[1-4].
>
> /dev/mapper/jmicron_Main2 is used for swap
> /dev/mapper/jmicron_Main3 is use
Control: forwarded -1 https://github.com/systemd/systemd/issues/2001
Control: severity -1 normal
Am 22.11.2015 um 14:20 schrieb Denys:
> Package: systemd-container
> Version: 228-2
> Severity: important
>
> Dear Maintainer,
>
> machinectl start #containername# fails when /var/lib/machines/#conta
Hi Josh
Am 24.11.2015 um 06:53 schrieb Josh Triplett:
> Package: systemd
> Version: 228-2
> Severity: wishlist
>
> /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
> disables systemd-timesyncd if /usr/sbin/ntpd (or another NTP daemon)
> exists. However, nothing causes
Control: tags -1 + moreinfo
On Mon, 24 Nov 2014 22:08:47 +0100 Nils Dagsson Moskopp
wrote:
> For reasons I still do not understand, systemd was unable to mount
> /boot as ext2. I have been unable to make the Linux kernel load the
> ext2 module â modprobe exited zero, but lsmod did not show the
Hi everyone,
a few days ago, I filed bug reports against packages which declare an
explicit dependency on the initscripts package [1] and asked them to
remove it.
My assumption back then was, that this dependency was mainly added for
the /run-transition and could be dropped now easily.
Unfortunat
Am 24.11.2015 um 19:32 schrieb Petter Reinholdtsen:
> [Michael Biebl]
>> a/ Pere suggested to turn the Required- dependencies into Should-
>> dependencies. This means, as long as initscripts is not installed,
>> insserv does not fail, but potentially calculates a wrong ord
Am 24.11.2015 um 19:44 schrieb Michael Biebl:
> Am 24.11.2015 um 19:32 schrieb Petter Reinholdtsen:
>> [Michael Biebl]
>>> a/ Pere suggested to turn the Required- dependencies into Should-
>>> dependencies. This means, as long as initscripts is not installed,
>
Am 24.11.2015 um 19:32 schrieb Petter Reinholdtsen:
> The reason I do not like this is that insserv do not know about package
> names and only do know about the dependency format and derive everything
> from there. I believe it is a mistake to hardcode script names into
> insserv. I also believe
Am 24.11.2015 um 19:37 schrieb Felipe Sateler:
> e/ Patch insserv to look for a flag file/setting somewhere in
> /etc/insserv{,.conf.d}, which causes it to treat Required-* as Should*
> (ie, conffile-version of --force). Then initscripts could ship such a
> configuration, thus demoting dependencies
Am 24.11.2015 um 19:59 schrieb Michael Biebl:
> Am 24.11.2015 um 19:37 schrieb Felipe Sateler:
>> e/ Patch insserv to look for a flag file/setting somewhere in
>> /etc/insserv{,.conf.d}, which causes it to treat Required-* as Should*
>> (ie, conffile-version of --force). T
Thanks for the suggestions, Felipe!
Am 24.11.2015 um 19:37 schrieb Felipe Sateler:
> f/ Patch update-rc.d to use --force when initscripts is not installed.
>
> These two options have the added advantage of not relying on the
> active init, and thus could work while switching to sysvinit in the
>
Am 24.11.2015 um 21:29 schrieb Michael Biebl:
> Thanks for the suggestions, Felipe!
>
> Am 24.11.2015 um 19:37 schrieb Felipe Sateler:
>> f/ Patch update-rc.d to use --force when initscripts is not installed.
What check did you have in mind here? Testing for a (conf)file
Am 24.11.2015 um 22:25 schrieb Petter Reinholdtsen:
> [Felipe Sateler]
>> That would potentially leave initscripts with wrong ordering, thus
>> breaking a boot back to sysvinit (via syvinit package).
>
> My guess is that this would not happen if the initscripts package is
> installed before trying
Hi Guillem!
On Sun, 18 Oct 2015 03:40:50 + Guillem Jover wrote:
> Control: tag 801156 pending
>
> Hi!
>
> Bug #801156 reported by you has been fixed in the Git repository. You can
> see the changelog below, and you can check the diff of the fix at:
>
> https://anonscm.debian.org/cgit/d
Am 25.11.2015 um 00:06 schrieb Felipe Sateler:
> +# This enables inistcripts-less systems to not fail when a
Aside from the typo, lgtm.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digita
Am 25.11.2015 um 00:06 schrieb Felipe Sateler:
> On 24 November 2015 at 18:57, Felipe Sateler wrote:
>> On 24 November 2015 at 18:28, Michael Biebl wrote:
>>> Am 24.11.2015 um 22:25 schrieb Petter Reinholdtsen:
>>>> [Felipe Sateler]
>>>>> That w
Am 11/25/2015 um 10:20 PM schrieb Francesco Poli (wintermute):
> Package: libpam-systemd
> Version: 228-2
> Severity: normal
>
> Hello,
> I noticed a weird bug that is possibly caused by libpam-systemd.
>
> Steps to reproduce (on a box with systemd as PID 1 process):
>
1..7
Tried those steps b
Am 26.11.2015 um 09:53 schrieb Mattia Belluco:
> Package: systemd
> Version: 228-2
> Arch: amd64
>
> If bluetooth is disabled by soft rfkill (blueman applet) the status
> survives reboot and systemd no longer loads bluetoothd (which in turn
> prevent blueman from loading) because:
>
> ● bluetooth
Am 26.11.2015 um 08:00 schrieb Eduard Bloch:
> Package: systemd
> Version: 228-2
>
> Dear Maintainer,
>
>* What led up to the situation?
>
> I created a buggy configuration of apt-cacher-ng and wondered why it did not
> start. When I run the service from command line, it dumps a couple of u
Control: tags -1 + moreinfo
Am 26.11.2015 um 16:04 schrieb Thomas Schmidt:
> Package: systemd
> Version: 228-2
> Severity: important
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate ***
>
>* What led up to the situation?
>
> Booting has to
Am 26.11.2015 um 15:59 schrieb Michael Biebl:
> Works here. But I actually need a service which produces more then 10
> lines of output when started.
To illustrate what I did:
# cat /etc/systemd/system/output.service
[Unit]
Description=foo
[Service]
Type=oneshot
ExecStart=/bin/sh -c &qu
Am 27.11.2015 um 00:16 schrieb Francesco Poli:
> On Thu, 26 Nov 2015 00:06:56 +0100 Michael Biebl wrote:
>
>> Am 11/25/2015 um 10:20 PM schrieb Francesco Poli (wintermute):
>>> Package: libpam-systemd
>>> Version: 228-2
>>> Severity: normal
>>&
Might have been a red herring
Am 28. November 2015 15:36:12 MEZ, schrieb Martin Pitt :
>Hey Michael,
>
>Michael Biebl [2015-09-24 18:32 +0200]:
>> Am 24.09.2015 um 17:46 schrieb hannu@pp.inet.fi:
>> > This works for me:
>> >
>> > copy /lib/sys
Am 28.11.2015 um 19:23 schrieb Francesco Poli:
> Please tell me whether you need any further information in order to
> investigate. Otherwise, please drop the moreinfo tag.
So far I don't know yet, how I can reproduce the problem. So I'll keep
the moreinfo tag.
--
Why is it that all of the in
Am 29.11.2015 um 00:12 schrieb Manuel Bilderbeek:
> How can I help?
Describe your setup in as much detail as possible. LVM, RAID, fstab etc.
Can you reproduce the issue with arbitrary mounts?
Can you reproduce the issue with a minimal setup? On a different system?
Do you have any hints how we can
Control: tags -1 + moreinfo
Am 02.12.2015 um 21:12 schrieb Jose Luis Tallon:
> Package: udev
> Version: 215-17+deb8u2
> Severity: normal
>
> Dear Maintainer,
>
>After upgrading a system from wheezy+backports to jessie,
> udev/systemd-udev
> (upgraded to systemd+newer udev) has stopped renami
Am 02.12.2015 um 20:30 schrieb Mattia Belluco:
> On 11/26/2015 04:01 PM, Michael Biebl wrote:
>> Am 26.11.2015 um 09:53 schrieb Mattia Belluco:
>> I'm confused, why is this a bug in particular (you disabled bluetooth)
>> and systemd specifically (bluetooth.service
Am 02.12.2015 um 22:15 schrieb Jose Luis Tallon:
> The ethernet interfaces were not renamed at boot, and left as eth0-eth9.
> During boot, systemd actually reported those names (eth0-eth9) when
> configuring networking.
Please boot with "udev.log-priority=debug" on the kernel command line
and then
Am 02.12.2015 um 23:35 schrieb Michael Biebl:
> Am 02.12.2015 um 22:15 schrieb Jose Luis Tallon:
>> The ethernet interfaces were not renamed at boot, and left as eth0-eth9.
>> During boot, systemd actually reported those names (eth0-eth9) when
>> configuring networking.
Control: severity -1 normal
Control: tags -1 moreinfo
Hi
Am 03.12.2015 um 03:02 schrieb Juhapekka Tolvanen:
>
> juhtolv@heresy | to 03 joulu 2015 03:52:26 | 1 | pts/1.1
> /home/juhtolv
> % systemctl --user status --all
> Failed to get D-Bus connection: Yhteys torjuttu
What's the output (as
Am 03.12.2015 um 09:23 schrieb Juhapekka Tolvanen:
> juhtolv@heresy | to 03 joulu 2015 04:04:14 | 10002 | pts/15
> /home/juhtolv
> % ps ux|grep systemd
> juhtolv829 0.0 0.2 4960 3556 ?Ss 03:51 0:00
> /lib/systemd/systemd --user
> juhtolv 7689 0.0 0.1 6292 2136 pts/15
Hi Guus
Am 03.12.2015 um 13:44 schrieb Guus Sliepen:
> On Thu, Dec 03, 2015 at 01:06:01PM +0100, Martin Pitt wrote:
>
>> many thanks for adding a native networking.service! Michael and I
>> found some corrections and tweaks to be made,
>
> Thanks for having a look at it. I'm still quite new to S
Am 03.12.2015 um 10:04 schrieb Juhapekka Tolvanen:
>
> On Thu, 03 Dec 2015, +10:37:51 EET (UTC +0200),
> Michael Biebl pressed some keys:
>
>> Is the problem reproducible after a reboot/relogin?
>
> Problem is reproducible after reboot. But then I tried something
> d
Am 03.12.2015 um 15:08 schrieb Martin Pitt:
>
> Guus Sliepen [2015-12-03 13:44 +0100]:
>>>In the medium term I'd be interested in cleaning this up, though.
>>>IMHO there needs to be a proper ifupdown-wait-online.service which
>>>just starts the virtual interfaces, let all the real one
Am 04.12.2015 um 09:35 schrieb Martin Pitt:
> Hello,
>
> Michael Biebl [2015-12-03 21:38 +0100]:
>>>> Yes. The only problem though is that it requires the admin to correctly
>>>> specify which interfaces are "auto" and which are "hotplug"
Am 04.12.2015 um 13:44 schrieb George B.:
> Package: systemd
> Version: 228-2
> Severity: important
>
> Hello,
>
> As of a few weeks ago (after an update) my laptop started auto-suspending
> after a period
> of inactivity. I assume this is logind related because I couldn't find
> anything else o
Hi
Am 07.12.2015 um 01:14 schrieb Dhionel Díaz:
>
> [Socket]
> ListenStream = 30865
> Accept = true
>
> [Install]
> WantedBy = sockets.target
>
>
> csync2@.service
>
>
> [Unit]
> Description = csyn2 asynchronous file synchronization
Typo, csyn'c'2
Also, please don't use spaces, but
Descrip
Am 08.12.2015 um 00:30 schrieb George B.:
> On 04/12/15 14:39, Michael Biebl wrote:
>>
>> Can you attach the output of (as root)
>> journalctl -u systemd-logind
>>
>> and mark the time when the auto-suspend happens.
>
> ```
> -- Logs begin at Mon 2015
Hi
Am 09.12.2015 um 17:18 schrieb Benjamin Drung:
> Package: python-systemd
> Version: 231-1
> Severity: normal
> Tags: patch
>
> Hi,
>
> salt 2015.8.3+ds-1 requires python-systemd since it does not yet support
> Python 3.
Is that process tracked somewhere?
We deliberately dropped python-system
Am 10.12.2015 um 00:55 schrieb Samuel Thibault:
> Eric Cooper, on Thu 19 Nov 2015 13:31:57 -0500, wrote:
>> While booting, it looks like the font switches from VGA to Terminus
>> during the boot messages. But then the screen is cleared and the
>> getty login prompts are back in VGA. If I run "set
Am 10.12.2015 um 00:55 schrieb Samuel Thibault:
> Eric Cooper, on Thu 19 Nov 2015 13:31:57 -0500, wrote:
>> While booting, it looks like the font switches from VGA to Terminus
>> during the boot messages. But then the screen is cleared and the
>> getty login prompts are back in VGA. If I run "set
Am 10.12.2015 um 03:47 schrieb Michael Biebl:
> ACTION=="add", SUBSYSTEM=="vtconsole", KERNEL=="vtcon*",
> RUN+="/bin/setupcon"
Unfortunate wrapping by the MUA.
This should be in one line, no line break:
ACTION=="add", SUBSYSTEM=="vt
Am 07.12.2015 um 13:31 schrieb Guus Sliepen:
> Now that we have a proper systemd service
> for ifupdown, could we just add WantedBy=network-online.target to
> networking.service? The only difference to me seems that your script
> waits until ifup has configured at least one interface, while the si
Am 10.12.2015 um 15:12 schrieb Guus Sliepen:
> On Thu, Dec 10, 2015 at 01:59:42PM +0100, Michael Biebl wrote:
>> The benefit here is, that other services, that don't need
>> network-online.target would not be blocked unnecessarily during boot.
>
> I don't understan
Control: severity -1 minor
Am 11.12.2015 um 11:21 schrieb Andreas Beckmann:
> during a test with piuparts I noticed your package left unowned files on
> the system after purge, which is a violation of policy 6.8 (or 10.8):
>
> https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-
Am 11.12.2015 um 11:40 schrieb Michael Biebl:
> That means someone called "update-rc.d udev disable".
>
> The udev package itself doesn't do that afaics. Can you find out who?
>
> I'm not convinced that the package itself should clean that up.
From a cursory
Control: tags -1 moreinfo
Am 11.12.2015 um 16:00 schrieb Salvo Tomaselli:
> Package: systemd
> Version: 228-2
> Severity: normal
>
> Dear Maintainer,
>
> doing
>> service xdm restart
>
> inside a graphic session will terminate Xorg but not restart.
>
> Systemd was supposed to solve this issue
Am 11.12.2015 um 16:29 schrieb Salvo Tomaselli:
>> I'm not sure why xdm should behave differently under systemd. After all,
>> it only ships a SysV init script atm.
>
> if "service xdm restart" is run directly by systemd rather than within
> the session, it would not
> kill itself and would keep w
Am 12.12.2015 um 17:31 schrieb Sanjoy Mahajan:
> A bunch of reasonably important iceweasel-downloaded .pdf files in /tmp
> suddenly disappeared. I feared that I had misconfigured the
> /etc/tmpfiles.d/tmp.conf and allowed automatic cleaning, but that file
> was correct (prevented /tmp cleaning):
On Sun, 13 Dec 2015 17:45:51 +0100
=?ISO-8859-1?Q?J=F6rg_Frings-F=FCrst?= wrote:
> Hello Daniel,
>
> thank you for spending your time helping to make Debian better with
> this bug report. Â
>
> I think after some tests, that this bug is based in a wrong handling
> from udev.
Care to elaborate
Am 13.12.2015 um 20:12 schrieb Sanjoy Mahajan:
> Michael Biebl writes:
>
>> Have you read the comments in /etc/tmpfiles.d/tmp.conf ?
>> You previously already had tmpfs-on-/tmp under sysvinit as you've set it
>> in /etc/default/rcS.
>
> I don't think so.
Am 14.12.2015 um 15:20 schrieb Roger Shimizu:
> Dear systemd maintainers,
>
> Thanks for helping for the adjtimex systemd service file last time.
> I write again because I find an issue related to the service file.
>
> When installing, adjtimex's postinst script will ask user whether to
> start t
Am 14.12.2015 um 16:19 schrieb Roger Shimizu:
> On Mon, Dec 14, 2015 at 11:57 PM, Felipe Sateler wrote:
>> Another option is to simply not enable/start the service, and just
>> ship instructions on how to do that in README.Debian.
>>
>> Running it on postinst looks weird to me. We normally do not
Am 14.12.2015 um 16:26 schrieb Michael Biebl:
> You could check for the existence of a config file in your sysv init
> script and simply exit if it doesn't exist.
> Under systemd the equivalent is a ConditionPathExists=/etc/foobar.conf
Fwiw, the rsync package is comparable to you
Am 14.12.2015 um 16:35 schrieb Roger Shimizu:
> On Tue, Dec 15, 2015 at 12:29 AM, Michael Biebl wrote:
>> Am 14.12.2015 um 16:26 schrieb Michael Biebl:
>>> You could check for the existence of a config file in your sysv init
>>> script and simply exit if it doesn
Control: reassign -1 shotwell
Am 13.12.2015 um 17:54 schrieb Michael Biebl:
> On Sun, 13 Dec 2015 17:45:51 +0100
> =?ISO-8859-1?Q?J=F6rg_Frings-F=FCrst?= wrote:
>> Hello Daniel,
>>
>> thank you for spending your time helping to make Debian better with
>> this bug
Am 16.12.2015 um 12:16 schrieb Anton Zinoviev:
> On Thu, Dec 10, 2015 at 03:47:24AM +0100, Michael Biebl wrote:
>>
>> $ cat /etc/udev/rules.d/90-setupcon.rules
>> ACTION=="add", SUBSYSTEM=="vtconsole", KERNEL=="vtcon*",
>> RUN+="/bin
Am 16.12.2015 um 15:16 schrieb Anton Zinoviev:
> On Wed, Dec 16, 2015 at 02:22:49PM +0100, Michael Biebl wrote:
>>
>> Wouldn't be hard to add this check to setupcon itself.
>
> Setupcon is a portable script that can be used on any distribution ---
> Debian or n
Am 16.12.2015 um 15:28 schrieb Anton Zinoviev:
> On Wed, Dec 16, 2015 at 03:21:22PM +0100, Michael Biebl wrote:
>> I don't see why this check would make it init system dependend or
>> dependend on Debian specifics.
>
> I was talking about the following check: whether in
Am 16.12.2015 um 15:43 schrieb Frank B. Brokken:
> Package: systemd
> Version: 228-2
> Severity: critical
> Justification: breaks the whole system
>
> Dear Maintainer,
>
>* What led up to the situation?
>
> Last week, Tuesday Dec. 8 I upgraded this system. One of the packages that
> were upg
Am 17.12.2015 um 13:46 schrieb Frank B. Brokken:
> Dear Michael Biebl, you wrote:
>
>> What happens afterwards? Are you dropped into the rescue shell?
>
> Afterwards (i.e., after the initial failure message) the system tries to
> continue booting, but shows lots of failure
Control: severity -1 normal
Control: tags -1 upstream
Hi
Am 17.12.2015 um 13:06 schrieb Matthias Urlichs:
> Package: systemd-container
> Version: 227-2
> Severity: important
> File: /usr/bin/systemd-nspawn
>
> systemd-nspawn --link-journal=host should accept an existing directory.
>
Please tes
Am 17.12.2015 um 16:24 schrieb Frank B. Brokken:
> This time the debug shell prompt was available at tty9, although booting
> failed. And in line with my previous findings, systemd-analyze and journalctl
> weren't available, as they live in /usr/bin, and /usr hadn't been mounted. But
Well, /usr is
Am 17.12.2015 um 22:38 schrieb Michael Biebl:
> Am 17.12.2015 um 16:24 schrieb Frank B. Brokken:
>> This time the debug shell prompt was available at tty9, although booting
>> failed. And in line with my previous findings, systemd-analyze and journalctl
>> weren't avail
901 - 1000 of 2654 matches
Mail list logo
