Difference between pages "Flavors and Mix-ins" and "Installing a Cron Daemon"

From Funtoo
(Difference between pages)
Jump to: navigation, search
m (Mix-ins)
 
m (Installation)
 
Line 1: Line 1:
This page documents flavors and mix-ins, which are components of [[Funtoo 1.0 Profile|Funtoo profiles]]:
+
== Introduction ==
 +
Cron daemons allow you to configure certain tasks to be run at specific times. Installing a cron daemon is a good idea because some packages may assume that you have a cron daemon installed and create jobs to update their databases with a cron daemon. There are several different loggers available to Funtoo users:
 +
* '''Fcron'''
 +
* '''Cronie'''
 +
* '''Vixie-Cron'''
  
== Flavors ==
+
== Installation ==
 +
To install the cron daemon, run the following command:
 +
<console>
 +
# ##i## emerge --ask fcron
  
A system can have only one flavor profile enabled at a time. The following flavors are available:
+
These are the packages that would be merged, in order:
  
;minimal: This flavor defines the most minimal possible flavor. It currently only contains defaults for all Funtoo Linux flavors.
+
Calculating dependencies... done!
 +
[ebuild  N    ] sys-process/cronbase-0.3.2-r1
 +
[ebuild  N    ] sys-process/fcron-3.1.2-r2  USE="mta pam readline system-crontab -debug (-selinux)" LINGUAS="-fr"
  
;core: The core flavor is the minimal flavor plus reasonable USE options, and is used for stage3 builds.
+
Would you like to merge these packages? [Yes/No]##i## yes
 +
</console>
  
;server: The server flavor is intended for servers but at this time just tracks core.
+
Now enable the cron init script so that is starts when your system boots, and enable the cron daemon:
  
;workstation: The workstation flavor is a minimal desktop system. It includes the core flavor plus these mix-ins: '''X''', '''audio''', '''dvd''', '''media''', '''console-extras'''
+
<console>
 +
# ##i##rc-update add fcron default
 +
* service fcron added to runlevel default
 +
# ##i##rc
 +
* Caching service dependencies ...              [ ok ]
 +
* Starting fcron ...                            [ ok ]
 +
</console>
  
;desktop: The desktop flavor is a full-featured desktop system, minus desktop environment (add KDE, GNOME or XFCE as a mix-in.) It includes the '''workstation''' flavor plus '''printing''' support.
+
=== System Cron Jobs ===
  
== Mix-ins ==
+
After the cron daemon has been emerged, you may see a message to run <tt>emerge --config</tt> to configure your cron daemon to process system cron jobs. System cron jobs are scripts that are installed by various packages into the following directories:
  
A system can have any number of mix-ins enabled at a time. The following mix-ins are available:
+
* <tt>/etc/cron.hourly</tt>
 +
* <tt>/etc/cron.daily</tt>
 +
* <tt>/etc/cron.weekly</tt>
 +
* <tt>/etc/cron.monthly</tt>
  
;audio: Enables core audio-related settings, currently related to ALSA.
+
For example, you should find a <tt>/etc/cron.daily/man-db</tt> script that is installed by the <tt>man-db</tt> ebuild. This system cron job's purpose is to update the man cache every day, and it will run only if you enable your cron daemon to manage system cron jobs.
  
;console-extras: Enables things that are nice to have for console-only systems. Currently enabling gpm in USE.
+
You may choose to enable your cron daemon so that it runs system cron jobs, or choose not to. Enabling a cron daemon to run system cron jobs will result in a bit more disk and CPU activity on your system, but should ensure that the system runs more optimally most of the time (proper caching of man pages, etc.) It is recommended for most systems, but your system will still function without system cron jobs active.
  
;dvd: USE settings related to optical drives -- CDR/DVD-ROM/RW use.
+
If you would like to have your system run system cron jobs, use <tt>emerge --config</tt> as specified in the emerge output:
  
;gnome: USE and package.use settings required to merge GNOME.
+
<console>
 +
# ##i##emerge --config sys-process/fcron
 +
Configuring pkg...
  
;hardened: Enables hardened support.
+
* This is going to set up fcron to execute check_system_crontabs.
 +
* In this configuration, you're no longer free to edit the systab
 +
* at your leisure, at it'll be rewritten the moment the crontabs
 +
* are modified.
  
;kde: USE and package.use settings required to merge KDE.
+
Rebuilding fcron systab.2013-10-19 21:20:38 
 +
INFO installing file /tmp/fcrontab.84pova for user systab
 +
Modifications will be taken into account right now.</console>
  
;media: USE settings related to audio/video media encoding. Can be for desktops or servers.
+
Your cron daemon is now configured to automatically run system cron jobs.
  
;print: Enables printing capability.
+
[[Category:System]]
 
+
;rhel5-compat: settings required for running a system that uses a Red Hat Enterprise Linux 5-based kernel.
+
 
+
;vmware-guest: settings related to using Funtoo Linux as a VMWare virtual machine guest.
+
 
+
;X: Settings related to the X Window System and hardware support.
+
 
+
;xfce: USE settings required for merging XFCE.
+
 
+
[[Category:Portage]]
+
[[Category:Featured]]
+
[[Category:Funtoo features]]
+

Revision as of 21:00, 10 December 2013

Introduction

Cron daemons allow you to configure certain tasks to be run at specific times. Installing a cron daemon is a good idea because some packages may assume that you have a cron daemon installed and create jobs to update their databases with a cron daemon. There are several different loggers available to Funtoo users:

  • Fcron
  • Cronie
  • Vixie-Cron

Installation

To install the cron daemon, run the following command:

#  emerge --ask fcron

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  N     ] sys-process/cronbase-0.3.2-r1
[ebuild  N     ] sys-process/fcron-3.1.2-r2  USE="mta pam readline system-crontab -debug (-selinux)" LINGUAS="-fr" 

Would you like to merge these packages? [Yes/No] yes

Now enable the cron init script so that is starts when your system boots, and enable the cron daemon:

# rc-update add fcron default
 * service fcron added to runlevel default
# rc
 * Caching service dependencies ...              [ ok ]
 * Starting fcron ...                            [ ok ]

System Cron Jobs

After the cron daemon has been emerged, you may see a message to run emerge --config to configure your cron daemon to process system cron jobs. System cron jobs are scripts that are installed by various packages into the following directories:

  • /etc/cron.hourly
  • /etc/cron.daily
  • /etc/cron.weekly
  • /etc/cron.monthly

For example, you should find a /etc/cron.daily/man-db script that is installed by the man-db ebuild. This system cron job's purpose is to update the man cache every day, and it will run only if you enable your cron daemon to manage system cron jobs.

You may choose to enable your cron daemon so that it runs system cron jobs, or choose not to. Enabling a cron daemon to run system cron jobs will result in a bit more disk and CPU activity on your system, but should ensure that the system runs more optimally most of the time (proper caching of man pages, etc.) It is recommended for most systems, but your system will still function without system cron jobs active.

If you would like to have your system run system cron jobs, use emerge --config as specified in the emerge output:

# emerge --config sys-process/fcron
Configuring pkg...

 * This is going to set up fcron to execute check_system_crontabs.
 * In this configuration, you're no longer free to edit the systab
 * at your leisure, at it'll be rewritten the moment the crontabs
 * are modified.

Rebuilding fcron systab.2013-10-19 21:20:38  
INFO installing file /tmp/fcrontab.84pova for user systab
Modifications will be taken into account right now.

Your cron daemon is now configured to automatically run system cron jobs.