On Dec 9, 2011, at 1:59 AM, Alexander Dalloz wrote:
> Am 09.12.2011 01:03, schrieb Reindl Harald:
>
>> why are radnom people try to tell me how i have to do my job
>> without knowing anyting about how i work?
>>
>> no there is no need on the production machine becuase all preparing
>> happens o
Am 09.12.2011 09:59, schrieb Alexander Dalloz:
> Am 09.12.2011 01:03, schrieb Reindl Harald:
>
>> why are radnom people try to tell me how i have to do my job
>> without knowing anyting about how i work?
>>
>> no there is no need on the production machine becuase all preparing
>> happens on a de
Am 09.12.2011 01:03, schrieb Reindl Harald:
> why are radnom people try to tell me how i have to do my job
> without knowing anyting about how i work?
>
> no there is no need on the production machine becuase all preparing
> happens on a dedicated environment with where local and caching repos
>
On Fri, Dec 9, 2011 at 1:03 PM, Reindl Harald wrote:
>
>
> Am 09.12.2011 00:53, schrieb Cliff Pratt:
>> On Fri, Dec 9, 2011 at 10:07 AM, Reindl Harald
>> wrote:
>>>
>>>
>>> Am 08.12.2011 22:04, schrieb Les Mikesell:
On Thu, Dec 8, 2011 at 2:25 PM, Reindl Harald
wrote:
>
> Am
Am 09.12.2011 00:53, schrieb Cliff Pratt:
> On Fri, Dec 9, 2011 at 10:07 AM, Reindl Harald wrote:
>>
>>
>> Am 08.12.2011 22:04, schrieb Les Mikesell:
>>> On Thu, Dec 8, 2011 at 2:25 PM, Reindl Harald
>>> wrote:
Am 08.12.2011 21:08, schrieb Cliff Pratt:
> It's a good idea NOT to p
On Fri, Dec 9, 2011 at 9:25 AM, Reindl Harald wrote:
>
>
> Am 08.12.2011 21:08, schrieb Cliff Pratt:
>> It's a good idea NOT to put stuff in /etc/crontab and NOT to change
>> the existing members of /etc/cron.d. It is a good idea NOT to change
>> root's crontab. Any of these may get overwritten by
On Fri, Dec 9, 2011 at 10:07 AM, Reindl Harald wrote:
>
>
> Am 08.12.2011 22:04, schrieb Les Mikesell:
>> On Thu, Dec 8, 2011 at 2:25 PM, Reindl Harald wrote:
>>>
>>> Am 08.12.2011 21:08, schrieb Cliff Pratt:
It's a good idea NOT to put stuff in /etc/crontab and NOT to change
the existi
On Thu, Dec 8, 2011 at 3:07 PM, Reindl Harald wrote:
>
>>> fedora did not overwrite any crontab from FC5 to F15 now because
>>> rpm-packages mark such configurations so the new versions get installed
>>> as .rpmnew
>>
>> Which means the changes those versions would like to have made won't
>> take
Am 08.12.2011 22:04, schrieb Les Mikesell:
> On Thu, Dec 8, 2011 at 2:25 PM, Reindl Harald wrote:
>>
>> Am 08.12.2011 21:08, schrieb Cliff Pratt:
>>> It's a good idea NOT to put stuff in /etc/crontab and NOT to change
>>> the existing members of /etc/cron.d. It is a good idea NOT to change
>>> r
On Thu, Dec 8, 2011 at 2:25 PM, Reindl Harald wrote:
>
> Am 08.12.2011 21:08, schrieb Cliff Pratt:
>> It's a good idea NOT to put stuff in /etc/crontab and NOT to change
>> the existing members of /etc/cron.d. It is a good idea NOT to change
>> root's crontab. Any of these may get overwritten by m
Am 08.12.2011 21:08, schrieb Cliff Pratt:
> It's a good idea NOT to put stuff in /etc/crontab and NOT to change
> the existing members of /etc/cron.d. It is a good idea NOT to change
> root's crontab. Any of these may get overwritten by maintenance.
/etc/crontab will NEVER get overwritten
to mak
It's a good idea NOT to put stuff in /etc/crontab and NOT to change
the existing members of /etc/cron.d. It is a good idea NOT to change
root's crontab. Any of these may get overwritten by maintenance.
We generally put cron stuff in a locally named and created member in
/etc/cron.d.
Cheers,
Clif
>From man 8 cron
Cron searches /var/spool/cron for crontab files which are
named
after accounts ... Cron also
searches for /etc/crontab and the files in the directory, which
are
in a different format (see crontab(5) ).
So cron itself knows about /etc/cron.d and
13 matches
Mail list logo
