From: Caspar Zhang <caspar@casparzhang.com>
To: Peng Haitao <penght@cn.fujitsu.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] logrotate01: fix a bug of config file's permission is wrong
Date: Fri, 11 May 2012 12:13:18 +0800 [thread overview]
Message-ID: <4FAC91DE.70203@casparzhang.com> (raw)
In-Reply-To: <1336703855-15408-1-git-send-email-penght@cn.fujitsu.com>
On 05/11/2012 10:37 AM, Peng Haitao wrote:
> config file's permission should be 644, please refer to:
> https://fedorahosted.org/logrotate/changeset/302
>
> Signed-off-by: Peng Haitao <penght@cn.fujitsu.com>
Reviewed-by: Caspar Zhang <caspar@casparzhang.com>
> ---
> testcases/commands/logrotate/logrotate_tests.sh | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/testcases/commands/logrotate/logrotate_tests.sh b/testcases/commands/logrotate/logrotate_tests.sh
> index 827dd5f..55ef0b3 100755
> --- a/testcases/commands/logrotate/logrotate_tests.sh
> +++ b/testcases/commands/logrotate/logrotate_tests.sh
> @@ -192,6 +192,7 @@ test01()
> rm -f $files > /dev/null 2>&1
> done
>
> + chmod 644 $LTPTMP/tst_logrotate.conf
> logrotate -fv $LTPTMP/tst_logrotate.conf > $LTPTMP/tst_logrotate.out 2>&1 \
> || RC=$?
> if [ $RC -eq 0 ]
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2012-05-11 4:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 2:37 [LTP] [PATCH] logrotate01: fix a bug of config file's permission is wrong Peng Haitao
2012-05-11 4:13 ` Caspar Zhang [this message]
2012-05-11 5:30 ` Wanlong Gao
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=4FAC91DE.70203@casparzhang.com \
--to=caspar@casparzhang.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=penght@cn.fujitsu.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