You're right. Reboot works fine. But stop the service and restart looks like a debug session with everything going to stdout.
Mike
-- Sent from my Palm Pre
On Jul 28, 2010 5:49 PM, David Ward <david_at_dward.us> wrote:
That is right Mike.
A normal system startup shouldn't see the daemon write to all ttys.
I am surprised that
/etc/init.d/incrond start
is doing this, actually.
-- Regards David Ward On Wed, 28 Jul 2010 15:13:07 -0600, Mike Young <myoung_at_wildernessvoice.com> wrote: > 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 mattdm_at_mattdm.org <http://mattdm.org/>Received on Tue Jun 05 2012 - 22:14:21 CEST
This archive was generated by hypermail 2.2.0 : Tue Jun 05 2012 - 22:14:21 CEST