From: Karel Zak <kzak@redhat.com>
To: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>
Cc: util-linux <util-linux@vger.kernel.org>
Subject: Re: mount (new): Using -a, exits with 64.
Date: Fri, 20 Jan 2012 00:17:21 +0100 [thread overview]
Message-ID: <20120119231721.GC6482@x2.net.home> (raw)
In-Reply-To: <4F188277.7090100@yahoo.com.ar>
On Thu, Jan 19, 2012 at 05:52:07PM -0300, Gerardo Exequiel Pozzi wrote:
> Using new mount, when run with -a and some mounting is performed, mount
> retuns 64 instead of 0.
Ah.. I know that umount exit codes and error messages are not ready,
but I forgot to check mount -a, so thanks. I will add this to my TODO
list for -rc2.
> # mkdir /mnt/coco
> # echo "coco /mnt/coco tmpfs defaults 0 0" >> /etc/fstab
> # mount -a ; echo $?
> 64
Anyway, this seems correct, man mount:
64 some mount succeeded
this used by mount -a.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2012-01-19 23:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 20:52 mount (new): Using -a, exits with 64 Gerardo Exequiel Pozzi
2012-01-19 23:17 ` Karel Zak [this message]
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=20120119231721.GC6482@x2.net.home \
--to=kzak@redhat.com \
--cc=util-linux@vger.kernel.org \
--cc=vmlinuz386@yahoo.com.ar \
/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;
as well as URLs for NNTP newsgroup(s).