Russ Allbery <[EMAIL PROTECTED]> writes: > I'll take a look and see about getting the packages uploaded tomorrow.
shishid appears to be broken, at least on my system, and I'm not sure how to fix it. In the current package, the init script starts the daemon in the foreground and it just hangs until one types Ctrl-D. It then dies and the boot process continues. Using --background fixes this, but shishid just starts and immediately exits. It spits out the following in syslog: Apr 20 19:09:08 wanderer /usr/sbin/shishid: Starting (GNUTLS `1.2.9') Apr 20 19:09:08 wanderer /usr/sbin/shishid: Listening on IPv6:*:kerberos/udp socket 0 Apr 20 19:09:08 wanderer /usr/sbin/shishid: Listening on IPv4:*:kerberos/tcp socket 4 Apr 20 19:09:08 wanderer /usr/sbin/shishid: Listening on IPv4:*:kerberos/udp socket 5 Apr 20 19:09:08 wanderer /usr/sbin/shishid: Error reading from IPv6:*:kerberos/udp on socket 0 (-1): Unknown error 4294967295 Apr 20 19:09:08 wanderer /usr/sbin/shishid: Closing IPv6:*:kerberos/udp socket 0 before it disappears. Also, if shishid isn't running, the init script stop action fails, which then causes all sorts of strange problems for the upgrade process. In fact, if the old shishid package is installed, it appears to be impossible to upgrade the system; the package is so broken that there doesn't appear to be any way to get rid of it without manually removing the init script and then using dpkg --purge --force-remove-reinstreq. I think some of this may be due to a debhelper bug; I'm investigating. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> _______________________________________________ Help-shishi mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-shishi
