Public bug reported:
In /etc/logrotate/proftpd-basic, the postrotate sections we find this:
invoke-rc.d proftpd restart 2>/dev/null >/dev/null || true
This command fails to properly restart the service.
Updating /etc/init.d/proftpd fixes the problem:
--- /etc/init.d/proftpd~2013-12-20
Has this fix been back-ported to Hardy? I'm looking at a massive upgrade
Hardy-Lucid now, and need to use a local mirror.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to adept in Ubuntu.
https://bugs.launchpad.net/bugs/147080
Title:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/848111
Title:
Configuration problem, razor is unable to log
To manage notifications about this bug go to:
Public bug reported:
When used with amavisd-new, razor runs as amavis:amavis, and has no
write permisison for the configured log file /var/log/razor-agent.log.
Thus it logs nothing.
Not sure if this should be logged as a bug with amavisd-new or razor.
ProblemType: Bug
DistroRelease: Ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/848119
Title:
Not usable on a server in DMZ
To manage notifications about this bug go to:
Public bug reported:
ubuntu-bug seemes to require both a web browser and outgoing connections
on tcp port 80. With an Ubuntu server in a locked-down DMZ, neither are
lightly to be available, so reporting bugs on such systems becomes
cumbersome.
In our case, an option to report using SMTP would
reassess it.
I think you can safely close it.
Thanks for your comments and I hope the options I presented help make
things better for you!
Thank you for your quick response, and your help :-)
-- Geir Helland
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Quick fix.
Log in, then run:
sudo dmesg -n 1
This will prevents all messages, expect panic messages, from appearing
on the console.
Alternatively (not tested), try adding -c 1 to the KLOGD= assignment
in /etc/init.d/klogd, then restart it.
--
PS3: Kernel floods log and console with
