From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com
Cc: J?rgen Tegn?r <jorgen.tegner@telia.com>
Subject: fix fsrlast location in --help output
Date: Thu, 1 Jan 2009 12:45:23 -0500 [thread overview]
Message-ID: <20090101174523.GA515@infradead.org> (raw)
Make sure xfs_fsr --help outputs the correct location for the fsrlast
file. Also add a _PATH_FSRLAST define to not have to keep this multiple
times in the source code, and remove a comment in xfs_fsr.c duplicating
the help text and manpage.
This fixes Debian bug #491525.
Reported-by: J?rgen Tegn?r <jorgen.tegner@telia.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Index: xfsdump/fsr/xfs_fsr.c
===================================================================
--- xfsdump.orig/fsr/xfs_fsr.c 2009-01-01 11:00:32.298701760 +0100
+++ xfsdump/fsr/xfs_fsr.c 2009-01-01 11:03:47.782548742 +0100
@@ -16,31 +16,6 @@
* Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
*/
-/*
- * fsr - file system reorganizer
- *
- * fsr [-d] [-v] [-n] [-s] [-g] [-t secs] [-f leftf] [-m mtab]
- * fsr [-d] [-v] [-n] [-s] [-g] xfsdev | dir | file ...
- *
- * If invoked in the first form fsr does the following: starting with the
- * dev/inum specified in /etc/fsrlast this reorgs each reg file in each file
- * system found in /etc/mtab. After 2 hours of this we record the current
- * dev/inum in /etc/fsrlast. If there is no /etc/fsrlast fsr starts at the
- * top of /etc/mtab.
- *
- * -g print to syslog (default if stdout not a tty)
- * -m mtab use something other than /etc/mtab
- * -t time how long to run
- * -f leftoff use this instead of /etc/fsrlast
- *
- * -v verbose. more -v's more verbose
- * -d debug. print even more
- * -n do nothing. only interesting with -v. Not
- * effective with in mtab mode.
- * -s print statistics only.
- * -p passes Number of passes before terminating global re-org.
- */
-
#include <xfs/xfs.h>
#include <xfs/jdm.h>
#include "config.h"
@@ -63,6 +38,7 @@
#define XFS_XFLAG_NODEFRAG 0x00002000 /* src dependancy, remove later */
#endif
+#define _PATH_FSRLAST "/var/tmp/.fsrlast_xfs"
char *progname;
@@ -98,7 +74,7 @@ static __int64_t minimumfree = 2048;
#define min(x, y) ((x) < (y) ? (x) : (y))
static time_t howlong = 7200; /* default seconds of reorganizing */
-static char *leftofffile = "/var/tmp/.fsrlast_xfs";/* where we left off last */
+static char *leftofffile = _PATH_FSRLAST; /* where we left off last */
static char *mtab = MOUNTED;
static time_t endtime;
static time_t starttime;
@@ -368,11 +344,11 @@ usage(int ret)
" -g Print to syslog (default if stdout not a tty).\n"
" -t time How long to run in seconds.\n"
" -p passes Number of passes before terminating global re-org.\n"
-" -f leftoff Use this instead of /etc/fsrlast.\n"
+" -f leftoff Use this instead of %s.\n"
" -m mtab Use something other than /etc/mtab.\n"
" -d Debug, print even more.\n"
" -v Verbose, more -v's more verbose.\n"
- ), progname, progname);
+ ), progname, progname, _PATH_FSRLAST);
exit(ret);
}
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2009-01-01 17:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-01 17:45 Christoph Hellwig [this message]
2009-01-01 18:04 ` fix fsrlast location in --help output Eric Sandeen
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=20090101174523.GA515@infradead.org \
--to=hch@infradead.org \
--cc=jorgen.tegner@telia.com \
--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