When the xfstests are executed in a batch (like "check 001-299") and produce syslog output, it is helpful to know which test was causing the output. Therefore each time a test is started, a syslog message is generated that contains the number of the xfstest. Signed-off-by: Stefan Behrens <sbehrens@xxxxxxxxxxxxxxxx> --- Changes v1->v2: - In order to avoid noise, check that /usr/bin/logger is there before trying to execute it. This usually should always be the case except for embedded environments. check | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/check b/check index f792009..a4af0f6 100755 --- a/check +++ b/check @@ -241,6 +241,7 @@ do start=`_wallclock` $timestamp && echo -n " ["`date "+%T"`"]" [ ! -x $seq ] && chmod u+x $seq # ensure we can run it + [ -x /usr/bin/logger ] && /usr/bin/logger "run xfstest $seq" ./$seq >$tmp.rawout 2>&1 sts=$? $timestamp && _timestamp -- 1.7.3.4 _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
