Package: man2html Version: 1.6-2 Severity: normal I woke up to a machine with a load of 11 this morning, because index++ from the weekly man2html cronjob was eating ~120 MB of VM, and had swapped in about 60MB.
Sure, it's a small(ish) machine, but it seems odd that we would need so much RAM just to turn man pages into html. Is a perl job trying to slurp in the entire manpage database instead of looping over it efficiently, or anything like that? -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12.3 Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Versions of packages man2html depends on: ii debconf [debconf-2.0] 1.4.58 Debian configuration management sy ii debianutils 2.14.3 Miscellaneous utilities specific t ii gawk 1:3.1.4-2.0.1 GNU awk, a pattern scanning and pr ii libc6 2.3.5-6 GNU C Library: Shared libraries an ii man-db 2.4.3-2 The on-line manual pager Versions of packages man2html recommends: ii apache [httpd-cgi] 1.3.33-7 versatile, high-performance HTTP s ii lynx 2.8.5-2 Text-mode WWW Browser -- debconf information: man2html/index_manpages: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
