public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "PaweA Hajdan (phajdan.jr)" <phajdan.jr@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in app-admin/logcheck/files: logcheck.cron
Date: Sun, 30 Dec 2012 18:53:17 +0000 (UTC)	[thread overview]
Message-ID: <20121230185317.BF8192171E@flycatcher.gentoo.org> (raw)

phajdan.jr    12/12/30 18:53:17

  Modified:             logcheck.cron
  Log:
  Make sure lock directory exists, bug #440880 by Ivan.
  
  (Portage version: 2.1.11.31/cvs/Linux i686, signed Manifest commit with key 30427902)

Revision  Changes    Path
1.2                  app-admin/logcheck/files/logcheck.cron

file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/app-admin/logcheck/files/logcheck.cron?rev=1.2&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/app-admin/logcheck/files/logcheck.cron?rev=1.2&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/app-admin/logcheck/files/logcheck.cron?r1=1.1&r2=1.2

Index: logcheck.cron
===================================================================
RCS file: /var/cvsroot/gentoo-x86/app-admin/logcheck/files/logcheck.cron,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- logcheck.cron	20 Dec 2009 10:05:09 -0000	1.1
+++ logcheck.cron	30 Dec 2012 18:53:17 -0000	1.2
@@ -1,5 +1,10 @@
 #!/bin/bash
-#
-# Please uncomment the following if you want logcheck to run hourly.
 
-#su -s /bin/bash -c /usr/sbin/logcheck logcheck
+set -e
+
+if [ ! -d /var/lock/logcheck ]; then
+	mkdir -p /var/lock/logcheck
+fi
+chown -R logcheck:logcheck /var/lock/logcheck
+
+su -s /bin/bash -c /usr/sbin/logcheck logcheck





                 reply	other threads:[~2012-12-30 18:53 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=20121230185317.BF8192171E@flycatcher.gentoo.org \
    --to=phajdan.jr@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