On Fri, Apr 20, 2012 at 04:11:16PM +0300, Teodor MICU wrote:
> 2012/4/20 Michael Vogt :
> > Sure, the setsid() call makes the process a session leader and removes
> > the controlling tty. The rational is that if you run
> > unattended-upgrades in a shell and then shutdown your tty goes away
> > and
2012/4/20 Michael Vogt :
> Sure, the setsid() call makes the process a session leader and removes
> the controlling tty. The rational is that if you run
> unattended-upgrades in a shell and then shutdown your tty goes away
> and unattended-upgrades gets killed even if its in the middle of a
> opera
On Fri, Apr 20, 2012 at 12:57:29PM +0300, Teodor MICU wrote:
> 2012/4/20 Michael Vogt :
> > Thanks for your bugreport. I fixed that now. I guess in your case it
> > was already the session-leader for some reason (maybe because of
> > systemd?).
>
> Yes, I use «systemd» but I don't know what being
2012/4/20 Michael Vogt :
> Thanks for your bugreport. I fixed that now. I guess in your case it
> was already the session-leader for some reason (maybe because of
> systemd?).
Yes, I use «systemd» but I don't know what being session-leader means.
Most times u-a is run automatically by Cron, only w
B1;3100;0cOn Fri, Apr 20, 2012 at 08:48:49AM +0300, Teodor wrote:
> Package: unattended-upgrades
> Version: 0.76.1
> Severity: grave
> Justification: renders package unusable
>
> Hi,
>
> The os.setsid() changes makes u-a abort on every invocation:
> | root@r2:~# unattended-upgrade
> | Tra
One important detail: I use «systemd», so this might not be a bug in U-A.
Thaks
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: unattended-upgrades
Version: 0.76.1
Severity: grave
Justification: renders package unusable
Hi,
The os.setsid() changes makes u-a abort on every invocation:
| root@r2:~# unattended-upgrade
| Traceback (most recent call last):
| File "/usr/bin/unattended-upgrade", line 913, in
7 matches
Mail list logo
