• Re: syslog setup

    From Lawrence D'Oliveiro@21:1/5 to Paul Coviello on Wed Jun 12 20:16:47 2024
    On Wed, 12 Jun 2024 14:25:44 -0400, Paul Coviello wrote:

    this is what I have currently from this file https://vmssoftware.com/docs/syslogd-openvms-04-Feb-2018.pdf:

    I notice it says to be sure to use tabs, not spaces, to separate the facility/severity spec from the destination spec. There’s even an option
    to send the messages to OPCOM, too, which might be useful.

    There’s an example “logger” command to send a test log message; did you get as far as trying that?

    Just guessing, here; I have zero familiarity with syslog on VMS.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lawrence D'Oliveiro@21:1/5 to Paul Coviello on Mon Jun 17 21:06:54 2024
    On Wed, 12 Jun 2024 16:47:11 -0400, Paul Coviello wrote:

    I do have a call with VSI tomorrow, though I'm not sure what yet will
    come out of it.

    How did it go?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Simon Clubley@21:1/5 to Paul Coviello on Wed Jun 19 12:08:01 2024
    On 2024-06-18, Paul Coviello <pcoviello@gmail.com> wrote:
    Lawrence D'Oliveiro wrote:
    On Wed, 12 Jun 2024 16:47:11 -0400, Paul Coviello wrote:

    I do have a call with VSI tomorrow, though I'm not sure what yet will
    come out of it.

    How did it go?

    well... I was asked if I would like professional services in helping to
    set this up, since we need to have this for some auditing purpose, I
    said yes, but I asked them to check to see if anyone knew how before
    they sent over a quote, I thought it was a fair question :-)

    :-)

    And did they confirm someone at VSI knows how to set it up ? :-)

    Simon.

    --
    Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
    Walking destinations on a map are further away than they appear.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Chris Townley@21:1/5 to Simon Clubley on Wed Jun 19 13:37:40 2024
    On 19/06/2024 13:08, Simon Clubley wrote:
    On 2024-06-18, Paul Coviello <pcoviello@gmail.com> wrote:
    Lawrence D'Oliveiro wrote:
    On Wed, 12 Jun 2024 16:47:11 -0400, Paul Coviello wrote:

    I do have a call with VSI tomorrow, though I'm not sure what yet will
    come out of it.

    How did it go?

    well... I was asked if I would like professional services in helping to
    set this up, since we need to have this for some auditing purpose, I
    said yes, but I asked them to check to see if anyone knew how before
    they sent over a quote, I thought it was a fair question :-)

    :-)

    And did they confirm someone at VSI knows how to set it up ? :-)

    Simon.


    and perhaps they should document it!

    --
    Chris

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jim Duff@21:1/5 to Paul Coviello on Sat Jun 22 08:59:07 2024
    On 21/6/24 22:19, Paul Coviello wrote:
    Chris Townley wrote:
    On 19/06/2024 13:08, Simon Clubley wrote:
    On 2024-06-18, Paul Coviello <pcoviello@gmail.com> wrote:
    Lawrence D'Oliveiro wrote:
    On Wed, 12 Jun 2024 16:47:11 -0400, Paul Coviello wrote:

    I do have a call with VSI tomorrow, though I'm not sure what yet will >>>>>> come out of it.

    How did it go?

    well...  I was asked if I would like professional services in
    helping to
    set this up, since we need to have this for some auditing purpose, I
    said yes, but I asked them to check to see if anyone knew how before
    they sent over a quote, I thought it was a fair question :-)

    :-)

    And did they confirm someone at VSI knows how to set it up ? :-)

    Simon.


    and perhaps they should document it!

    no confirmation yet, and absolutely agree there should be something
    telling you how to set it up instead of leading you to believe just by
    adding in the opcom section it works... it doesn't there is some other setting I don't know.

    Silly question, but can you describe what you're expecting to happen
    that doesn't?

    I built this from the source included in the zip file and there are
    certainly a few quirks with it, but I don't know if the same are present
    in the prebuilt executables in the zip.

    I suggest running the executable with debug like so after setting
    default to where ever you have it:

    $ mcr []syslogd -d

    This will produce a number of messages, the first of interest to me was
    "Can't open SYSLOGD_CONFIG", note not TCPIP$SYSLOGD_CONFIG as the PDF
    tells you to define. So you may need to define a logical SYSLOGD_CONFIG
    to where you have the config file (or change the source code to include
    the TCPIP$ prefix and rebuild).

    Note the example defines the logical as SYS$LOGIN:SYSLOGD_CONFIG.CFG,
    which is useless unless you are logged in as TCPIP$SYSLOG, per the PDF.

    Define it to point at the actual directory.

    This is what a proper startup looks like (apologies for line wrap):

    $ define tcpip$syslogd_config sys$sysroot:[tcpip$syslog]syslogd.cfg
    $ mcr []syslogd -d
    Binding to SYSLOG on port 514
    init
    cfline(*.err /sys$login:err.log)
    Opening Log file sys$login:err.log
    cfline(*.debug /sys$login:debug.log)
    Opening Log file sys$login:debug.log
    cfline(local0.*,user.* /sys$login:local.log)
    Opening Log file sys$login:local.log
    cfline(*.err XXXXX)
    cfline(*.* @node.domain.name)
    cfline(local1.err %CENTRAL)
    OPCOM Class CENTRAL decoded as 1
    3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 X FILE: sys$login:err.log
    7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 X FILE: sys$login:debug.log
    X 8 X X X X X X X X X X X X X X 8 X X X X X X X X FILE: sys$login:local.log
    3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 X USERS: XXXXX,
    8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 X FORW: node.domain.name
    X X X X X X X X X X X X X X X X X 3 X X X X X X X CONSOLE: 1
    logmsg: pri 56, flags 4, from node, msg syslogd: restart
    Priority skip fac:5, 3 < 6
    Logging to FILE sys$login:debug.log
    Priority skip fac:5, 16 < 6
    Priority skip fac:5, 3 < 6
    Logging to FORW node.domain.name
    Priority skip fac:5, 16 < 6
    syslogd: restarted
    Selecting 3

    Once you have that out of the way, everything seems to work. You can
    test it with the logger command as described in the PDF. Note you can
    specify priorities with the logger command, which is sadly not
    documented in the PDF, but which any man page will happily tell you about.

    $ logger -p local1.err "test central"
    $

    Message from syslogd@node at Jun 22 07:44:31 ...
    test central

    $
    %%%%%%%%%%% OPCOM 22-JUN-2024 07:44:31.11 %%%%%%%%%%%
    Message from user XXXXX on NODE
    Message from syslogd@node at Jun 22 07:44:31 ...
    test central

    HTH
    Jim
    --
    eight-cubed.com

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jim Duff@21:1/5 to Paul Coviello on Sun Jun 23 07:57:01 2024
    On 23/6/24 03:23, Paul Coviello wrote:
    Jim Duff wrote:
    [Massive snip]
    hmmm what was I expecting!  well it seemed pretty straight forward in
    the PDF that you set it up as it says and it just works, now after
    reading your comments there might be more I have to do.

    I'll try it on Monday.

    and the logger test message does work. just trying to get OPCOM to
    connect to it and hopefully your suggestions above I can figure it out

    thanks

    When you say "just trying to get OPCOM to connect to it" are you
    expecting that syslogd will somehow intercept your OPCOM messages and
    log them somewhere else? Because it doesn't do that.

    It takes syslog messages that match the priorities you have assigned to
    forward to OPCOM, in this case local1.err, and does exactly that, as I demonstrated in the example.

    Jim
    --
    eight-cubed.com

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?Arne_Vajh=C3=B8j?=@21:1/5 to Jim Duff on Sat Jun 22 18:49:24 2024
    On 6/22/2024 5:57 PM, Jim Duff wrote:
    On 23/6/24 03:23, Paul Coviello wrote:
    Jim Duff wrote:
    [Massive snip]
    hmmm what was I expecting!  well it seemed pretty straight forward in
    the PDF that you set it up as it says and it just works, now after
    reading your comments there might be more I have to do.

    I'll try it on Monday.

    and the logger test message does work. just trying to get OPCOM to
    connect to it and hopefully your suggestions above I can figure it out

    When you say "just trying to get OPCOM to connect to it" are you
    expecting that syslogd will somehow intercept your OPCOM messages and
    log them somewhere else?  Because it doesn't do that.

    It takes syslog messages that match the priorities you have assigned to forward to OPCOM, in this case local1.err, and does exactly that, as I demonstrated in the example.

    But if one want to send OPCOM messages to syslog then I assume one could:
    * enable terminal as operator terminal
    * run a little utility program that trap broadcasts
    and send them to syslog
    ?

    Arne

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jim Duff@21:1/5 to All on Sun Jun 23 14:10:07 2024
    On 23/6/24 08:49, Arne Vajhøj wrote:
    On 6/22/2024 5:57 PM, Jim Duff wrote:
    On 23/6/24 03:23, Paul Coviello wrote:
    Jim Duff wrote:
    [Massive snip]
    hmmm what was I expecting!  well it seemed pretty straight forward in
    the PDF that you set it up as it says and it just works, now after
    reading your comments there might be more I have to do.

    I'll try it on Monday.

    and the logger test message does work. just trying to get OPCOM to
    connect to it and hopefully your suggestions above I can figure it out

    When you say "just trying to get OPCOM to connect to it" are you
    expecting that syslogd will somehow intercept your OPCOM messages and
    log them somewhere else?  Because it doesn't do that.

    It takes syslog messages that match the priorities you have assigned
    to forward to OPCOM, in this case local1.err, and does exactly that,
    as I demonstrated in the example.

    But if one want to send OPCOM messages to syslog then I assume one could:
    * enable terminal as operator terminal
    * run a little utility program that trap broadcasts
      and send them to syslog
    ?

    Arne


    Sure, why not?

    https://www.eight-cubed.com/downloads.html#catch_opcom

    will trap the OPCOM messages, and it's a simple matter to open a
    datagram socket and write to the syslog port.

    Jim.
    --
    eight-cubed.com

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Simon Clubley@21:1/5 to Paul Coviello on Tue Jun 25 12:08:40 2024
    On 2024-06-24, Paul Coviello <pcoviello@gmail.com> wrote:
    Paul Coviello wrote:

    Hi Jim I just downloaded the zip file and out of curiosity do I need 'C'
    to run this?


    never mind I answered my own question... it doesn't run on itanium...

    Just curious if VSI ever got back to you...

    Simon.

    --
    Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
    Walking destinations on a map are further away than they appear.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jim Duff@21:1/5 to Paul Coviello on Wed Jun 26 04:50:46 2024
    On 24/6/24 23:56, Paul Coviello wrote:
    Paul Coviello wrote:
    Jim Duff wrote:
    On 23/6/24 08:49, Arne Vajhøj wrote:
    On 6/22/2024 5:57 PM, Jim Duff wrote:
    On 23/6/24 03:23, Paul Coviello wrote:
    Jim Duff wrote:
    [Massive snip]
    hmmm what was I expecting!  well it seemed pretty straight forward >>>>>> in the PDF that you set it up as it says and it just works, now
    after reading your comments there might be more I have to do.

    I'll try it on Monday.

    and the logger test message does work. just trying to get OPCOM to >>>>>> connect to it and hopefully your suggestions above I can figure it >>>>>> out

    When you say "just trying to get OPCOM to connect to it" are you
    expecting that syslogd will somehow intercept your OPCOM messages
    and log them somewhere else?  Because it doesn't do that.

    It takes syslog messages that match the priorities you have
    assigned to forward to OPCOM, in this case local1.err, and does
    exactly that, as I demonstrated in the example.

    But if one want to send OPCOM messages to syslog then I assume one
    could:
    * enable terminal as operator terminal
    * run a little utility program that trap broadcasts
       and send them to syslog
    ?

    Arne


    Sure, why not?

    https://www.eight-cubed.com/downloads.html#catch_opcom

    will trap the OPCOM messages, and it's a simple matter to open a
    datagram socket and write to the syslog port.

    Jim.

    Hi Jim I just downloaded the zip file and out of curiosity do I need
    'C' to run this?


    never mind I answered my own question...  it doesn't run on itanium...

    You need the C compiler to compile it, yes. And no idea what "it
    doesn't run on Itanium" means. I originally wrote it on Alpha, and it's
    been run in production on Alpha and IA64, and tested on x86.

    Jim
    --
    eight-cubed.com

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Simon Clubley@21:1/5 to Paul Coviello on Wed Jun 26 12:06:43 2024
    On 2024-06-25, Paul Coviello <pcoviello@gmail.com> wrote:
    Simon Clubley wrote:
    On 2024-06-24, Paul Coviello <pcoviello@gmail.com> wrote:
    Paul Coviello wrote:

    Hi Jim I just downloaded the zip file and out of curiosity do I need 'C' >>>> to run this?


    never mind I answered my own question... it doesn't run on itanium...

    Just curious if VSI ever got back to you...


    nope... :-(

    Sounds about right, unfortunately.

    Simon.

    --
    Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
    Walking destinations on a map are further away than they appear.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Robert A. Brooks@21:1/5 to Paul Coviello on Wed Jun 26 11:43:03 2024
    On 6/25/2024 9:09 AM, Paul Coviello wrote:
    Simon Clubley wrote:
    On 2024-06-24, Paul Coviello <pcoviello@gmail.com> wrote:
    Paul Coviello wrote:

    Hi Jim I just downloaded the zip file and out of curiosity do I need 'C' >>>> to run this?


    never mind I answered my own question...  it doesn't run on itanium...

    Just curious if VSI ever got back to you...

    Simon.



    nope... :-(

    Who of my colleagues have you been emailing with?

    Do you have a tracking number for this problem?

    --
    -- Rob

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?Arne_Vajh=C3=B8j?=@21:1/5 to Jim Duff on Wed Jun 26 13:26:46 2024
    On 6/23/2024 12:10 AM, Jim Duff wrote:
    On 23/6/24 08:49, Arne Vajhøj wrote:
    On 6/22/2024 5:57 PM, Jim Duff wrote:
    On 23/6/24 03:23, Paul Coviello wrote:
    Jim Duff wrote:
    [Massive snip]
    hmmm what was I expecting!  well it seemed pretty straight forward
    in the PDF that you set it up as it says and it just works, now
    after reading your comments there might be more I have to do.

    I'll try it on Monday.

    and the logger test message does work. just trying to get OPCOM to
    connect to it and hopefully your suggestions above I can figure it out

    When you say "just trying to get OPCOM to connect to it" are you
    expecting that syslogd will somehow intercept your OPCOM messages and
    log them somewhere else?  Because it doesn't do that.

    It takes syslog messages that match the priorities you have assigned
    to forward to OPCOM, in this case local1.err, and does exactly that,
    as I demonstrated in the example.

    But if one want to send OPCOM messages to syslog then I assume one could:
    * enable terminal as operator terminal
    * run a little utility program that trap broadcasts
       and send them to syslog
    ?

    Sure, why not?

    https://www.eight-cubed.com/downloads.html#catch_opcom

    will trap the OPCOM messages, and it's a simple matter to open a
    datagram socket and write to the syslog port.

    So to summarize and make sure that everybody sees the
    same picture.

    Normal flow:

    application--->syslogd--->file

    Builtin extra capability:

    |->OPCOM
    application--->syslogd-|
    |->file

    Not builtin extra capability:

    custom program<---OPCOM
    |
    v
    application--->syslogd--->file

    And it could be very unwise to combine:

    custom program<----|
    | |
    v |->OPCOM-|
    application--->syslogd-|
    |->file

    Arne

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Robert A. Brooks@21:1/5 to Paul Coviello on Wed Jun 26 23:15:27 2024
    On 6/26/2024 9:54 PM, Paul Coviello wrote:

    after a poke they did get back to me it was Jan and Sophia. no one in
    support can help and it would be an SOW with an engineer. Who I
    still don't know if they can help. waiting to hear back

    If you are offered a statement of work, that tends to imply that
    the help you are asking for is over and above what is provided
    by your support contract.

    As an engineer, I don't get involved in those decisions; I just
    fix stuff.

    --
    -- Rob

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?Arne_Vajh=C3=B8j?=@21:1/5 to Paul Coviello on Thu Jun 27 19:46:41 2024
    On 6/27/2024 9:40 AM, Paul Coviello wrote:
    Robert A. Brooks wrote:
    On 6/26/2024 9:54 PM, Paul Coviello wrote:
    after a poke they did get back to me it was Jan and Sophia. no one in
    support can help and it would be an SOW with an engineer.  Who I
    still don't know if they can help.  waiting to hear back

    If you are offered a statement of work, that tends to imply that
    the help you are asking for is over and above what is provided
    by your support contract.

    As an engineer, I don't get involved in those decisions; I just
    fix stuff.

    I suppose it is since it's freeware from their website, though to be
    honest I would have thought some form of helping set it up with more documentation would have been nice too.

    If I understand correctly then this software is:
    * a port of the Unix code done by John Vottoro in 1995 on VMS 6.x
    * HP put it on the Freeware CD in 2006
    * an employee of VSI put up a PDF in 2018 with instructions on
    how to get it running on VMS 8.4

    I would have been very surprised if VSI considered it covered
    by any support contract for any customer. A SOW and a price tag
    seems quite natural to me.

    Those that do not want to pay for it can change the code and/or
    write whatever documentation they need themselves - it is open
    source under a BSD license, which is a very permissive license.

    Arne

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lawrence D'Oliveiro@21:1/5 to Paul Coviello on Fri Jun 28 00:23:35 2024
    On Thu, 27 Jun 2024 09:40:12 -0400, Paul Coviello wrote:

    I suppose it is since it's freeware from their website ...

    Is it freeware <https://en.wikipedia.org/wiki/Freeware> or Free software <https://en.wikipedia.org/wiki/Free_software>?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?Arne_Vajh=C3=B8j?=@21:1/5 to Lawrence D'Oliveiro on Thu Jun 27 20:39:58 2024
    On 6/27/2024 8:23 PM, Lawrence D'Oliveiro wrote:
    On Thu, 27 Jun 2024 09:40:12 -0400, Paul Coviello wrote:
    I suppose it is since it's freeware from their website ...

    Is it freeware <https://en.wikipedia.org/wiki/Freeware> or Free software <https://en.wikipedia.org/wiki/Free_software>?

    In the broad definition of "freeware" (just meaning gratis as opposed
    to a more narrow definition of gratis but not open source): both.

    BSD license.

    Arne

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lawrence D'Oliveiro@21:1/5 to All on Fri Jun 28 01:40:57 2024
    On Thu, 27 Jun 2024 20:39:58 -0400, Arne Vajhøj wrote:

    On 6/27/2024 8:23 PM, Lawrence D'Oliveiro wrote:

    On Thu, 27 Jun 2024 09:40:12 -0400, Paul Coviello wrote:

    I suppose it is since it's freeware from their website ...

    Is it freeware <https://en.wikipedia.org/wiki/Freeware> or Free
    software <https://en.wikipedia.org/wiki/Free_software>?

    In the broad definition of "freeware" (just meaning gratis as opposed to
    a more narrow definition of gratis but not open source): both.

    The two are disjoint.

    BSD license.

    Free software.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)