Public bug reported:
Binary package hint: cupsys
Cups daemon went mad and started writing 0x00 to its access_log until
disk got full. It stopped it after restarting the daemon. Will see if it
does it again.
I wonder whether the log file sizes should be limited so this kind of
things don't get happen accidentally by mad daemons? :)
Oh, the distro is Edgy with latest updates applied.
** Affects: cupsys (Ubuntu)
Importance: Undecided
Status: Unconfirmed
** Description changed:
Binary package hint: cupsys
Cups daemon went mad and started writing 0x00 to its access_log until
- disk got full. It stopped it after restrting the daemon. Will see if it
- does it again. I wonder whether the log file sizes should be limited so
- this kind of things don't get happen accidentally by mad daemons? :)
+ disk got full. It stopped it after restarting the daemon. Will see if it
+ does it again.
+
+ I wonder whether the log file sizes should be limited so this kind of
+ things don't get happen accidentally by mad daemons? :)
** Description changed:
Binary package hint: cupsys
Cups daemon went mad and started writing 0x00 to its access_log until
disk got full. It stopped it after restarting the daemon. Will see if it
does it again.
I wonder whether the log file sizes should be limited so this kind of
things don't get happen accidentally by mad daemons? :)
+
+ Oh, the distro is Edgy with latest updates applied.
--
cups daemon writes 0x00 to access_log forever
https://launchpad.net/bugs/79518
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
