Prev: awesome on slackware64-current
Next: Company dress code with no exceptions!
From: nospam on 21 Feb 2010 09:12
I suspect this has been asked a lot of times before but I could not find
an answer using Google. Why is the default logging of popa3d to
/var/log/messages and the only way to change it is to recompile?

I have tried the suggestions at

http://www.openwall.com/lists/popa3d-users/2006/05/11/1

and that stops all logging.

It would seem to me that it could be configured right from the beginning
as a defautl to let syslog determine where the logging went. If the
user wanted a separate log file he could use

popa3d.* -/var/log/popa3dlog

or if the user wanted the logging in messages he could remove the popa3d
directive and the popa3d.none from the /var/log/messages directive so it
default to messages.

I just don't understand why the default would force a user to recompile
each time he does an install or there is a popa3d upgrade if he wants to
log other than to the message file. It is not that way for the sendmail
daemon. It makes not sense to me. What am I missing?

From: Loki Harfagr on 21 Feb 2010 12:11
Sun, 21 Feb 2010 09:12:29 -0500, nospam did cat :

> I suspect this has been asked a lot of times before but I could not find
> an answer using Google.

> User-Agent: MicroPlanet-Gravity/2.70.2067

Zimmer off windblock tröll!
(sorry, guess DanC's sleeping now ;-)

> Why is the default logging of popa3d to
> /var/log/messages and the only way to change it is to recompile?
>
> I have tried the suggestions at
>
> http://www.openwall.com/lists/popa3d-users/2006/05/11/1
>
> and that stops all logging.

strange, that *should* work (any of the two methods exposed)
at least it used to, I don't have any popa3d setup available
anywhere but I just tried a check up and it worked flawlessly with
the syslog method, here's the simple diff -U 1 of syslog.conf :
---------
--- /etc/syslog.conf.orig 2010-02-21 18:04:29.789926401 +0100
+++ /etc/syslog.conf 2010-02-21 18:01:51.334550447 +0100
@@ -15,2 +15,3 @@
*.info;*.!warn;\
+ popa3d.none;\
authpriv.none;cron.none;mail.none;news.none -/var/log/messages
@@ -34,2 +35,6 @@

+# Popa3d related logs:
+!!popa3d
+*.* -/var/log/popa3d
+
# Emergency level messages go to all users:
---------

Now, I'd try and guess your problems may be in that you're trying and
use popa3d 'under' inetd or other wrapper? That could make a difference.

> It would seem to me that it could be configured right from the beginning
> as a defautl to let syslog determine where the logging went.

But it is, at least for real standalone server mode :-)

> If the
> user wanted a separate log file he could use
>
> popa3d.* -/var/log/popa3dlog
>
> or if the user wanted the logging in messages he could remove the popa3d
> directive and the popa3d.none from the /var/log/messages directive so it
> default to messages.
>
> I just don't understand why the default would force a user to recompile
> each time he does an install or there is a popa3d upgrade if he wants to
> log other than to the message file. It is not that way for the sendmail
> daemon. It makes not sense to me. What am I missing?

good question!-)
From: jr4412 on 21 Feb 2010 13:42
On 21 Feb, 14:12, <nos...(a)notreal.com> wrote:
> I suspect this has been asked a lot of times before but I could not find
> an answer using Google.   Why is the default logging of popa3d to
> /var/log/messages and the only way to change it is to recompile?  
>
> I have tried the suggestions at
>
> http://www.openwall.com/lists/popa3d-users/2006/05/11/1
>
> and that stops all logging.  
>
> It would seem to me that it could be configured right from the beginning
> as a defautl to let syslog determine where the logging went.  If the
> user wanted a separate log file he could use
>
> popa3d.*                                            -/var/log/popa3dlog
>
> or if the user wanted the logging in messages he could remove the popa3d
> directive and the popa3d.none from the /var/log/messages directive so it
> default to messages.
>
> I just don't understand why the default would force a user to recompile
> each time he does an install or there is a popa3d upgrade if he wants to
> log other than to the message file.  It is not that way for the sendmail
> daemon. It makes not sense to me.  What am I missing?

from the link:

"recompile popa3d... Before it, RTFInstall instructions-- change the
logging
facility on params.h from default to

#define SYSLOG_FACILITY LOG_LOCAL0

create an entry for that login facility on your /etc/syslog.conf
file.

....

Make the following entry on your /etc/syslog.conf file

#vi /etc/syslog.conf

!!popa3d
*.* -/var/log/popa3d"

but if you changd the header file as suggested, the entry in '/etc/
syslog.conf' ought to then read:

# popa3d
local0.*<Tab>-/var/log/popa3d

