Subject: new syslogd

From: Dale Scheetz <[email-masked]>
Date: Thu, 6 Jun 1996 15:03:57 -0400 (EDT)

When I installed the new 1.3-6 syslogd I got the following during
installation:

starting /sbin/syslogd ...
  syslogd: network logging disabled (syslog/udp service unknown).
  syslogd: see syslog(8) for details of whether and how to enable it.:
Operation not permitted
starting /sbin/klogd ...
klogd: already running.

It's not clear what Operation is not permitted, but something in the
post-inst script probably failed.

I also noticed that this package provides, replaces, and conflicts with
syslogd. Is this right? I suspect that the conflicts may be what is
causing the recent user posting about dselect being unwilling to remove
the old package?

In any case it doesn't seem to be a robust installation yet.

Later,

Dwarf

------------                                          --------------

aka   Dale Scheetz                   Phone:   1 (904) 877-0257
      Flexible Software              Fax:     NONE 
      Black Creek Critters           e-mail:  [email-masked]

------------ If you don't see what you want, just ask --------------

---

From: [email-masked] (Martin Schulze)
Date: Fri, 7 Jun 96 10:36 MET DST

You write:

}When I installed the new 1.3-6 syslogd I got the following during
                                   ^
				   k
}installation:

}starting /sbin/syslogd ...
}  syslogd: network logging disabled (syslog/udp service unknown).
}  syslogd: see syslog(8) for details of whether and how to enable it.:
}Operation not permitted

This should not happen.

}starting /sbin/klogd ...
}klogd: already running.

}It's not clear what Operation is not permitted, but something in the
}post-inst script probably failed.

I seem to remember that the operation that isn't permitted is binding
a port or similar, I'm not sure at the moment.

Dwarf, just enable the entry syslog/udp in the /etc/services file and
the message vanishes.  According to the documentation which represents
the code, this is not a risk as you still have control over receiption
of syslog messages from the I-Net, you have to add `-r' to the
argument list if you want to, otherwise the port isn't opened ofr
reading.

}I also noticed that this package provides, replaces, and conflicts with
}syslogd. Is this right? I suspect that the conflicts may be what is
}causing the recent user posting about dselect being unwilling to remove
}the old package?

According to Ian J. this is correct.

}In any case it doesn't seem to be a robust installation yet.

Thanks.

Joey
-- 
  / Martin Schulze  *  [email-masked]  *  26129 Oldenburg /
 /              Whenever you meet yourself you're in a time loop /
/ http://home.pages.de/~joey/           or in front of a mirror /

---

From: Dale Scheetz <[email-masked]>
Date: Fri, 7 Jun 1996 09:01:05 -0400 (EDT)

> }When I installed the new 1.3-6 syslogd I got the following during

Yeah, this is still very confusing...

After the above installation I did:

dpkg -s syslogd

and got:

Package: syslogd
Essential: yes
Status: install ok config-files
Priority: required
Section: base
Maintainer: Martin Schulze <[email-masked]>
Version: 1.3-2
Config-Version: 1.3-2
Pre-Depends: libc5 (>=5.2.18-1)
Conffiles:
 /etc/syslog.conf 2d11be2cc2ec4ad74e651a6a946228ea
 /etc/init.d/sysklogd adbb56dff4c7ab89ab959a2677bca78b
Description: Kernel and system logging daemons.
 This package implements two system log daemons. The syslogd daemon is
 an enhanced version of the standard Berkeley utility program. This
 daemon is responsible for providing logging of messages received from
 programs and facilities on the local host as well as from remote
 hosts.
 .
 The klogd daemon listens to kernel message sources and is responsible
 for prioritizing and processing operating system messages. The klogd
 daemon can run as a client of syslogd or optionally as a standalone
 program. Klogd can now be used to decode EIP addresses if it can
 determine a System.map file.

and when I do:

dpkg -s sysklogd

I get:

Package: sysklogd
Essential: yes
Status: install ok installed
Priority: required
Section: base
Maintainer: Martin Schulze <[email-masked]>
Version: 1.3-6
Replaces: syslogd
Provides: syslogd
Pre-Depends: libc5 (>=5.2.18-1)
Conflicts: syslogd
Conffiles:
 /etc/syslog.conf 1158ff9e7d55009929f1b4f1673d0348
 /etc/init.d/sysklogd f03ee6e2e4261b2c43f3a9b60aeb1d50
 /etc/cron.weekly/sysklogd 6492db834c0c9b29c38b81dbbf803c77
Description: Kernel and system logging daemons.
 This package implements two system log daemons. The syslogd daemon is
 an enhanced version of the standard Berkeley utility program. This
 daemon is responsible for providing logging of messages received from
 programs and facilities on the local host as well as from remote
 hosts.
 .
 The klogd daemon listens to kernel message sources and is responsible
 for prioritizing and processing operating system messages. The klogd
 daemon can run as a client of syslogd or optionally as a standalone
 program. Klogd can now be used to decode EIP addresses if it can
 determine a System.map file.

It seems, from the above, that dpkg thinks that the conf-files for syslogd
are still installed?

BTW, this new version does log to the correct files, so we are making
headway :-)

TIA,

Dwarf

------------ If you don't see what you want, just ask --------------

---

From: Guy Maor <[email-masked]>
Date: Fri, 7 Jun 1996 08:08:32 -0500 (CDT)

> It seems, from the above, that dpkg thinks that the conf-files for syslogd

That was bug 3214, which dpkg 1.2.4 will fix.

Guy

---

From: [email-masked]
Date: Fri, 7 Jun 96 09:23 EDT

Dale> Package: syslogd 
  Dale> Status: install ok config-files
  Dale> 
  Dale> Package: sysklogd 
  Dale> Status: install ok installed
  Dale> 
  Dale>  It seems, from the above, that dpkg thinks that the conf-files for
  Dale> syslogd are still installed?

  Guy>  That was bug 3214, which dpkg 1.2.4 will fix.

Not so.

Bug 3214, which I reported, did not leave the replaced package in status
"installed". It only left the conffiles associated with the package.  That
got fixed by Ian.

What we have here is the rather odd situation of two conflicting packages
installed side by side.

--
Dirk Eddelb"uttel                             http://qed.econ.queensu.ca/~edd

---

From: Ian Jackson <[email-masked]>
Date: Mon, 10 Jun 96 02:23 BST

Dale Scheetz writes ("Re: new syslogd"):
...
> Status: install ok config-files
...
> It seems, from the above, that dpkg thinks that the conf-files for syslogd

Yes, and the problem with this is ... ?

Ian.

---

From: Ian Jackson <[email-masked]>
Date: Mon, 10 Jun 96 02:23 BST

Dirk Eddelbuettel writes ("Re: new syslogd"):
...
> What we have here is the rather odd situation of two conflicting packages

No, what we have is one package which has been removed, with only old
configuration remaining, and one package which has been installed.

Ian.

---

From: Dale Scheetz <[email-masked]>
Date: Mon, 10 Jun 1996 08:05:40 -0400 (EDT)

> Yes, and the problem with this is ... ?
Well, sysklogd conflicts with syslogd. I assume this means that it
conflicts with it's conffiles too? The thought was that this could be why
dselect has problems with syslogd and sysklogd.

Later,

Dwarf

------------ If you don't see what you want, just ask --------------

---

From: Ian Jackson <[email-masked]>
Date: Sun, 16 Jun 96 23:11 BST

> conflicts with it's conffiles too?

No.

>  The thought was that this could be why

Could you please elaborate on these problems ?

Ian.