syslogd

[issinoho]

Has anyone successfully ported/compiled the freeware syslogd package available from the VMS Software Freeware pages to x86?
Here's what I get when I try a naive compile...

Code: Select all

@build_syslogd

        return;
........^
%CC-W-NORETURNVAL, The function "main" returns a value, but no value is given in
 this return statement.
at line number 389 in file DKA100:[TEMP.syslogd.src]logger.c;1

    return;
....^
%CC-W-NORETURNVAL, The function "main" returns a value, but no value is given in
 this return statement.
at line number 431 in file DKA100:[TEMP.syslogd.src]logger.c;1
%ILINK-F-OPENIN, error opening SYS$COMMON:[SYSLIB]ucx$ipc.olb; as input
-RMS-E-FNF, file not found
%DCL-W-SKPDAT, image data (records not beginning with "$") ignored

[sms]

Code: Select all

> Has anyone successfully ported/compiled [...]

   Not I.  (Not even unsuccessfully.)

> [...] the freeware syslogd package available from the VMS Software
> Freeware pages [...]

   Thanks for the helpful link.

> [...] to x86?

   How old is that code?  From those complaints, I'd guess that any
recent VMS version on any hardware would see the same problems.  Instant
advice from someone who hasn't looked at the code or the builder(s):

> %CC-W-NORETURNVAL, [...]

   Fix the code, or ignore the warning?

> %ILINK-F-OPENIN, [...] ucx$ipc.olb [...]

   UCX?  How old is that code?

   Change the LINK command (or options file) to use:
      SYS$LIBRARY:TCPIP$IPC_SHR.EXE /SHAREABLE
instead uf:
      SYS$LIBRARY:UCX$IPC.OLB /LIBRARY
which seems not to be distributed these days?

      dire sys$library:*ipc*

   Look for newer/better syslogd code?

[imiller]

Here is the source if anyone as the time to try

https://vms.process.com/scripts/fileser ... D=&RM=&RY=

[issinoho]

Ok, turns out it was a very easy fix - a few code fixups and changes to the build script combined with these instructions means I now have a fully functioning syslogd daemon running on x86, https://vmssoftware.com/docs/syslogd-op ... b-2018.pdf

My code is available here,

Code: Select all

git@bitbucket.org:drunkenbaker/syslogd.git

Thanks for the help.

[arne_v]

If you need something newer but with less features, then https://github.com/intoolswetrust/simple-syslog-server runs fine on VMS. Download ZIP to PC, build with maven, upload jar to VMS and run.

[sms]

Code: Select all

>    Not I.  (Not even unsuccessfully.)

   Hmmm.  Less true than I'd thought.  I seem to have done things with
this stuff, but it was back around 21-APR-2004, so I probably didn't
consider IA64, let alone x86_64.

   Apparently, though, I simplified the builder for "modern"
environments (making it approximately universal?):

ITS $ type BUILD_SYSLOGD.COM
$!
$!  Compile and Link syslogd and logger
$!
$!  Compile and link.
$!
$ cc logger
$ link logger
$ cc syslogd
$ link /notraceback syslogd
$!

which seems to work around here:

V87 $ @ BUILD_SYSLOGD.COM
V87 $ 

V87 $ tcpip show version

  VSI TCP/IP Services for OpenVMS x86_64 Version V6.0
  on a VMware, Inc. VMware20,1 running OpenVMS V9.2-2  


   If anyone cares, I could post the modified C modules, too: LOGGER.C,
SYSLOGD.C.  (The fact that the file names are upper-case suggests that I
still had ODS2 system disks back then.)

   I don't remember doing any actual testing, but it compiled and
linked (then and now), so what could go wrong?

[jonesd]

I wrote a syslog daemon 20 years ago and found the data sent to it tended to be noisy and bursty. It's easy to end up with a lot of marginally useful data to wade through.

[arne_v]

I wrote a syslog daemon 20 years ago and found the data sent to it tended to be noisy and bursty. It's easy to end up with a lot of marginally useful data to wade through.

I think the days of manual reading such logs are long gone.

You log hundreds of MB or maybe some GB. And then you use tools to search in the data.

ELK, EFK etc..

[sms]

Code: Select all

>    If anyone cares, I could post [...]

   I failed to resist the temptation:

      http://antinode.info/dec/sw/syslogd.html

   Still no testing (by me) beyond compile+link, but the build worked on
Alpha, IA64, VAX, and x86_64.  The new builder creates a subdirectory
for each hardware architecture, instead of using ".EXE_xxx" types.

   Complaints are always welcome.

[jonesd]

I think the days of manual reading such logs are long gone.

You log hundreds of MB or maybe some GB. And then you use tools to search in the data.

ELK, EFK etc..

That was kind of my point, getting syslogd running on your VMS box probabily also needs other tools (at the very least something like Perl).