HTH
From: nospam on 21 Feb 2010 19:54
In article <135d8bb7-0575-4039-aa45-e3dbbbd96fe0
@i39g2000yqm.googlegroups.com>, jr4412(a)googlemail.com says...
> On 21 Feb, 14:12, <nos...(a)notreal.com> wrote:
> > I suspect this has been asked a lot of times before but I could not find
> > an answer using Google.   Why is the default logging of popa3d to
> > /var/log/messages and the only way to change it is to recompile?  
> >
> > I have tried the suggestions at
> >
> > http://www.openwall.com/lists/popa3d-users/2006/05/11/1
> >
> > and that stops all logging.  
> >
> > It would seem to me that it could be configured right from the beginning
> > as a defautl to let syslog determine where the logging went.  If the
> > user wanted a separate log file he could use
> >
> > popa3d.*                                            -/var/log/popa3dlog
> >
> > or if the user wanted the logging in messages he could remove the popa3d
> > directive and the popa3d.none from the /var/log/messages directive so it
> > default to messages.
> >
> > I just don't understand why the default would force a user to recompile
> > each time he does an install or there is a popa3d upgrade if he wants to
> > log other than to the message file.  It is not that way for the sendmail
> > daemon. It makes not sense to me.  What am I missing?
>
> from the link:
>
> "recompile popa3d... Before it, RTFInstall instructions-- change the
> logging
> facility on params.h from default to
>
> #define SYSLOG_FACILITY LOG_LOCAL0
>
> create an entry for that login facility on your /etc/syslog.conf
> file.
>
> ...
>
> Make the following entry on your /etc/syslog.conf file
>
> #vi /etc/syslog.conf
>
> !!popa3d
> *.* -/var/log/popa3d"
>
> but if you changd the header file as suggested, the entry in '/etc/
> syslog.conf' ought to then read:
>
> # popa3d
> local0.*<Tab>-/var/log/popa3d
>
> HTH
>

I think you are suggesting that I will have to recompile and then make
changes to syslog.conf based on the recompiling that are different from
the changes shown in the URL. That it is certainly a solution (thank
you) but I am still curious as to why they have a default configuration
makes that necessary.

From: nospam on 21 Feb 2010 20:01
In article <pan.2010.02.21.17.11.51(a)thedarkdesign.free.fr.INVALID>, l0k1
@thedarkdesign.free.fr.INVALID says...
> Sun, 21 Feb 2010 09:12:29 -0500, nospam did cat :
>
> > I suspect this has been asked a lot of times before but I could not find
> > an answer using Google.
>
> > User-Agent: MicroPlanet-Gravity/2.70.2067
>
> Zimmer off windblock tröll!
> (sorry, guess DanC's sleeping now ;-)
>

??????????????


> > Why is the default logging of popa3d to
> > /var/log/messages and the only way to change it is to recompile?
> >
> > I have tried the suggestions at
> >
> > http://www.openwall.com/lists/popa3d-users/2006/05/11/1
> >
> > and that stops all logging.


My error. The stopping of all logging resulted from a variation of the
syslog configuration that I tried after the first run using the
configuration as shown in the above URL did not work.

I configured syslog.conf as you suggested, which seems to be just
a typographical variation of the URL suggestion, and what happened is
that I not only had the popa3d messages in the "popa3d" log file but all
the other messages that normally get logged to the "messages" file as
well. Nothing gets logged to "messages" with that configuration.

This is also what happened earlier, and what prompted the trial and
error changes that resulted in a configuration that stopped all logging
and which I reported in error. My apologies for the confusion.


>
> strange, that *should* work (any of the two methods exposed)
> at least it used to, I don't have any popa3d setup available
> anywhere but I just tried a check up and it worked flawlessly with
> the syslog method, here's the simple diff -U 1 of syslog.conf :
> ---------
> --- /etc/syslog.conf.orig 2010-02-21 18:04:29.789926401 +0100
> +++ /etc/syslog.conf 2010-02-21 18:01:51.334550447 +0100
> @@ -15,2 +15,3 @@
> *.info;*.!warn;\
> + popa3d.none;\
> authpriv.none;cron.none;mail.none;news.none -/var/log/messages
> @@ -34,2 +35,6 @@
>
> +# Popa3d related logs:
> +!!popa3d
> +*.* -/var/log/popa3d
> +
> # Emergency level messages go to all users:
> ---------



I think this is what I tried the first time. The only difference is the
first line where I had

-------
# Exclude authpriv, cron, mail, and news. These are logged elsewhere.
*.info;*.!warn;\
authpriv.none;cron.none;mail.none;popa3d.none;\
news.none -/var/log/messages

------

but I would not think that should make a difference.



>
> Now, I'd try and guess your problems may be in that you're trying and
> use popa3d 'under' inetd or other wrapper? That could make a difference.
>
> > It would seem to me that it could be configured right from the beginning
> > as a defautl to let syslog determine where the logging went.
>
> But it is, at least for real standalone server mode :-)

I am running it as a standalone server starting it with rc.popa3d in
/etc/rc.d using /usr/sbin/popa3d -D

>
> > If the
> > user wanted a separate log file he could use
> >
> > popa3d.* -/var/log/popa3dlog
> >
> > or if the user wanted the logging in messages he could remove the popa3d
> > directive and the popa3d.none from the /var/log/messages directive so it
> > default to messages.
> >
> > I just don't understand why the default would force a user to recompile
> > each time he does an install or there is a popa3d upgrade if he wants to
> > log other than to the message file. It is not that way for the sendmail
> > daemon. It makes not sense to me. What am I missing?
>
> good question!-)
>

Is this in answer to "What am I missing" or why it is configured by
default the way it is? I am sure there must be a reason for the default
configuration but it sure beats the heck out of me as to what it is.

 |  Next  |  Last
Pages: 1 2
Prev: awesome on slackware64-current
Next: Company dress code with no exceptions!