Bug#655051: inn doesn't start

2012-01-08 Thread KNL
On Sun, 8 Jan 2012 18:13:59 +0100 m...@linux.it (Marco d'Itri) wrote: > On Jan 08, KNL wrote: > > > A /etc/init.d/inn start doesn't report any errors and no errors is > > repported in /var/log/news. > This is hard to believe. > Please look harder. This is ab

Bug#655052: dpkg: error processing inn2

2012-01-07 Thread KNL
Package: inn2 Version: 2.5.2-2~squeeze1 Severity: important Tags: upstream When installing inn2 dpkg fails with the following: Setting up inn2 (2.5.2-2~squeeze1) ... innconfval: open of /etc/news/inn.conf failed: No such file or directory dpkg: error processing inn2 (--configure): subprocess in

Bug#655051: inn doesn't start

2012-01-07 Thread KNL
Package: inn Version: 1:1.7.2q-39+squeeze1 Severity: grave Tags: upstream Justification: renders package unusable After installation inn doesn't start and a "ps aux" shows that inn isn't running. A /etc/init.d/inn start doesn't report any errors and no errors is repported in /var/log/news. It

Bug#607340: Bug exists in squeeze, but it's not related to sites-enabled

2011-03-18 Thread knl
The bug exists in Squeeze, but the symlink is not related to /etc/apache2/sites-enabled. Upon installation the configuration should create a symlink from /etc/squirrelmail/apache.conf to /etc/apache2/conf.d/squirrelmail.conf - this is what is missing. Until the bug is fixed just use this command

Bug#505133: Patch for mc to specify port in shell link

2008-11-09 Thread knl
This patch fixes the bug. Apply this patch to fish.c I have tested it, and it works. After the patch it is possible to specify the port number in a shell link like this: /#sh:[EMAIL PROTECTED]:3000/home/foo/ --- Mange venlige hilsner/Best regards Kim Lesmer Programmer/Unix systemadministrator

Bug#505133: mc: Impossible to specify port number in shell link (patched succesfully)

2008-11-09 Thread knl
On Sun, 9 Nov 2008 23:21:10 +0100 Michelle Konzack <[EMAIL PROTECTED]> wrote: > Am 2008-11-09 19:53:00, schrieb Kim N. Lesmer: > > When using the shell link, it should be possible to specify the > > port number like this: > > > > [EMAIL PROTECTED]:3000/home/username/ > > This can not work since

Bug#505133: mc: Impossible to specify port number in shell link

2008-11-09 Thread knl
On Sun, 9 Nov 2008 23:21:10 +0100 Michelle Konzack <[EMAIL PROTECTED]> wrote: > Am 2008-11-09 19:53:00, schrieb Kim N. Lesmer: > > When using the shell link, it should be possible to specify the > > port number like this: > > > > [EMAIL PROTECTED]:3000/home/username/ > > This can not work since