-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marc MERLIN schrieb:
> But sure enough, it seems to have worked.
> I.e. your patch seems to have fixed the SEGV I was seeing.
Thanks for testing the patch. I just uploaded libpam-mount 0.18-4 with
the patch applied.
Regards,
Bastian
- --
,''`.
On Thu, Dec 07, 2006 at 10:51:26PM +0100, Bastian Kleineidam wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Marc MERLIN schrieb:
> > Indeed. 0.12 was the latest in my distro, but I downloaded the latest 0.18
> > from packages.debian.org/testing/ and I still have the same problem
> Yo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marc MERLIN schrieb:
> Indeed. 0.12 was the latest in my distro, but I downloaded the latest 0.18
> from packages.debian.org/testing/ and I still have the same problem
You normally don't need to use pam_mount together with su. If you do,
there unfortun
On Tue, Dec 05, 2006 at 09:22:31PM +0100, Bastian Kleineidam wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Marc MERLIN schrieb:
> > cron (Version: 3.0pl1-87ubuntu2) / libpam-mount (0.12.0-1ubuntu1)
> Please try a newer version of pam_mount. The current one is 0.18, which
> has a lot
Package: cron
Version: 3.0pl1-87
libpam-mount makes cron segfault each time it forks off a child to run
tasks if it's built with pam support.
strace -f cron -f shows
[pid 3298] setrlimit(RLIMIT_AS, {rlim_cur=RLIM_INFINITY,
rlim_max=RLIM_INFINITY}) = 0
[pid 3298] setrlimit(RLIMIT_LOCKS, {rlim_
5 matches
Mail list logo