Re: daemon not really doing anything on Fedora 13

So it seems to be working pretty well now. I created a script that actually contains my regex and functions. Now incron gets triggered and then looks at that file, which probably what I should have done in the first place.

One thing I've noticed, though, is that the terminal I start my incrond service in is going nuts with all sorts of activity. I am running the daemon via /etc/init.d/incrond.

Is there a way to quiet the output? Or does it just go away if it's run at boot up via runlevels?

Thanks,

Mike
On Jul 28, 2010, at 11:06 AM, Matthew Miller wrote:

> On Wed, Jul 28, 2010 at 10:23:01AM -0600, Mike Young wrote:
>>> My guess is that what's happening is that the log file is being created
>>> with permissions determined by the umask, and then chmodded. So, when
>>> you do the chmod on file creation with incron, that works, but then
>>> immediately after the application sets it back.
>> The problem is that log files get rolled with a time stamp and then a new,
>> blank one is created. When the new one is created with 644, the app no
>> longer works. Changing the log via a cron takes care of the problem. But
>> then I have the down time in between. This deals with it right from the
>> start. Plus, I can use this for other items not related to this log issue.
>
> Yeah. So what I'm suggesting is that changing permissions on IN_CREATE may
> be *too soon*.
>
>
> --
> Matthew Miller blocked-address <http://mattdm.org/>
Received on Tue Jun 05 2012 - 22:14:21 CEST