Hi Mark, I started it from /etc/rc because having it configured from TCPIP's AUTOLOG the result was just the message of the subject, and it ended. So I commented out the AUTOLOG statement regarding SYSLOG, and I subsequently configured SYSLOG to be started from /etc/rc. I am not starting it from two different places. The result is that starting it from /etc/rc works, but letting TCPIP start it using the AUTOLOG feature ends with the message "already active".
On Mon, Oct 8, 2012 at 5:49 PM, Mark Zelden <m...@mzelden.com> wrote: > On Mon, 8 Oct 2012 16:31:39 +0200, IT Pro <bilit...@gmail.com> wrote: > >>We have customized /etc/rc to include the start of syslog, very >>similar to what you say, and it works like that: >> >>_BPX_JOBNAME='SYSLOGT' /usr/sbin/syslogd -d -c -u -f >>/usr/local/etc/syslogd.conf & >> > > Well then you've answered your own question. If you are starting > it via /etc/rc, then when you try to start it from a > console START command or AUTOLOG it will have already > been active and you will see the message you are seeing. > > Choose only one method to start it (I prefer /etc/rc). > > Regards, > > Mark > -- > Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS > mailto:m...@mzelden.com > Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html > Systems Programming expert at http://expertanswercenter.techtarget.com/ > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
