public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org, wschlich@gentoo.org
Subject: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in sys-process/fcron: ChangeLog fcron-3.0.4.ebuild
Date: Fri, 9 Nov 2007 01:08:05 -0800	[thread overview]
Message-ID: <20071109090805.GD5516@supernova> (raw)
In-Reply-To: <E1IqPdj-00082u-U5@stork.gentoo.org>

On 08:54 Fri 09 Nov     , Wolfram Schlich (wschlich) wrote:
> 1.1                  sys-process/fcron/fcron-3.0.4.ebuild
> 
> file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-process/fcron/fcron-3.0.4.ebuild?rev=1.1&view=markup
> plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-process/fcron/fcron-3.0.4.ebuild?rev=1.1&content-type=text/plain

> 	if useq debug; then

use() is useq() now. Dunno whether this is common enough to deserve a 
repoman check.

> 	if ls -1 /var/spool/cron/fcrontabs/* >&/dev/null; then

This particular check ignores ROOT, and so does the rest of 
pkg_postinst(). Seems to me that a cron daemon is a package relatively 
likely to be installed using ROOT, so it's worth fixing.

> 		ewarn
> 		ewarn "WARNING: fcron now uses a dedicated fcron-specific"
> 		ewarn "spooldir /var/spool/fcron instead of the commonly"
> 		ewarn "used /var/spool/cron for several reasons."
> 		ewarn
> 		ewarn "Copying over existing crontabs from /var/spool/cron/fcrontabs"
> 		cp /var/spool/cron/fcrontabs/* /var/spool/fcron/ >&/dev/null \
> 			|| die "failed to migrate existing crontabs"
> 		ewarn "You should now remove /var/spool/cron/fcrontabs!"
> 		ewarn
> 		ewarn "Fixing permissions and ownership of /var/spool/fcron"
> 		chown root:root /var/spool/fcron/* >&/dev/null
> 		chmod 0600 /var/spool/fcron/* >&/dev/null
> 		chown fcron:fcron /var/spool/fcron/*.orig >&/dev/null
> 		chmod 0640 /var/spool/fcron/*.orig >&/dev/null
> 		ewarn
> 		ewarn "*** YOU SHOULD IMMEDIATELY UPDATE THE"
> 		ewarn "*** fcrontabs ENTRY IN /etc/fcron/fcron.conf"
> 		ewarn "*** AND RESTART YOUR FCRON DAEMON!"
> 		ebeep 20
> 		epause 10

Thanks,
Donnie
-- 
gentoo-dev@gentoo.org mailing list



       reply	other threads:[~2007-11-09  9:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1IqPdj-00082u-U5@stork.gentoo.org>
2007-11-09  9:08 ` Donnie Berkholz [this message]
2007-11-20  0:52   ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in sys-process/fcron: ChangeLog fcron-3.0.4.ebuild Wolfram Schlich
2007-11-20  1:23     ` Petteri Räty
2007-11-21  1:02       ` Wolfram Schlich

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=20071109090805.GD5516@supernova \
    --to=dberkholz@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=wschlich@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