<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>11009</bug_id>
          
          <creation_ts>2002-11-20 11:43 0000</creation_ts>
          <short_desc>metalog.conf &quot;crond&quot; vs &quot;cron&quot;</short_desc>
          <delta_ts>2003-10-16 19:57:14 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>Applications</component>
          <version>1.2</version>
          <rep_platform>All</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          
          <priority>P2</priority>
          <bug_severity>minor</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>mak-gentoo-bugzilla@greenhills.co.uk</reporter>
          <assigned_to>pebenito@gentoo.org</assigned_to>
          

      

      
          <long_desc isprivate="0">
            <who>mak-gentoo-bugzilla@greenhills.co.uk</who>
            <bug_when>2002-11-20 11:43:35 0000</bug_when>
            <thetext>metalog.conf uses program name &quot;crond&quot; in it&apos;s Crond section.    
    
http://lists.gentoo.org/pipermail/gentoo-announce/2002-April/000151.html     
suggests that dcron is the Gentoo default, and that has a &quot;crond&quot;.     
http://www.gentoo.org/doc/en/gentoo-x86-install.xml     
suggests using vcron, and that has a &quot;cron&quot; instead.  
It also recommends metalog.    
    
So if you use the recommended metalog and vcron together, 
you get cron messages only in /var/log/everything/, not /var/log/crond.    
    
I found that a little surprising. Not sure what (if anything) to do    
about it. Perhaps metalog&apos;s ebuild file should warn you to change  
metalog.conf if you use it with vcron?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>mkeadle@gmail.com</who>
            <bug_when>2002-12-02 03:44:06 0000</bug_when>
            <thetext>From what I can see:

dcron = crond
fcron = fcron
vcron = cron

So the only cron that will work out-o-the-box is dcron, while the other two need
.conf adjustments in metalog.

I&apos;m wondering if it might do some good to switch:

program  = &quot;crond&quot;

to:

facility = &quot;cron&quot;

in metalog.conf. That should cover capture of all cron messages regardless of
which cron is being used. </thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>mak-gentoo-bugzilla@greenhills.co.uk</who>
            <bug_when>2002-12-02 07:52:37 0000</bug_when>
            <thetext>Sounds good to me; I&apos;ve changed my metalog.conf accordingly.

You might also consider using:

  logdir   = &quot;/var/log/cron&quot;

instead of:

  logdir   = &quot;/var/log/crond&quot;

although I could imagine such a change could cause some confusion.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>pebenito@gentoo.org</who>
            <bug_when>2003-10-15 20:09:23 0000</bug_when>
            <thetext>Wow this bug has been idling around for a long time.  I&apos;ve got facility =
&quot;cron&quot; in my config, and I use vcron fine.  I&apos;ll try to find out if it works
with d/fcron too.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>pebenito@gentoo.org</who>
            <bug_when>2003-10-16 19:57:14 0000</bug_when>
            <thetext>Ok, this change is committed to CVS.  Vcron and fcron work with facility,
and I couldn&apos;t get dcron to log to syslog.  If dcron does log to syslog,
but not using the cron facility, then its got the problem.</thetext>
          </long_desc>
      
    </bug>

</bugzilla>