Re: Bug#765854: ecryptfs-utils: Private directory not automatically unmounted anymore on logout

On Sun, Jan 8, 2017 at 10:04 PM, Julian Andres Klode wrote: > On Sun, Jan 08, 2017 at 09:32:25PM +0100, Martin Pitt wrote: >> so the mount/unmount needs to be done by a PAM module >> (pam_ecryptfs). This works just fine in Ubuntu at least (I've used ecryptfs >> on >> my $HOME

Re: Bug#765854: ecryptfs-utils: Private directory not automatically unmounted anymore on logout

On Sun, Jan 08, 2017 at 09:32:25PM +0100, Martin Pitt wrote: > Julian Andres Klode [2017-01-08 19:13 +0100]: > > (1) Seems you install to lib/systemd/system - but the service would have to > > be > > in lib/systemd/user to work (it's a user service) > > That makes little sense IMHO -- the

Re: Bug#765854: ecryptfs-utils: Private directory not automatically unmounted anymore on logout

Julian Andres Klode [2017-01-08 19:13 +0100]: > (1) Seems you install to lib/systemd/system - but the service would have to be > in lib/systemd/user to work (it's a user service) That makes little sense IMHO -- the systemd user instance needs to be able to see ~/.config/systemd/user/ at

Re: Bug#765854: ecryptfs-utils: Private directory not automatically unmounted anymore on logout

On Sun, Jan 08, 2017 at 08:25:01PM +0100, László Böszörményi (GCS) wrote: > On Sun, Jan 8, 2017 at 7:13 PM, Julian Andres Klode wrote: > > Two points: > > > > (1) Seems you install to lib/systemd/system - but the service would have to > > be > > in lib/systemd/user to work

Re: Bug#765854: ecryptfs-utils: Private directory not automatically unmounted anymore on logout

/usr/lib/systemd/user, please Am 8. Januar 2017 19:13:24 MEZ schrieb Julian Andres Klode : >On Sun, Jan 08, 2017 at 04:58:35PM +0100, László Böszörményi (GCS) >wrote: >> Hi Julian, >> >> On Fri, Jan 6, 2017 at 3:06 PM, Julian Andres Klode >wrote: >> > Second

Re: Bug#765854: ecryptfs-utils: Private directory not automatically unmounted anymore on logout

On Sun, Jan 08, 2017 at 04:58:35PM +0100, László Böszörményi (GCS) wrote: > Hi Julian, > > On Fri, Jan 6, 2017 at 3:06 PM, Julian Andres Klode wrote: > > Second ping, more than 2 years later. > > > > Seriously, that's more than 2 years old now, with a simple workaround, and > >

Re: Bug#765854: ecryptfs-utils: Private directory not automatically unmounted anymore on logout

On Sun, Jan 8, 2017 at 4:58 PM, László Böszörményi (GCS) wrote: > On Fri, Jan 6, 2017 at 3:06 PM, Julian Andres Klode wrote: >> Second ping, more than 2 years later. >> >> Seriously, that's more than 2 years old now, with a simple workaround, and >> security

Re: Bug#765854: ecryptfs-utils: Private directory not automatically unmounted anymore on logout

Hi Julian, On Fri, Jan 6, 2017 at 3:06 PM, Julian Andres Klode wrote: > Second ping, more than 2 years later. > > Seriously, that's more than 2 years old now, with a simple workaround, and > security implications (private data remaining accessible after logout). Sure, I don't

Processed: Re: Processed: Prepare for status update

Processing commands for cont...@bugs.debian.org: > # On 2017-01-08 Debian Bug Tracking System wrote: > # > Processing commands for cont...@bugs.debian.org: > # > # >> # temporarily unarchive to document current status > # >> # this still one of google's tophits for > # >>

Processed: Prepare for status update

Processing commands for cont...@bugs.debian.org: > # temporarily unarchive to document current status > # this still one of google's tophits for > # "systemd" tcp wrapper > unarchive 618409 Bug #618409 {Done: Tollef Fog Heen } [systemd] Enable TCP wrapper support Unarchived

Processing of systemd-cron_1.5.4-4_amd64.changes

systemd-cron_1.5.4-4_amd64.changes uploaded successfully to localhost along with the files: systemd-cron_1.5.4-4.dsc systemd-cron_1.5.4-4.debian.tar.xz systemd-cron-dbgsym_1.5.4-4_amd64.deb systemd-cron_1.5.4-4_amd64.buildinfo systemd-cron_1.5.4-4_amd64.deb Greetings, Your

Bug#850602: marked as done (systemd: Suspending the system takes long (>10sec))

Your message dated Sun, 8 Jan 2017 13:21:30 +0100 with message-id and subject line Re: Bug#850602: Acknowledgement (systemd: Suspending the system takes long (>10sec)) has caused the Debian Bug report #850602, regarding systemd: Suspending the

Bug#850602: systemd: Suspending the system takes long (>10sec)

Package: systemd Version: 232-8 Severity: normal Dear Maintainer, on my new laptop, suspending the machine takes pretty long (>10sec) compared to what I got sued to on my old machine (<3sec). I am not sure where the cuplrit is. Here's what the journal has to say for these 10 seconds: Jan 08