public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "W.Kenworthy" <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] fcron
Date: Tue, 03 Apr 2007 20:15:49 +0800	[thread overview]
Message-ID: <1175602550.17606.27.camel@bunyip.localdomain> (raw)
In-Reply-To: <200704031006.01554.alan@linuxholdings.co.za>

On Tue, 2007-04-03 at 10:06 +0200, Alan McKinnon wrote:
> On Tuesday 03 April 2007, Trevor Forbes wrote:
> > W.Kenworthy wrote:
...
> > [Bug 171998] sys-process/fcron-3.0.2-r1 - root can't list/edit
> > cronjobs.
> 
> Getting a little OT here, but I find that a very interesting bug report. 
> It seems sensible that adding root to the fcron group would fix the 
> problem, but this raises an interesting question:
> 
...

didnt work for me - root was added, cron stopped an restarted.  Logged
in as root at another console - no change.  Havnt rebooted though.

BillK


-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-04-03 12:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-02 14:09 [gentoo-user] fcron W.Kenworthy
2007-04-02 14:41 ` Alexis Lahouze
2007-04-02 14:49 ` Alan McKinnon
2007-04-02 15:12   ` Alexis Lahouze
2007-04-02 15:28   ` Etaoin Shrdlu
2007-04-02 15:20     ` Alan McKinnon
2007-04-02 22:59       ` W.Kenworthy
2007-04-03  7:31         ` Trevor Forbes
2007-04-03  8:06           ` Alan McKinnon
2007-04-03 12:15             ` W.Kenworthy [this message]
2007-04-03 12:49               ` Alan McKinnon
2007-04-03 13:08                 ` W.Kenworthy
2007-04-03 12:10           ` W.Kenworthy
2007-04-03 13:26       ` Dirk Heinrichs
2007-04-03 14:37         ` Alan McKinnon
2007-04-03 22:44         ` W.Kenworthy
  -- strict thread matches above, loose matches on Subject: below --
2013-01-30  6:07 jens wefer

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=1175602550.17606.27.camel@bunyip.localdomain \
    --to=billk@iinet.net.au \
    --cc=gentoo-user@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