Michael Kapp wrote:
> 1. Logging Format
> 
> Logging in heartbeat-v2.07
> 
> All heartbeat components are logging like this:
> 
> Example:
> ========
> 
> cib: [32185]
> 
> but i think it has to look as the standard format:
> 
> Example:
> ========
> 
> smtpd[10799]:

I suspect this could be changed.  But, it turns out to be easier to grep
for messages from particular subsystems if they're in the format we use.

> ?
> 
> #=========================================================
> 
> 2. Why does the default ha_logd.cf file has to be in /etc?
> 
> The hearbeat logfile says:
> 
> 2006-11-13 16:37:55 +01:00; node1; local7.info; heartbeat: [18382]:
> info: logfile and debug file are those specified in logd config file
> (default /etc/logd.cf)
> 
> The place of ha_logd.cf should be in /etc/ha.d or /etc/ha.d/conf?

I don't know who created the conf directory -- but it's not much used.

With regard to the log file name, logd isn't really specific to
Linux-HA, and we had some other folks be interested in using it.  So, we
chose (maybe wrongly) to locate it in /etc directly - in a probably vain
attempt to encourage reuse.

> So i have to put a symlink to it...
> 
> $> ln -s ha.d/ha_logd.cf logd.cf
> 
> #=========================================================
> 
> 3. Why is the logd configuration file in the heartbeat logfile called
> logd.cf and as an examples hearbeat provides
> /usr/share/doc/heartbeat-2.0.7-r2/ha_logd.cf.gz (gentoo)?

Sounds broken.

> #=========================================================
> 
> 4. Why does
> 
> $> man ha_logd
> 
> not say where the logfile configuration has to be?
> 
> There is also a typo in the man page of ha_logd:
> 
> ...User can configure log file, debuf file...
> 
> should be
> 
> ...User can configure log file, debug file...
> 
> #=========================================================
> 
> 5. Can someone explain me the functionality of ha_logd in detail please
> (is it used as "fallback" logger daemon, if yes how etc.)?

It is a NON-BLOCKING logging daemon.  We've seen syslog get many
hundreds of messages behind when logging is cranked up.  Heartbeat can't
tolerate that kind of anti-social blocking behavior ;-)


> #=========================================================
> 
> 6. @all gentoo users, there is also a bug in the init-script of
> heartbeat (2.0.7-r2) ha_logd not starting and stopping - bug reported
> (http://bugs.gentoo.org/show_bug.cgi?id=155106) - patch attached
> (heartbeat.ha_logd.diff).

Is this in our source base?


> #=========================================================
> 
> 7. I think the logging of heartbeat should be improved to a more
> transparent and readable format(!?).

I think the big problem is how much we do (that is we log things no one
cares about), and secondarily how clear the messages are.  I don't think
things like foo[pid}: are the problem.  But maybe you don't think that's
the real problem either.



-- 
    Alan Robertson <[EMAIL PROTECTED]>

"Openness is the foundation and preservative of friendship...  Let me
claim from you at all times your undisguised opinions." - William
Wilberforce
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/

Reply via email to