From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 5c313dec7d860d47b51c69923a3d91c8f2334df5
Date: Sun, 30 Dec 2012 09:49:29 +0100 [thread overview]
Message-ID: <20121230084930.0DFA920132@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1396 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via 5c313dec7d860d47b51c69923a3d91c8f2334df5 (commit)
from 65c6ed3f278cc8e42dc79309bed1c96e8c171d33 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 5c313dec7d860d47b51c69923a3d91c8f2334df5
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun Dec 30 09:48:35 2012 +0100
lcr: fix logfile in initskript.
-----------------------------------------------------------------------
Summary of changes:
src/initscripts/init.d/lcr | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/src/initscripts/init.d/lcr b/src/initscripts/init.d/lcr
index 56a4553..dd72967 100644
--- a/src/initscripts/init.d/lcr
+++ b/src/initscripts/init.d/lcr
@@ -18,7 +18,7 @@
case "${1}" in
start)
boot_mesg "Starting Linux Call Router..."
- nice --10 /usr/sbin/lcr fork >> /var/log/lcr 2>&1
+ nice --10 /usr/sbin/lcr fork >> /var/log/lcr/console.log 2>&1
evaluate_retval
;;
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2012-12-30 8:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20121230084930.0DFA920132@argus.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.org \
/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