SCIENTIFIC-LINUX-DEVEL Archives

September 2011

SCIENTIFIC-LINUX-DEVEL@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Stephen Isard <[log in to unmask]>
Reply To:
Stephen Isard <[log in to unmask]>
Date:
Mon, 26 Sep 2011 11:55:45 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 lines)
On Sun, 25 Sep 2011 15:38:16 +1200, Sean <[log in to unmask]> wrote:

>Fcron is a scheduler that can replace and is far superior to both
>vixie-cron & anacron. I have often wondered at the relatively small
>level of take up, which I now realise could be a consequence of the rpm
>installation being misconfigured in SL6, and going all the way back to
>RH8. Before discovering this lately I used to have to always re-install
>from raw tarball to get working software.
>
>Fcron has a default installation directory of /etc, and when custom
>installing to some other <DESTDIR> instead, as the RH rpm does, there
>are special instructions to be followed. The RH rpm for fcron does not
>follow those instructions in relation to PAM and, while apparently
>installing ok, ends up broken, with a spurious pam.conf file under
>/usr/local/etc.

I installed fcron with 'yum localinstall' on an FC5 laptop from 
fcron-3.0.4-1.fc10.i386.rpm.  fcron and fcrontab files were put into
/etc/pam.d, and nothing in /usr/local/etc.  It runs without problems

I can't remember why fc10, but it was probably the most recent version at
the time.

Stephen Isard

ATOM RSS1 RSS2