Re: Syslogd in PASE - another port instead of 514

As a general statement - you cannot reliably use Linux documentation for PASE utilities - nor for QShell utilities - you have to use AIX for things in PASE (and the correct version of AIX), and you have to go to the QShell documentation for QShell utilities.

Every Unix/Linux OS has its own versions of all these utilities. And the various shells all behave differently - QShell is sometimes the same as things like bash and ksh - but it can't be relied on.

HTH
Vern

On 12/29/2014 10:32 AM, Zvi Kave wrote:

David,

From Linux documentation I saw that -p is for output not input (/dev/log).

-p socket
You can specify an alternative unix domain socket instead of /dev/log.

So there is no chance to use "-p" for input socket.
On the other hand, "-a" is missing in PASE syslogd arguments.
In Linux documentation it is used just for that:
-a socket
Using this argument you can specify additional sockets from that
syslogd has to listen to. This is needed if you're going to let
some daemon run within a chroot() environment. You can use up
to 19 additional sockets. If your environment needs even more,
you have to increase the symbol MAXFUNIX within the syslogd.c
source file. An example for a chroot() daemon is described by
the people from OpenBSD at
[1]http://www.psionic.com/papers/dns.html.

Nevertheless, I tried your suggestion, but no change.


Regards,

Zvi

On 29/12/2014 16:10, David Gibbs wrote:

On 12/25/14 4:37 AM, Zvi Kave wrote:

I tried as you suggested with " /usr/sbin/syslogd -p 5555 " but it
still gets messages from port 514 only, not 5555. Did I miss
something ?

OK, this is a complete WAG (Wild A-- Guess), but I noticed that most of
the man pages for syslogd indicate that the -p arg is supposed to be a
unix domain socket.

Have you tried launching syslogd with -p inet:5555 ?

david

References

Visible links
1. http://www.psionic.com/papers/dns.html