Bug#803013: systemd should not destroy application created cgroups

On Fri, Nov 13, 2015 at 11:36:30AM +1100, paul.sz...@sydney.edu.au wrote: > Progress? For my efforts upstream, I got the comment: > > > Sorry, but systemd implements a single-writer cgroup logic (as > > requested by the kernel maintainers), and hence takes possesion of the > > whole tree. ... > >

Re: How to have an /etc/xdg/autostart/app.desktop service wait for a (systemd) service?

Hi Michael, Michael Biebl wrote (12 Nov 2015 13:35:55 GMT) : > Am 12.11.2015 um 14:29 schrieb Patrick Schleizer: >> I have an app started by `/etc/xdg/autostart/app.desktop` that requires >> a systemd service to be started first. > The only proper way to do this "right" would be to have a systemd

Bug#803013: systemd should not destroy application created cgroups

On Fri, Nov 13, 2015 at 12:50:57PM +0100, Julian Andres Klode wrote: > On Fri, Nov 13, 2015 at 11:36:30AM +1100, paul.sz...@sydney.edu.au wrote: > > Progress? For my efforts upstream, I got the comment: > > > > > Sorry, but systemd implements a single-writer cgroup logic (as > > > requested by the

Bug#788788: marked as done (add efivars automount fix to Jessie)

Your message dated Fri, 13 Nov 2015 16:01:45 +0100 with message-id <5645fb59.7010...@debian.org> and subject line Re: Bug#788788: add efivars automount fix to Jessie has caused the Debian Bug report #788788, regarding add efivars automount fix to Jessie to be marked as done. This means that you cl

Bug#756109: systemd: Please copy 70-uaccess.rules and 71-seat.rules in the initramfs

On Sun, 29 Mar 2015 05:30:23 +0200 m...@linux.it (Marco d'Itri) wrote: > On Jul 26, Laurent Bigonville wrote: > > > Do you think that it could be possible to copy 70-uaccess.rules and > > 71-seat.rules (and maybe 73-seat-late.rules) in the initramfs? > Adding 70-uaccess.rules is easy, but 71-seat

Bug#805042: journal is killed every minute by watchdog

Package: systemd Version: 227-3 Severity: important Since updating to 227-3, I get the following message every minute Nov 13 18:23:28 pluto systemd-journald[25893]: System journal (/var/log/journal/) is currently using 808.1M. Maximum allowed usage

Bug#719695: Prefer symlinks over Alias= for non-matching service names

Control: tags -1 upstream fixed-upstream Control: forwarded -1 https://github.com/systemd/systemd/pull/1515 On Mon, 03 Aug 2015 23:26:41 +0530 Ritesh Raj Sarraf wrote: > Package: systemd > Version: 223-2 > Followup-For: Bug #719695 > > Hello, > > I am hit by the same problem. > > So far, we've sh

Processed: Re: Prefer symlinks over Alias= for non-matching service names

Processing control commands: > tags -1 upstream fixed-upstream Bug #719695 [systemd] Prefer symlinks over Alias= for non-matching service names Added tag(s) fixed-upstream and upstream. > forwarded -1 https://github.com/systemd/systemd/pull/1515 Bug #719695 [systemd] Prefer symlinks over Alias= fo

Bug#769889: dconf-CRITICAL: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.

I just experienced this problem on Debian Jessie AMD64 with MATE. mate-panel process devoured 16GB of RAM and 15GB of swap, I had to reboot PC from terminal. on ~/.xsession-errors file I found never-ending stream of error messages: (mate-panel:1490): dconf-CRITICAL **: unable to create file '/run/

Bug#769889: dconf-CRITICAL: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.

Am 13.11.2015 um 23:42 schrieb pioruns: > I just experienced this problem on Debian Jessie AMD64 with MATE. > mate-panel process devoured 16GB of RAM and 15GB of swap, I had to > reboot PC from terminal. > on ~/.xsession-errors file I found never-ending stream of error messages: > (mate-panel:1490

Rappel

Cher client, Il s'est avéré nécéssaire d'une vérification récente des comptes de tous nos clients. Pour cela, il est important d'accéder à votre compte le plus tôt possible. Visitez votre espace client pour y accéder. Merci, LCL à votre service. _