On 10/26/19 8:34 PM, Trent via blfs-support wrote:
On 10/26/19 7:13 PM, Douglas R. Reno via blfs-support wrote:
On 10/26/19 7:04 PM, Trent via blfs-support wrote:
From this section:
http://www.linuxfromscratch.org/blfs/view/stable-systemd/general/fcron.html
Last part:
sed -i 's:/var/run/fcron.pid:/run/fcron.pid:' \
/lib/systemd/system/fcron.service Is returning: sed: can't read
/lib/systemd/system/fcron.service: No such file or directory
Directory exists, but no fcron.service. Does not exist in the 2018,
or 2019 BLFS Systemd Units package either.
You should have a /lib/systemd/system/fcron.service installed from
the 'make install' command since it's provided by the package.
Can you check and see if you have the following files in your
fcron-3.2.1 tarball (and verify the md5sum please):
renodr [ /sources/fcron-3.2.1.src/fcron-3.2.1 ]$ ls script/ | grep
systemd
fcron.init.systemd.in
The makefile should generate a fcron.init.systemd which will then be
installed to /lib/systemd/system as 'fcron.service'
I just checked my script against the book for verification and ran it
again and came up with the expected result
There is also one other thing I forgot to mention on that installation.
The command "/etc/rc.d/init.d/sysklogd reload" is returning: -bash:
/etc/rc.d/init.d/sysklogd: No such file or directory Trent
That should be in the systemd version only. In the SysV version of BLFS,
running that after modifying the syslog.conf file will allow your system
to begin logging cron events without restarting the system. In systemd,
fcron logs to the journal (by default, you can modify that I've heard
but I've never tried it).
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
