From: Donald Douwsma <ddouwsma@bigpond.net.au>
To: "Arkadiusz Miśkiewicz" <arekm@maven.pl>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] [LIBXCMD]: Move error messages to appropriate places.
Date: Fri, 30 Jan 2009 01:29:06 +1100 [thread overview]
Message-ID: <4981BD32.2090405@bigpond.net.au> (raw)
In-Reply-To: <1233167051-14711-1-git-send-email-arekm@maven.pl>
Arkadiusz Miśkiewicz wrote:
> Replace raw perror() with proper message in
> fs_table_initialise_mounts().
>
> Replace raw perror() with proper message and move it from
> fs_mount_point_from_path() to fs_table_initialise_projects() where this
> message has meaning.
I like your change, it makes things clearer.
But does this particular error actually help people? I've seen it a few times
when testing quota code in the past. It's only used when reading in projects,
and causes errors to be displayed even when issuing non project commands.
$ sudo bash -c "echo 10:/var/nonexistantdir >> /etc/projects
$ xfs_quota -c print
/var/nonexistantdir: No such file or directory
Filesystem Pathname
/home /dev/sda8
I'd be tempted to remove this error, and add error checking code to the project specific
commands that walk tree's.
Unless there's some corner case I'm missing, What do you think?
Don
>
> Signed-off-by: Arkadiusz Miśkiewicz <arekm@maven.pl>
> ---
> libxcmd/paths.c | 9 ++++++---
> 1 files changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/libxcmd/paths.c b/libxcmd/paths.c
> index facea06..6c36b79 100644
> --- a/libxcmd/paths.c
> +++ b/libxcmd/paths.c
> @@ -248,7 +248,8 @@ fs_table_initialise_mounts(
> dir = fsname = fslog = fsrt = NULL;
>
> if ((count = getmntinfo(&stats, 0)) < 0) {
> - perror("getmntinfo");
> + fprintf(stderr, _("%s: getmntinfo() failed: %s\n"),
> + progname, strerror(errno));
> return 0;
> }
>
> @@ -298,7 +299,6 @@ fs_mount_point_from_path(
> struct stat64 s;
>
> if (stat64(dir, &s) < 0) {
> - perror(dir);
> return NULL;
> }
>
> @@ -327,8 +327,11 @@ fs_table_initialise_projects(
> while ((path = getprpathent()) != NULL) {
> if (project && prid != path->pp_prid)
> continue;
> - if ((fs = fs_mount_point_from_path(path->pp_pathname)) == NULL)
> + if ((fs = fs_mount_point_from_path(path->pp_pathname)) == NULL) {
> + fprintf(stderr, _("%s: cannot find mount point for path `%s': %s\n"),
> + progname, path->pp_pathname, strerror(errno));
> continue;
> + }
> found = 1;
> dir = strdup(path->pp_pathname);
> fsname = strdup(fs->fs_name);
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-01-29 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 18:24 [PATCH] [LIBXCMD]: Move error messages to appropriate places Arkadiusz Miśkiewicz
2009-01-29 9:30 ` Nathan Scott
2009-01-29 14:29 ` Donald Douwsma [this message]
2009-01-29 14:43 ` Arkadiusz Miskiewicz
2009-01-29 15:07 ` Donald Douwsma
2009-01-29 22:09 ` Christoph Hellwig
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=4981BD32.2090405@bigpond.net.au \
--to=ddouwsma@bigpond.net.au \
--cc=arekm@maven.pl \
--cc=xfs@oss.sgi.com \
/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