[Bug 1516451] Re: check_disk plugin broken after upgrade to 15.10

2015-11-24 Thread Ben Coleman
Also note that while 15.10 does change the permissions on /sys/kernel/debug/tracing (from drwxr-xr-x in 15.04 to drwx-- in 15.10), the permissions on /sys/kernel/debug are drwx-- on both 15.10 and 15.04 - which means that /sys/kernel/debug shouldn't be readable from a non-root account on

[Bug 1194960] Re: unmatched entries for dovecot sieve deliveries when mailbox name contains whitespace

2015-07-28 Thread Ben Coleman
Just checked this on 14.04 and 15.10, and this fix is present. I presume it was added upstream? ** Changed in: logwatch (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in

[Bug 1418636] Re: /usr/share/man/man1/gem.1.gz is a dangling symlink

2015-02-25 Thread Ben Coleman
In utopic, /usr/share/man/man1/gem.1.gz points to gem2.1.1.gz, and comes from the ruby package. Note that in trusty, /usr/share/man/man1/gem.1.gz pointed to gem1.9.1.1.gz (also from the ruby package), and gem1.9.1.1.gz comes from the ruby1.9.1 package. Looks like gem2.1.1.gz was left out of the

[Bug 1194960] [NEW] unmatched entries for dovecot sieve deliveries when mailbox name contains whitespace

2013-06-26 Thread Ben Coleman
Public bug reported: On Ubuntu 13.04, using the stock dovecot and logwatch, I get unmatched entries for dovecot when sieve delivers into a mailbox that has whitespace in its name. The line which detects sieve deliveries (line 157) assumes that the mailbox name will not have whitespace: }

[Bug 1061154] [NEW] pgsql.cfg includes a check_pgsql_4 command, but check_pgsql does not actually take the -4 argument

2012-10-03 Thread Ben Coleman
Public bug reported: The /etc/nagios-plugins/config/pgsql.cfg configuration file includes a check_pgsql_4 command, which should force the connection to use IPv4. However, the program called, /usr/lib/nagios/plugins/check_pgsql, does not actually accept the -4 parameter. I'd rather see this

[Bug 807153] Re: DNSSEC-enabled named sometimes does not die on service bind9 stop

2012-05-02 Thread Ben Coleman
The problem with the init script in the debian bug was that bind9 itself wasn't dying, and the init script was set up to wait until bind9 died. It was made moot by by upstream release of bind 9.8.1, which fixed the problem of bind9 not dying. -- You received this bug notification because you are

[Bug 807153] Re: DNSSEC-enabled named sometimes does not die on service bind9 stop

2012-05-01 Thread Ben Coleman
I'm also seeing this problem on 2 of the machines under my control. Two others running bind9 do notpo have this problem. The two that have this problem do have DNSSEC enabled (though only one of them is actually serving a DNSSEC-using zone). This seems to be related to Debian bug #570852