[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Uploaded rlinetd 0.5.4 (sparc) to ftp-master



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Mon, 20 Aug 2001 00:07:13 +0200
Source: rlinetd
Binary: rlinetd
Architecture: sparc
Version: 0.5.4
Distribution: unstable
Urgency: low
Maintainer: Debian/sparc Build Daemon <buildd@sparc.debian.org>
Changed-By: Robert Luberda <robert@debian.org>
Description: 
 rlinetd    - gruesomely over-featured inetd replacement
Closes: 91319 102721 105854
Changes: 
 rlinetd (0.5.4) unstable; urgency=low
 .
   * In `user' directive call setgid() before setuid() (closes: #105854).
   * Log file name and line number on parse warnings (closes: #91319).
   * Call exit() instead of abort() on fatal errors (closes: #102721).
   * Do not close no opened socket (fixes rlinetd part of #103299).
   * Rewrite inetd2rlinetd, now it outputs each service in separater file in
     /etc/rlinetd.d directory
 .
   * Remove files from /etc/rlinetd.d directory when package is purged.
   * Update copyright file.
   * Include both (upstream & Debian) changelogs in the package.
   * /etc/rlinetd.conf: skip editor backup files in dircetory /etc/rlinetd.d.
 .
   * Added a very simple update-inetd script, which can only add a service.
   * We diverts /etc/init.d/inetd file to make sure that inetd is not started.
   * If no service is defined in /etc/rlinetd*, ask user via debconf if we
     should import settings from /etc/inetd.conf.
 .
   * rlinetd conflicts with xinetd and with old netbase package.
   * Added dependency on debconf and dpkg (both versioned).
   * We recommends sysklogd|system-log-daemon and suggests portmap.
Files: 
 44cef2dc39c15178d7e0ae54f35bca2b 68292 net extra rlinetd_0.5.4_sparc.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.6 and Gnu Privacy Guard <http://www.gnupg.org/>

iEYEARECAAYFAjuCVVMACgkQgD/uEicUG7DaXQCaA/+TDfDMDb767caMfmpkMLvN
PWoAoKBHPECe3aNL0OV1SPLCSYfo8NxL
=VdHn
-----END PGP SIGNATURE-----



Reply to: