From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/1] network.sh: Cleanup netpan logs
Date: Sun, 10 Jun 2018 12:23:08 +0200 [thread overview]
Message-ID: <20180610102308.GA10123@x230> (raw)
In-Reply-To: <20180610101309.8201-1-pvorel@suse.cz>
Hi,
> network.sh script doesn't delete it's logs, which can lead to fill /tmp.
> Remove these files, which unify behavior with runltp and runltplite.sh
> (just don't use trap to force remove on INT).
...
> testscripts/network.sh | 2 ++
...
> @@ -121,3 +121,5 @@ if [ $? -eq "0" ]; then
> else
> echo ltp-pan reported FAIL
> fi
> +
> +rm -rf $TMPDIR
I suppose there is no reason to keep ltp-net logs, that it was left by accident.
This patch keeps /tmp/netpan.log, but that's just one file.
Kind regards,
Petr
next prev parent reply other threads:[~2018-06-10 10:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-10 10:13 [LTP] [PATCH 1/1] network.sh: Cleanup netpan logs Petr Vorel
2018-06-10 10:23 ` Petr Vorel [this message]
2018-06-14 10:38 ` Alexey Kodanev
2018-06-14 11:34 ` Petr Vorel
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=20180610102308.GA10123@x230 \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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