From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 0aa93f5b11a57236f523714373e1abca25caaa65
Date: Thu, 07 Feb 2013 12:02:46 +0100 [thread overview]
Message-ID: <20130207110250.60843200DA@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1636 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 0aa93f5b11a57236f523714373e1abca25caaa65 (commit)
from 6f704a3c85dc453e1a8cebafbca5446e59aab6d6 (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 0aa93f5b11a57236f523714373e1abca25caaa65
Author: Daniel Weismüller <whytea(a)ipfire.org>
Date: Thu Feb 7 11:36:03 2013 +0100
Delete checkdeaddl.lck file on boot.
This lock file does only exist, when the system has suddenly
been shut down while update accelerator is optimizing its cache.
-----------------------------------------------------------------------
Summary of changes:
src/initscripts/init.d/cleanfs | 3 +++
1 file changed, 3 insertions(+)
Difference in files:
diff --git a/src/initscripts/init.d/cleanfs b/src/initscripts/init.d/cleanfs
index 855e63e..d526c35 100644
--- a/src/initscripts/init.d/cleanfs
+++ b/src/initscripts/init.d/cleanfs
@@ -90,6 +90,9 @@ case "${1}" in
cd /var/lock &&
find . -type f ! -newer /proc -exec rm -f {} \; || failed=1
+ boot_mesg -n " /var/log/updatexlrator" ${NORMAL}
+ rm -f /var/log/updatexlrator/checkdeaddl.lck
+
boot_mesg " /var/run" ${NORMAL}
cd /var/run &&
find . ! -type d ! -name utmp ! -newer /proc \
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-02-07 11:02 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=20130207110250.60843200DA@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