From: jhuang0 <jackie.huang@windriver.com>
To: Phil Blundell <pb@pbcl.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/6] sysvinit: add init.d/bootlogd status command for LSB compliance
Date: Tue, 20 Aug 2013 17:33:46 +0800 [thread overview]
Message-ID: <521337FA.9040701@windriver.com> (raw)
In-Reply-To: <1376980784.4083.27.camel@x121e.pbcl.net>
On 8/20/2013 2:39 PM, Phil Blundell wrote:
> On Tue, 2013-08-20 at 11:25 +0800, jackie.huang@windriver.com wrote:
>> @@ -37,6 +40,19 @@ case "$0" in
>> ;;
>> esac
>>
>> +# default /var/log/boot is not an option since /var/log becomes
>> +# /var/volatile/log
>> +logfile=/var/local/bootlogd.log
>> +
>> +#
>> +# Create initial log files
>> +#
>> +if [ ! -f "$logfile" ] && touch "$logfile" >/dev/null 2>&1; then
>> + echo "(Nothing has been logged yet.)" >| "$logfile"
>> + chown root:adm "$logfile"
>> + chmod 640 "$logfile"
>> +fi
>> +
>> case "$ACTION" in
>> start)
>> echo -n "Starting $DESC: "
>> @@ -44,9 +60,9 @@ case "$ACTION" in
>> then
>> umask 027
>> start-stop-daemon --start --quiet \
>> - --exec $DAEMON -- -r
>> + --exec $DAEMON -- -r -l $logfile
>> else
>> - $DAEMON -r
>> + $DAEMON -r -l $logfile
>> fi
>> echo "$NAME."
>> ;;
>
> It's not totally obvious that the changes are related to the "status"
> command. If you're creating new logfiles that didn't exist previously
> then I think the commit message ought to explain why.
>
Sorry, my mistake to involve some other patch when I got the patch from
our layer, I will remake the patches.
Thanks,
Jackie
> p.
>
>
>
>
--
Jackie Huang
WIND RIVER | China Development Center
MSN:jackielily@hotmail.com
Tel: +86 8477 8594
Mobile: +86 138 1027 4745
next prev parent reply other threads:[~2013-08-20 9:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 3:25 [PATCH 0/6] Add status command for LSB compliance for some packages jackie.huang
2013-08-20 3:25 ` [PATCH 1/6] dbus: add init.d/dbus-1 status command for LSB compliance jackie.huang
2013-08-20 3:25 ` [PATCH 2/6] sysvinit: add init.d/bootlogd " jackie.huang
2013-08-20 6:39 ` Phil Blundell
2013-08-20 9:33 ` jhuang0 [this message]
2013-08-20 3:25 ` [PATCH 3/6] nfs-utils: add init.d/nfsserver " jackie.huang
2013-08-20 6:36 ` Phil Blundell
2013-08-20 3:25 ` [PATCH 4/6] openssh: add init.d/sshd " jackie.huang
2013-08-22 6:42 ` Khem Raj
2013-08-22 7:02 ` jhuang0
2013-08-22 7:15 ` ChenQi
2013-08-20 3:25 ` [PATCH 5/6] sysklogd: add init.d/syslog " jackie.huang
2013-08-20 3:25 ` [PATCH 6/6] at: add init.d/atd " jackie.huang
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=521337FA.9040701@windriver.com \
--to=jackie.huang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pb@pbcl.net \
/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