Hi, Yes, I want the option of silent operation. I run the sync from cron, I don't want output every 15minutes! But I do want output if there is an error. I suppose I could just pipe stdout into /dev/null. Still it would be nice if one could control what is output. Matt
On Mon, Aug 17, 2015 at 9:40 PM, Sriram Karra <[email protected]> wrote: > Hm... Is it because you want a totally silent operation? > > I have it this way because the logger is not set up before the config is > being applied. So these will appear as config lines only to console and not > to the log file itself which can be confusing. > > On Mon, Aug 17, 2015 at 2:25 PM, mwilkins <[email protected]> wrote: >> >> >> Hi, >> >> Any chance you could apply this patch? It stops the printing of the >> four lines of information, rather logging.info is used. So if you >> don't want output you can set the log level and not pipe stdout to >> /dev/null. >> >> Thanks >> >> --- state.py.orig 2015-08-17 20:51:21.076719747 +1200 >> +++ state.py 2015-08-17 20:51:24.684827243 +1200 >> @@ -70,9 +70,9 @@ >> self._migrate_config_if_reqd(self.confi_curr_ver) >> >> try: >> - print 'Applying base config from file %s...' % self.confn >> + logging.info('Applying base config from file %s...' % >> self.confn) >> confi = open(self.confn, "r") >> - print 'Applying base config from file %s...done' % self.confn >> + logging.info('Applying base config from file %s...done' % >> self.confn) >> except IOError, e: >> print 'Error! Could not Open file (%s): %s' % (self.confn, e) >> raise >> @@ -86,9 +86,9 @@ >> stc = demjson.decode(confi.read()) >> sts = demjson.decode(statei.read()) >> >> - print 'Applying user customizations from file %s...' % >> self.confpy >> + logging.info('Applying user customizations from file %s...' % >> self.confpy) >> self._customize_config(self.confpy, stc) >> - print 'Applying user customizations from file %s...done' % >> self.confpy >> + logging.info('Applying user customizations from file %s...done' % >> self.confpy) >> >> # # A sample profile is given in the initial distribution, that >> should >> # # not be written back to the file. Do the needful. >> >> Matt >> >> -- >> You received this message because you are subscribed to the Google Groups >> "ASynK Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send an email to [email protected]. >> To view this discussion on the web, visit >> https://groups.google.com/d/msgid/asynk/20150817085528.GA17491%40stoker. >> For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "ASynK Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/asynk/AS-DhUTqFUY/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web, visit > https://groups.google.com/d/msgid/asynk/CAFkt3UP_C05rk4C26cej%2Bmc-%3Ds7f4sySGMrFF7SKp%2BosKgdA6Q%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "ASynK Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send an email to [email protected]. To view this discussion on the web, visit https://groups.google.com/d/msgid/asynk/CADH-zAcGpyQk9R2osoq%2BOY-k1H-3EytuGrB03nSjoBL_cUacHQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
