[horde] Horde logging. Syslog options

[Vilius Šumskas]

Sveiki,

Wednesday, September 28, 2011, 11:04:27 PM, you wrote:

>> -----Original Message-----
>> From: horde-bounces at lists.horde.org [mailto:horde-
>> bounces at lists.horde.org] On Behalf Of Michael J Rubinsky
>> Quoting Simon Brereton <simon.brereton at buongiorno.com>:
>> 
>> >> -----Original Message-----
>> >> From: horde-bounces at lists.horde.org [mailto:horde-
>> >> bounces at lists.horde.org] On Behalf Of Torsten Krah
>> >>
>> >> Am Mittwoch, den 28.09.2011, 11:48 -0400 schrieb Simon Brereton:
>> >> > My next question, therefore, is - what are the pros and cons of
>> >> using
>> >> > Syslog?  Does anyone use the syslog option - and if so, why?
>> How
>> >> do
>> >> > you have that setup?
>> >>
>> >> I am using the syslog option - main reasons is that i have logging
>> >> delegated to well known syslog stuff. Using syslog you are able to
>> >> use all features you can to with your syslog implementation.
>> >> Don't know about cons - maybe someone else do ;).
>> >>
>> >> horde config:
>> >>
>> >> $conf['log']['priority'] = 'INFO';
>> >> $conf['log']['ident'] = 'HORDE';
>> >> $conf['log']['name'] = LOG_LOCAL7;
>> >> $conf['log']['type'] = 'syslog';
>> >> $conf['log']['enabled'] = true;
>> >>
>> >>
>> >> syslog (using rsyslog) is configured like this:
>> >>
>> >> local7.*                        -/var/log/horde.log
>> >>
>> >> /etc/logrotate.d/rsyslog - append the /var/log/horde.log file to
>> be
>> >> rotated.
>> >>
>> >> Thats the setup, works very well.
>> >
>> > I thank you.  That works!  But how do you get the sync to log?
>> > Presumably, I just revert to $conf[activesync][logging][type]=Horde
>> > and then either make local7.sync to log to /var/log/horde/sync.log
>> and
>> > update /etc/logrotate.d/rsyslog is there some other way to do it?
>> 
>> No idea about the syslog stuff, but with activesync logging set to
>> 'Horde', all activesync related messages are logged to your Horde
>> log.
>> If you want activesync to log messages to a separate file, set it to
>> 'Custom' and enter the path to a log file to receive the activesync
>> log messages. The 'Custom' log can only write to a separate text
>> file, it doesn't have the ability to write to syslog.

> Yes, that's why I want to do it that way.  But I can't if I keep
> getting the Horde_Log_Handler_Stream: "/var/log/horde/horde4.log"
> cannot be opened with mode "a+" error.

So  now,  when you get at least error in the logs, what happens if you
log to /tmp/horde.log ?

-- 
Best regards,
 Vilius