Util-Linux package development
 help / color / mirror / Atom feed
From: Ruediger Meier <sweet_f_a@gmx.de>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: bug v2.29-rc2, /etc/mtab file
Date: Thu, 20 Oct 2016 18:24:43 +0200	[thread overview]
Message-ID: <201610201824.43329.sweet_f_a@gmx.de> (raw)
In-Reply-To: <20161020160021.2hjla2qxaglo37tv@ws.net.home>

On Thursday 20 October 2016, Karel Zak wrote:
> On Thu, Oct 20, 2016 at 03:59:15PM +0200, Ruediger Meier wrote:
> > Hi,
> >
> > On RHEL/CentOs-6 with /etc/mtab file some of our mount tests write
> > something to /etc/mtab. AFAIR it should be ignored nowadays by
> > default, right?
> >
> > After our test-suite was running I see these lines left in
> > /etc/mtab:
> >
> > tmpd
> > /home/abuild/rpmbuild/BUILD/util-linux-2.29-rc2/tests/output/mount/
> >fstab-broken-mnt tmpfs rw 0 0 tmpd
> > /home/abuild/rpmbuild/BUILD/util-linux-2.29-rc2/tests/output/mount/
> >fstab-broken-mnt tmpfs rw 0 0 none
> > /home/abuild/rpmbuild/BUILD/util-linux-2.29-rc2/tests/output/mount/
> >fstab-none-mnt tmpfs rw,nosuid,nodev,relatime 0 0
>
> Because our mount (from the test) calls /sbin/mount.tmpfs where
> is executed standard mount(8) from system.

Ah interesting. That's why it works on my local system (also mtab file) 
where I don't have /sbin/mount.tmpfs.

> I'll improve the test to call umount --fake to clean up mtab.

Still a bit annoying that these "third party mount binaries" may modify 
mtab but our umount does not.

cu,
Rudi

  reply	other threads:[~2016-10-20 16:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-20 13:59 bug v2.29-rc2, /etc/mtab file Ruediger Meier
2016-10-20 16:00 ` Karel Zak
2016-10-20 16:24   ` Ruediger Meier [this message]
2016-10-20 16:32     ` Karel Zak
2016-10-20 16:28 ` Karel Zak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201610201824.43329.sweet_f_a@gmx.de \
    --to=sweet_f_a@gmx.de \
    --cc=kzak@redhat.com \
    --cc=util-linux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox