On Sat, 2020-02-01 at 22:39 +0100, Marc Lehmann wrote:
> On Sat, Feb 01, 2020 at 07:41:03AM +0800, Ian Kent
> wrote:
> > > decided that nobody should use symlinks as bind mounts are the
> > > future(tm).
> > > From an upstream POV it was more neglect (on my part) of the
> > symlink code in favour
On Sat, Feb 01, 2020 at 07:41:03AM +0800, Ian Kent wrote:
> > decided that nobody should use symlinks as bind mounts are the
> > future(tm).
>
> >From an upstream POV it was more neglect (on my part) of the
> symlink code in favour of bind mounts.
Not sure why you write this, but it's clearly no
On Fri, 2020-01-31 at 18:15 +0100, Marc Lehmann wrote:
> On Fri, Jan 31, 2020 at 07:16:14PM +0800, Ian Kent
> wrote:
> > It looks like this package has the change that adds handling of
> > symlinks to umount_multi() so this should not be calling umount()
> > at all.
>
> Ah, I tried to see if ther
Hi all,
On Fr 31 Jan 2020 18:24:42 CET, Marc Lehmann wrote:
On Fri, Jan 31, 2020 at 02:24:11PM +, Mike Gabriel
wrote:
Marc, as I get it, it would be welcome to get the discussed issue fixed in
Debian stable (aka buster). Right?
It would be convenient yes, but since I had to roll back
As added info, I installed 5.1.6 form tetsing on some of the affected
machines, and the problem is indeed gone, local filesystems don't randomly
get unmounted on autofs restarts or expires.
Thanks!
--
The choice of a Deliantra, the free code+content MORPG
-==-
On Fri, Jan 31, 2020 at 02:24:11PM +, Mike Gabriel
wrote:
> Marc, as I get it, it would be welcome to get the discussed issue fixed in
> Debian stable (aka buster). Right?
It would be convenient yes, but since I had to roll back the timeout
change (in my configs) anyway, I can live with the
On Fri, Jan 31, 2020 at 07:16:14PM +0800, Ian Kent wrote:
> It looks like this package has the change that adds handling of
> symlinks to umount_multi() so this should not be calling umount()
> at all.
Ah, I tried to see if there was a custom symlink patch in debians version,
but it seems to e in
Control: close -1
Control: fixed -1 5.1.5-1
Hi,
On Fr 31 Jan 2020 12:47:15 CET, Ian Kent wrote:
On Fri, 2020-01-31 at 19:35 +0800, Ian Kent wrote:
On Fri, 2020-01-31 at 19:29 +0800, Ian Kent wrote:
> On Fri, 2020-01-31 at 19:16 +0800, Ian Kent wrote:
> > On Fri, 2020-01-31 at 07:55 +0100, Ma
On Fri, 2020-01-31 at 19:35 +0800, Ian Kent wrote:
> On Fri, 2020-01-31 at 19:29 +0800, Ian Kent wrote:
> > On Fri, 2020-01-31 at 19:16 +0800, Ian Kent wrote:
> > > On Fri, 2020-01-31 at 07:55 +0100, Marc Lehmann wrote:
> > > > > > Sounds like I have enough information to duplicate the
> > > > > >
On Fri, 2020-01-31 at 19:29 +0800, Ian Kent wrote:
> On Fri, 2020-01-31 at 19:16 +0800, Ian Kent wrote:
> > On Fri, 2020-01-31 at 07:55 +0100, Marc Lehmann wrote:
> > > > > Sounds like I have enough information to duplicate the
> > > > > problem
> > > > > so
> > > > > I'll have a look see.
> > > >
On Fri, 2020-01-31 at 19:16 +0800, Ian Kent wrote:
> On Fri, 2020-01-31 at 07:55 +0100, Marc Lehmann wrote:
> > > > Sounds like I have enough information to duplicate the problem
> > > > so
> > > > I'll have a look see.
> > >
> > > Oh, as usual, what's the autofs source version of your package
> >
On Fri, 2020-01-31 at 07:55 +0100, Marc Lehmann wrote:
> > > Sounds like I have enough information to duplicate the problem so
> > > I'll have a look see.
> >
> > Oh, as usual, what's the autofs source version of your package
> > please,
> > since I'll be using the current development source to wo
> > Sounds like I have enough information to duplicate the problem so
> > I'll have a look see.
>
> Oh, as usual, what's the autofs source version of your package please,
> since I'll be using the current development source to work on it.
It's the one mentioned in my original report (that you pro
On Fri, 2020-01-31 at 13:34 +0800, Ian Kent wrote:
> On Fri, 2020-01-31 at 01:09 +0100, Marc Lehmann wrote:
> > On Thu, Jan 30, 2020 at 11:50:32PM +, Mike Gabriel <
> > sunwea...@debian.org> wrote:
> > > This seems like something to be discussed upstream. I Cc:ed Ian
> > > Kent, maybe
> > > he
On Fri, 2020-01-31 at 13:34 +0800, Ian Kent wrote:
> On Fri, 2020-01-31 at 01:09 +0100, Marc Lehmann wrote:
> > On Thu, Jan 30, 2020 at 11:50:32PM +, Mike Gabriel <
> > sunwea...@debian.org> wrote:
> > > This seems like something to be discussed upstream. I Cc:ed Ian
> > > Kent, maybe
> > > he
On Fri, 2020-01-31 at 01:09 +0100, Marc Lehmann wrote:
> On Thu, Jan 30, 2020 at 11:50:32PM +, Mike Gabriel <
> sunwea...@debian.org> wrote:
> > This seems like something to be discussed upstream. I Cc:ed Ian
> > Kent, maybe
> > he has some 2? to add.
>
> Cool!
>
> In the meantime, I digged a
On Thu, Jan 30, 2020 at 11:50:32PM +, Mike Gabriel
wrote:
> This seems like something to be discussed upstream. I Cc:ed Ian Kent, maybe
> he has some 2? to add.
Cool!
In the meantime, I digged a bit more, and it seems that it is because with
misc-device support, autofs uses the AUTOFS_DEV_I
Hi Marc, hi Ian,
@Ian: I am the new autofs package maintainer in Debian.
On Fr 31 Jan 2020 00:38:10 CET, Marc Lehmann wrote:
Dear Maintainer,
for many years, I started automount with -t 8640, and by now had
forgotten what this was for (or whether I reported the problem). Today, I
removed
Package: autofs
Version: 5.1.2-4
Severity: normal
Dear Maintainer,
for many years, I started automount with -t 8640, and by now had
forgotten what this was for (or whether I reported the problem). Today, I
removed it and got reminded what it was supposed to work around.
Effectively, when aut
19 matches
Mail list logo
