> "MB" == Michael Biebl writes:
MB> Can you attach your /etc/fstab please and the file /run/systemd/was-enabled.
MB> Is there a file /etc/systemd/system/tmp.mount (or was in the past)?
UUID=355d426a-cbfc-4faf-91d6-4f9405199517 /home auto defaults,commit=111 0 2
UUID=34610b6a-70a3-48d9-b135-9
Martin Pitt:
> The option has already be reverted in the packaging git.
> This isn't an exercise in "who shouts the loudest".
It should, however, be an exercise in fixing bugs properly. (-:
Turning off the enabling flag doesn't fix the underlying flawed
mechanism. There is still a logind bug
Processing commands for cont...@bugs.debian.org:
> retitle 826045 systemd-boot: New kernels are not automatically added
Bug #826045 [systemd] systemd: New kernels are not booted
Changed Bug title to 'systemd-boot: New kernels are not automatically added'
from 'systemd: New kernels are not booted'
Processing control commands:
> tag -1 help
Bug #826045 [systemd] systemd: New kernels are not booted
Added tag(s) help.
--
826045: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826045
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
_
Control: tag -1 help
Michael Biebl [2016-06-01 22:39 +0200]:
> systemd-boot is not officially supported yet.
> We install the systemd-boot related files so users can play with them,
> but you are basically on your own.
>
> Maybe it's better to remove them.
>
> Martin, your thoughts?
If someone
Processing control commands:
> severity -1 wishlist
Bug #826045 [systemd] systemd: New kernels are not booted
Severity set to 'wishlist' from 'important'
--
826045: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826045
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
___
Control: severity -1 wishlist
Am 01.06.2016 um 22:25 schrieb Thomas Prokosch:
> After gummiboot has been integrated into systemd as systemd-boot, I
> decided to give this new feature a try and installed a new machine
> with systemd, not installing gummiboot or any other boot loader. The
> machine
Package: systemd
Version: 229-6
Severity: important
After gummiboot has been integrated into systemd as systemd-boot, I
decided to give this new feature a try and installed a new machine
with systemd, not installing gummiboot or any other boot loader. The
machine is capable of booting an UEFI stub
clone 816391 -1
reassign -1 systemd
retitle -1 systemctl status should propagate through PartOf
block 816391 -1
thanks
Michael Biebl schrieb am Donnerstag, dem 14. April 2016:
> Am 14.04.2016 um 00:46 schrieb Michael Biebl:
> > The tor.service afaics is only used, so you have a
> > systemctl resta
Processing commands for cont...@bugs.debian.org:
> clone 816391 -1
Bug #816391 [tor] tor: "systemctl status tor" does not provide useful output
Bug 816391 cloned as bug 826041
> reassign -1 systemd
Bug #826041 [tor] tor: "systemctl status tor" does not provide useful output
Bug reassigned from pac
Processing control commands:
> block 792894 by 826011 826012
Bug #792894 [isc-dhcp-server] systemd units for dhcp server (addressing ipv4
and ipv6)
792894 was not blocked by any bugs.
792894 was not blocking any bugs.
Added blocking bug(s) of 792894: 826012 and 826011
--
792894: http://bugs.deb
Package: systemd
Version: 230-2
Severity: normal
This message [1] identifies that compound target units are the
appropriate mechanism for controlling multiple service units.
The LSB override hook currently only consider .service units, ignoring
compound .target units.
Support for this would be u
Package: init-system-helpers
Version: 1.34
Severity: normal
This message [1] identifies that compound target units are the
appropriate mechanism for controlling multiple service units.
The sys-v compatibility helpers (service, {invoke,update}-rc.d,
debhelpers, et al.) currently only consider .ser
On 2016-06-01 11:35:42 +0200, Michael Biebl wrote:
> Am 01.06.2016 um 10:40 schrieb Vincent Lefevre:
>
> > This is part of one of my /etc/network/if-up.d scripts, where I have
> > "su vinc17 -c some_script" (which just does a rewrite of one of my
> > config files).
>
> You are involving the pam s
Your message dated Wed, 1 Jun 2016 11:35:42 +0200
with message-id
and subject line Re: Bug#825995: systemd: slow boot: pam_systemd(su:session):
Failed to create session: Connection timed out
has caused the Debian Bug report #825995,
regarding systemd: slow boot: pam_systemd(su:session): Failed to
On 2016-06-01 10:40:53 +0200, Vincent Lefevre wrote:
> which is new. Earlier in the logs:
>
> Jun 01 10:14:22 zira su[718]: Successful su for vinc17 by root
> Jun 01 10:14:22 zira systemd[1]: Reached target Sockets.
> Jun 01 10:14:22 zira su[718]: + ??? root:vinc17
> Jun 01 10:14:22 zira systemd[1
Package: systemd
Version: 230-2
Severity: important
As of systemd 230, the boot is much slower than before, which is
rather annoying. journalctl shows:
[...]
Jun 01 10:14:24 zira systemd[1]: Started Initialize hardware monitoring sensors.
Jun 01 10:14:24 zira systemd[1]: Starting LSB: lm-sensors
Processing commands for cont...@bugs.debian.org:
> severity 825981 minor
Bug #825981 [systemd] failure message upon install
Severity set to 'minor' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
825981: http://bugs.debian.org/cgi-bin/bugreport.cgi?b
Am 01.06.2016 um 08:51 schrieb Michael Biebl:
> Can you attach your /etc/fstab please and the file /run/systemd/was-enabled.
> Is there a file /etc/systemd/system/tmp.mount (or was in the past)?
I'm assuming there is an /tmp entry in /etc/fstab.
systemctl is-enabled in jessie vs stretch:
$ system
a self compiled Version of libcaf links perfectly. Also the example taken
from
https://raw.githubusercontent.com/actor-framework/actor-framework/0.13.2/examples/message_passing/dining_philosophers.cpp
is the same as the submitted example. So it seems it is related to the C++
ABI change. Maybe, the
20 matches
Mail list logo
