Uploaded image for project: 'OpenDNSSEC'
  1. OpenDNSSEC
  2. OPENDNSSEC-240

signer on netbsd loses syslog after a thread is created

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.3.7
    • Fix Version/s: 1.3.8
    • Component/s: Signer
    • Labels:
      None
    • Environment:

      NetBSD 5.1

      Description

      I noticed that there is no syslog messages from the threads created on NetBSD 5.1, I have a test that starts 32 threads and check that there started and all it got in the syslog was:

      Apr 4 15:36:36 netbsd64-ods09 ods-signerd: [engine] running as pid 10479
      Apr 4 15:36:36 netbsd64-ods09 ods-signerd: [hsm] libhsm connection opened succesfully
      Apr 4 15:36:36 netbsd64-ods09 ods-signerd: [zonelist] read file /home/jerry/workspace/root/1.3/etc/opendnssec/zonelist.xml
      Apr 4 15:36:36 netbsd64-ods09 ods-signerd: [engine] signer started
      Apr 4 15:36:37 netbsd64-ods09 ods-signerd: [cmdhandler] received command running[7]
      Apr 4 15:36:38 netbsd64-ods09 ods-signerd: [cmdhandler] received command stop[4]
      Apr 4 15:36:38 netbsd64-ods09 ods-signerd: [engine] signer shutdown
      Apr 4 15:36:38 netbsd64-ods09 ods-signerd: [log] switching log to stderr verbosity 0 (log level 2)

      It should have a lot more, create worker[], [worker[]] reporting for duty etc...

        Attachments

          Activity

            People

            Assignee:
            jerry Jerry Lundström
            Reporter:
            jerry Jerry Lundström
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: