Package: leafnode
Version: 1.11.3.rel-4
Severity: normal

I was running leafnode on a system with sporadic ppp connections.
After getting a permanent connection, I ran dpkg-reconfigure to tell
it I had one.  Things didn't work after that, and the log show lots of
entries like

Sep  5 20:41:27 localhost leafnode[17504]: cannot open /etc/news/leafnode/config
Sep  5 20:41:27 localhost leafnode[17504]: 503 Unable to read configuration 
file, exiting; the server's syslog should have more information.

All the files in /etc/news/leafnode/ had user and group of root.

It is possible this is an artifact of my editing the config file while
logged in as root (using RCS to control it).  However, all the files
in the directory had root:root for owner:group.

I did a manual chgrp to news for those same files, and things seemed
to work after that.

So I may have caused the problem, but I thought I'd report it in case
not.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (990, 'stable'), (50, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27advncdfs
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages leafnode depends on:
ii  debconf [debconf-2.0]         1.4.57     Debian configuration management sy
ii  libc6                         2.3.5-6    GNU C Library: Shared libraries an
ii  libpcre3                      5.0-1.1    Perl 5 Compatible Regular Expressi
ii  logrotate                     3.7.1-1    Log rotation utility
ii  netbase                       4.21       Basic TCP/IP networking system
ii  tcpd                          7.6.dbs-8  Wietse Venema's TCP wrapper utilit

leafnode recommends no packages.

-- debconf information:
* leafnode/update-groups: false
  leafnode/update-groupinfo:
* leafnode/tcpd: true
  leafnode/update-maxcount:
  leafnode/ppp:
* leafnode/network: permanent
  leafnode/expireinfo:
  leafnode/purge: false
* leafnode/server: nntp2.rawbw.com


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to