OpenPKG CVS Repository
  http://cvs.openpkg.org/
  ____________________________________________________________________________

  Server: cvs.openpkg.org                  Name:   Thomas Lotterer
  Root:   /v/openpkg/cvs                   Email:  [EMAIL PROTECTED]
  Module: openpkg-src                      Date:   16-Mar-2005 17:34:56
  Branch: HEAD                             Handle: 2005031616345600

  Modified files:
    openpkg-src/ngircd      ngircd.patch

  Log:
    fix wrong programming language ;-) and copy'n'paste bug

  Summary:
    Revision    Changes     Path
    1.2         +2  -2      openpkg-src/ngircd/ngircd.patch
  ____________________________________________________________________________

  patch -p0 <<'@@ .'
  Index: openpkg-src/ngircd/ngircd.patch
  ============================================================================
  $ cvs diff -u -r1.1 -r1.2 ngircd.patch
  --- openpkg-src/ngircd/ngircd.patch   16 Mar 2005 13:44:52 -0000      1.1
  +++ openpkg-src/ngircd/ngircd.patch   16 Mar 2005 16:34:56 -0000      1.2
  @@ -6,7 +6,7 @@
        NGIRCd_Sniffer = FALSE;
    #endif
   +#ifdef PID_FILE
  -+    NGIRCd_PidFile[0] = '/dev/null';
  ++    strlcpy( NGIRCd_PidFile, "/dev/null", sizeof( NGIRCd_PidFile ));
   +#endif
        strlcpy( NGIRCd_ConfFile, SYSCONFDIR, sizeof( NGIRCd_ConfFile ));
        strlcat( NGIRCd_ConfFile, CONFIG_FILE, sizeof( NGIRCd_ConfFile ));
  @@ -44,7 +44,7 @@
   +              old_umask = umask((mode_t) 0022);
   +              pid = getpid();
   +              if ((fp = fopen(NGIRCd_PidFile, "w")) == NULL)
  -+               syslog(LOG_ERR, "cannot write PID file '%s'", PID_FILE);
  ++               syslog(LOG_ERR, "cannot write PID file '%s'", 
NGIRCd_PidFile);
   +              fprintf(fp, "%ld\n", (long)pid);
   +              fclose(fp);
   +              umask(old_umask);
  @@ .
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
CVS Repository Commit List                     [email protected]

Reply via email to