From: "Mike Frysinger" <vapier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-process/cronbase/files/, sys-process/cronbase/
Date: Wed, 19 Aug 2015 21:49:59 +0000 (UTC) [thread overview]
Message-ID: <1440020985.710db44781655c192126ce09e53f03d2679042e2.vapier@gentoo> (raw)
commit: 710db44781655c192126ce09e53f03d2679042e2
Author: Mike Frysinger <vapier <AT> gentoo <DOT> org>
AuthorDate: Wed Aug 19 21:48:47 2015 +0000
Commit: Mike Frysinger <vapier <AT> gentoo <DOT> org>
CommitDate: Wed Aug 19 21:49:45 2015 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=710db447
sys-process/cronbase: fix lockdir path #557620
.../cronbase/{cronbase-0.3.7.ebuild => cronbase-0.3.7-r1.ebuild} | 0
sys-process/cronbase/files/run-crons-0.3.7 | 2 +-
2 files changed, 1 insertion(+), 1 deletion(-)
diff --git a/sys-process/cronbase/cronbase-0.3.7.ebuild b/sys-process/cronbase/cronbase-0.3.7-r1.ebuild
similarity index 100%
rename from sys-process/cronbase/cronbase-0.3.7.ebuild
rename to sys-process/cronbase/cronbase-0.3.7-r1.ebuild
diff --git a/sys-process/cronbase/files/run-crons-0.3.7 b/sys-process/cronbase/files/run-crons-0.3.7
index 16fe0fa..c661c77 100755
--- a/sys-process/cronbase/files/run-crons-0.3.7
+++ b/sys-process/cronbase/files/run-crons-0.3.7
@@ -6,7 +6,7 @@
# for scripts to be executed. The info about last run is stored in
# /var/spool/cron/lastrun
-LOCKDIR="/var/run/lock"
+LOCKDIR="/var/lock"
CRONSPOOLDIR="/var/spool/cron"
LASTRUNDIR="${CRONSPOOLDIR}/lastrun"
# This is the legacy lockfile that we need to clean up.
next reply other threads:[~2015-08-19 21:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 21:49 Mike Frysinger [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-03-15 2:33 [gentoo-commits] repo/gentoo:master commit in: sys-process/cronbase/files/, sys-process/cronbase/ Mike Frysinger
2016-09-30 14:17 Tobias Klausmann
2016-10-02 8:48 Tobias Klausmann
2016-10-03 17:19 Tobias Klausmann
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=1440020985.710db44781655c192126ce09e53f03d2679042e2.vapier@gentoo \
--to=vapier@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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