Bug#609294: /etc/init.d/polipo status doesn't work
Package: polipo
Version: 1.0.4-1+lenny1
Severity: minor
/etc/init.d/polipo status
returns:
Usage: /etc/init.d/polipo {start|stop|restart|force-reload}
Status is a standard operand for init scripts.
Without it, one cannot easily determine whether the polipo daemon is running
normally.
-- System Information:
Debian Release: 5.0.1
APT prefers proposed-updates
APT policy: (500, 'proposed-updates'), (500, 'unstable'), (500, 'testing'),
(500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-686-bigmem (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages polipo depends on:
ii libc6 2.9-6 GNU C Library: Shared libraries
polipo recommends no packages.
polipo suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#549492: [php-maint] Bug#549492: Bug#549492: Bug#549492: Bug#549492: segmentation faults in version 5.3.1-4
any ideas here? php-cgi continues to segfault. until this problem, this has been a more or less rock solid server. now it's not. :-/ On Sat, Feb 27, 2010 at 2:23 PM, Count László de Almásy calm...@gmail.com wrote: here's a new backtrace (after installing php5-dbg) Program received signal SIGSEGV, Segmentation fault. zend_hash_destroy (ht=0x1000701) at /build/buildd-php5_5.3.1-5-amd64-M9dAcL/php5-5.3.1/Zend/zend_hash.c:712 712 /build/buildd-php5_5.3.1-5-amd64-M9dAcL/php5-5.3.1/Zend/zend_hash.c: No such file or directory. in /build/buildd-php5_5.3.1-5-amd64-M9dAcL/php5-5.3.1/Zend/zend_hash.c (gdb) bt #0 zend_hash_destroy (ht=0x1000701) at /build/buildd-php5_5.3.1-5-amd64-M9dAcL/php5-5.3.1/Zend/zend_hash.c:712 #1 0x00719575 in fcgi_finish_request (req=0x7fffca8122e0, force_close=0) at /build/buildd-php5_5.3.1-5-amd64-M9dAcL/php5-5.3.1/sapi/cgi/fastcgi.c:871 #2 0x00715886 in sapi_cgi_deactivate () at /build/buildd-php5_5.3.1-5-amd64-M9dAcL/php5-5.3.1/sapi/cgi/cgi_main.c:864 #3 0x00643a22 in sapi_deactivate () at /build/buildd-php5_5.3.1-5-amd64-M9dAcL/php5-5.3.1/main/SAPI.c:444 #4 0x00639485 in php_request_shutdown (dummy=0x1000701) at /build/buildd-php5_5.3.1-5-amd64-M9dAcL/php5-5.3.1/main/main.c:1627 #5 0x007172a3 in main (argc=32767, argv=0x0) at /build/buildd-php5_5.3.1-5-amd64-M9dAcL/php5-5.3.1/sapi/cgi/cgi_main.c:2155 -- Cheers, László -- Cheers, László -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#549492: [php-maint] Bug#549492: Bug#549492: Bug#549492: Bug#549492: segmentation faults in version 5.3.1-4
here's a new backtrace (after installing php5-dbg) Program received signal SIGSEGV, Segmentation fault. zend_hash_destroy (ht=0x1000701) at /build/buildd-php5_5.3.1-5-amd64-M9dAcL/php5-5.3.1/Zend/zend_hash.c:712 712 /build/buildd-php5_5.3.1-5-amd64-M9dAcL/php5-5.3.1/Zend/zend_hash.c: No such file or directory. in /build/buildd-php5_5.3.1-5-amd64-M9dAcL/php5-5.3.1/Zend/zend_hash.c (gdb) bt #0 zend_hash_destroy (ht=0x1000701) at /build/buildd-php5_5.3.1-5-amd64-M9dAcL/php5-5.3.1/Zend/zend_hash.c:712 #1 0x00719575 in fcgi_finish_request (req=0x7fffca8122e0, force_close=0) at /build/buildd-php5_5.3.1-5-amd64-M9dAcL/php5-5.3.1/sapi/cgi/fastcgi.c:871 #2 0x00715886 in sapi_cgi_deactivate () at /build/buildd-php5_5.3.1-5-amd64-M9dAcL/php5-5.3.1/sapi/cgi/cgi_main.c:864 #3 0x00643a22 in sapi_deactivate () at /build/buildd-php5_5.3.1-5-amd64-M9dAcL/php5-5.3.1/main/SAPI.c:444 #4 0x00639485 in php_request_shutdown (dummy=0x1000701) at /build/buildd-php5_5.3.1-5-amd64-M9dAcL/php5-5.3.1/main/main.c:1627 #5 0x007172a3 in main (argc=32767, argv=0x0) at /build/buildd-php5_5.3.1-5-amd64-M9dAcL/php5-5.3.1/sapi/cgi/cgi_main.c:2155 -- Cheers, László -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#549492: [php-maint] Bug#549492: Bug#549492: Bug#549492: segmentation faults in version 5.3.1-4
On Wed, Feb 24, 2010 at 3:56 PM, Ondřej Surý ond...@debian.org wrote: We still need the backtrace. Without a backtrace your report is almost useless. i just can't figure out how to do that. i've spent a considerable amount of time trying, but all the methods seem to assume either that i'm running apache, or that i know what is triggering the crash so i can hand-run php-cgi, and i don't. the problem is that it's a production server, and the segfaults happen with allot of time between them, with an unknown trigger. all i can tell you is that the hardware is healthy, and all the packages are updated. i'll just continue to update and hope the problem is caught elsewhere. -- Cheers, László -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#549492: [php-maint] Bug#549492: Bug#549492: Bug#549492: segmentation faults in version 5.3.1-4
ok, some helpful person showed me how to do 'attach' to a pid with gdb, so i'm now able to monitor the php-cgi processes. here's an initial backtrace. is this helpful? Program received signal SIGSEGV, Segmentation fault. 0x00698277 in zend_hash_destroy () (gdb) bt #0 0x00698277 in zend_hash_destroy () #1 0x00719575 in ?? () #2 0x00715886 in ?? () #3 0x00643a22 in sapi_deactivate () #4 0x00639485 in php_request_shutdown () #5 0x007172a3 in ?? () #6 0x7f6d4a23aabd in __libc_start_main () from /lib/libc.so.6 #7 0x0042bd79 in _start () -- Cheers, László -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#549492: [php-maint] Bug#549492: Bug#549492: Bug#549492: segmentation faults in version 5.3.1-4
and yet another one: Program received signal SIGSEGV, Segmentation fault. 0x00698277 in zend_hash_destroy () (gdb) bt #0 0x00698277 in zend_hash_destroy () #1 0x00719575 in ?? () #2 0x00715886 in ?? () #3 0x00643a22 in sapi_deactivate () #4 0x00639485 in php_request_shutdown () #5 0x007172a3 in ?? () #6 0x01000701 in ?? () #7 0x01000701 in ?? () #8 0x01000701 in ?? () #9 0x01000701 in ?? () #10 0x01000701 in ?? () #11 0x01000701 in ?? () #12 0x01000701 in ?? () #13 0x01000701 in ?? () #14 0x01000701 in ?? () #15 0x01000701 in ?? () #16 0x01000601 in ?? () #17 0x080001000301 in ?? () #18 0x450fdc00 in ?? () #19 0x7fff in ?? () #20 0x in ?? () -- Cheers, László -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#549492: [php-maint] Bug#549492: Bug#549492: segmentation faults in version 5.3.1-4
i found the segfault was related to libc, so i updated that package and the other dependencies of php-cgi, and that seems to have fixed the segfaults. -- Cheers, László -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#549492: [php-maint] Bug#549492: Bug#549492: segmentation faults in version 5.3.1-4
of course, just as i say that (even though i waited 24 hours) i got a couple more segfaults. :-/ so, php-cgi is still segfaulting, even with all package dependencies for php-cgi and php-mysql current. Feb 24 14:16:27 kernel: [9904871.496277] php-cgi[3520]: segfault at 1000701 ip 7fdba3cedb10 sp 7fff025ad430 error 4 in libc-2.10.2.so[7fdba3cb8000+14a000] -- Cheers, László -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#549492: [php-maint] Bug#549492: Bug#549492: segmentation faults in version 5.3.1-4
Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages php5-mysql depends on: ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib ii libmysqlclient16 5.1.44-2 MySQL database client library ii php5-cgi [phpapi-20090626]5.3.1-5server-side, HTML-embedded scripti ii php5-common 5.3.1-5Common files for packages built fr Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages php5-cgi depends on: ii libbz2-1.0 1.0.5-4 high-quality block-sorting file co ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib ii libcomerr2 1.41.10-1 common error description library ii libdb4.8 4.8.26-1 Berkeley v4.8 Database Libraries [ ii libgssapi-krb5-2 1.8+dfsg~alpha1-7 MIT Kerberos runtime libraries - k ii libk5crypto3 1.8+dfsg~alpha1-7 MIT Kerberos runtime libraries - C ii libkrb5-3 1.8+dfsg~alpha1-7 MIT Kerberos runtime libraries ii libmagic1 5.04-1File type determination library us ii libpcre3 7.8-3 Perl 5 Compatible Regular Expressi ii libssl0.9.80.9.8k-8 SSL shared libraries ii libxml22.7.6.dfsg-2+b1 GNOME XML library ii mime-support 3.48-1MIME files 'mime.types' 'mailcap ii php5-common5.3.1-5 Common files for packages built fr ii tzdata 2010b-1 time zone and daylight-saving time ii ucf3.0025Update Configuration File: preserv ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#549492: [php-maint] Bug#549492: segmentation faults in version 5.3.1-4
something is rotten in Denmark bro. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#549492: [php-maint] Bug#549492: Bug#549492: segmentation faults in version 5.3.1-4
On Mon, Feb 22, 2010 at 3:15 AM, Ondřej Surý ond...@debian.org wrote: - your system information (f.e. output of reportbug --template libapache2-mod-php5) System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash - your list of php5 modules installed (and preferrably list of their dependencies as well) only the following are installed: libapache2-mod-php5 php5-cgi php5-curl php5-gd php5-mcrypt php5-mysql php5-common php5 - install php5-dbg and get proper backtrace (/usr/share/doc/apache2.2-common/README.backtrace) i run cherokee, not apache. do you know how to get backtraces with cherokee? -- Cheers, László -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#549492: segmentation faults in version 5.3.1-4
i've started to see this problem after upgrading to version 5.3.1-4 of this package. it's very easy to reproduce, just by browsing around one of my wordpress sites. i see the following in my syslog: Feb 21 13:28:55 farc kernel: [9642819.574930] php-cgi[18295]: segfault at 1000721 ip 00698277 sp 7fff5b86a270 error 4 in php5-cgi[40+6fe000] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525358: Better testcase, --exclude-dir only works with a REGEX.
Thanks for the advice. Just changing the option name, but using the old pattern syntax, didn't work in all cases, though. I created a better testcase: # mkdir -p /tmp/clamtest/test1 /tmp/clamtest/kde-htest # mkdir -p /clamtest/test1 # touch /tmp/clamtest/test1/clamtest.test1.sample.file # cp /tmp/kde-htest/konqueror-crash-Gpj9Ca.log /tmp/clamtest/kde-htest/ # touch /clamtest/test1/clamtest.test1.sample.file # touch /clamtest/test1/junk # clamscan -r --exclude-dir=//clamtest/ /tmp /clamtest /tmp/clamtest/tmp.clamtest.sample.file: Empty file /tmp/clamtest/kde-htest/konqueror-crash-Gpj9Ca.log: OK /tmp/clamtest/tmp/temp.clamtest.tmp.sample.file: OK /tmp/.X0-lock: OK /clamtest/test1/clamtest.test1.sample.file: Empty file /clamtest/test1/junk: Empty file So just changing from --exclude to --exclude-dir, using the original syntax for PATT of // to indicate a root directory doesn't work. Later Internet search on --exclude-dir turned up http://www.linuxforums.org/forum/redhat-fedora-linux-help/56093-clam-av.html which shows the Fedora version of clamscan --help saying that the syntax is --exclude-dir=REGEX I tested this and found that it works: # clamscan -r --exclude-dir=^/clamtest/ /tmp /clamtest /tmp/clamtest/tmp.clamtest.sample.file: Empty file /tmp/clamtest/kde-htest/konqueror-crash-Gpj9Ca.log: OK /tmp/clamtest/tmp/temp.clamtest.tmp.sample.file: OK /tmp/.X0-lock: OK /clamtest: Excluded So sometime between clamav 0.92.1 and 0.94.dfsg.2-1lenny2, the syntax for --exclude-dir=PATT (and related options) changed to require PATT to be a regular expression. Is there any chance of getting the man page and --help output changed to say REGEX instead of PATT? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#544131: libpam-mount: umount.crypt returns 1 on success, causes bogus pam_mount unmount failed message
Package: libpam-mount Version: 1.10-1 Severity: minor Got the following from /var/log/auth.log : 3795 Aug 28 23:46:00 athlon login[26999]: pam_mount(pam_mount.c:312): pam_mount 1.10: entering auth stage 3796 Aug 28 23:46:01 athlon login[26999]: pam_unix(login:session): session opened for user wife by LOGIN(uid=0) 3797 Aug 28 23:46:01 athlon login[26999]: pam_mount(pam_mount.c:458): pam_mount 1.10: entering session stage 3798 Aug 28 23:46:02 athlon login[26999]: pam_mount(pam_mount.c:479): back from global readconfig 3799 Aug 28 23:46:02 athlon login[26999]: pam_mount(pam_mount.c:481): per-user configurations not allowed by pam_mount.conf 3799 .xml 3800 Aug 28 23:46:02 athlon login[26999]: pam_mount(misc.c:38): Session open: (uid=0, euid=0, gid=615, egid=615) 3801 Aug 28 23:46:03 athlon login[26999]: pam_mount(rdconf2.c:182): checking sanity of volume record (/dev/disk/by-id/usb-H 3801 itachi_HTS543232L9A300_090423FB2403-0:0-part5) 3802 Aug 28 23:46:03 athlon login[26999]: pam_mount(pam_mount.c:536): about to perform mount operations 3803 Aug 28 23:46:04 athlon login[26999]: pam_mount(mount.c:181): Mount info: globalconf, user=wife volume server=(null) 3803 path=/dev/disk/by-id/usb-Hitachi_HTS543232L9A300_090423FB2403-0:0-part5 mountpoint=/home/wife cipher=(null) fsk 3803 eypath=(null) fskeycipher=(null) fskeyhash=(null) options=exec,fsck,nodev,nosuid,user_xattr,noatime / fstab=0 3803 3804 Aug 28 23:46:04 athlon login[26999]: pam_mount(mount-sysv.c:57): realpath of volume /home/wife is /home/wife 3805 Aug 28 23:46:04 athlon login[26999]: pam_mount(mount-sysv.c:61): checking to see if /dev/disk/by-id/usb-Hitachi_HTS543 3805 232L9A300_090423FB2403-0:0-part5 is already mounted at /home/wife 3806 Aug 28 23:46:05 athlon login[26999]: pam_mount(mount.c:494): checking for encrypted filesystem key configuration 3807 Aug 28 23:46:05 athlon login[26999]: pam_mount(mount.c:497): about to start building mount command 3808 Aug 28 23:46:05 athlon login[26999]: command: [mount.crypt] [-oexec,fsck,nodev,nosuid,user_xattr,noatime] [/dev/disk/b 3808 y-id/usb-Hitachi_HTS543232L9A300_090423FB2403-0:0-part5] [/home/wife] 3809 Aug 28 23:46:06 athlon login[14582]: pam_mount(misc.c:38): set_myuidpre: (uid=0, euid=0, gid=615, egid=615) 3810 Aug 28 23:46:06 athlon login[14582]: pam_mount(misc.c:38): set_myuidpost: (uid=0, euid=0, gid=615, egid=615) 3811 Aug 28 23:46:06 athlon login[26999]: pam_mount(mount.c:75): mount errors: 3812 Aug 28 23:46:07 athlon login[26999]: pam_mount(mount.c:78): Command successful. 3813 Aug 28 23:46:09 athlon login[26999]: pam_mount(mount.c:539): waiting for mount 3814 Aug 28 23:46:09 athlon login[26999]: command: [pmvarrun] [-u] [wife] [-o] [1] 3815 Aug 28 23:46:10 athlon login[14772]: pam_mount(misc.c:38): set_myuidpre: (uid=0, euid=0, gid=615, egid=615) 3816 Aug 28 23:46:10 athlon login[14772]: pam_mount(misc.c:38): set_myuidpost: (uid=0, euid=0, gid=615, egid=615) 3817 Aug 28 23:46:10 athlon login[26999]: pam_mount(pam_mount.c:418): pmvarrun says login count is 1 3818 Aug 28 23:46:11 athlon login[26999]: pam_mount(pam_mount.c:550): done opening session (ret=0) 3819 Aug 28 23:46:40 athlon login[26999]: pam_unix(login:session): session closed for user wife 3820 Aug 28 23:46:40 athlon login[26999]: pam_mount(pam_mount.c:592): received order to close things 3821 Aug 28 23:46:40 athlon login[26999]: pam_mount(misc.c:38): Session close: (uid=0, euid=0, gid=615, egid=615) 3822 Aug 28 23:46:41 athlon login[26999]: command: [pmvarrun] [-u] [wife] [-o] [-1] 3823 Aug 28 23:46:41 athlon login[15548]: pam_mount(misc.c:38): set_myuidpre: (uid=0, euid=0, gid=615, egid=615) 3824 Aug 28 23:46:41 athlon login[15548]: pam_mount(misc.c:38): set_myuidpost: (uid=0, euid=0, gid=615, egid=615) 3825 Aug 28 23:46:42 athlon login[26999]: pam_mount(pam_mount.c:418): pmvarrun says login count is 0 3826 Aug 28 23:46:42 athlon login[26999]: pam_mount(mount.c:673): going to unmount 3827 Aug 28 23:46:42 athlon login[26999]: pam_mount(mount.c:181): Mount info: globalconf, user=wife volume server=(null) 3827 path=/dev/disk/by-id/usb-Hitachi_HTS543232L9A300_090423FB2403-0:0-part5 mountpoint=/home/wife cipher=(null) fsk 3827 eypath=(null) fskeycipher=(null) fskeyhash=(null) options=exec,fsck,nodev,nosuid,user_xattr,noatime / fstab=0 3827 3828 Aug 28 23:46:43 athlon login[26999]: command: [umount.crypt] [/home/wife] 3829 Aug 28 23:46:43 athlon login[15550]: pam_mount(misc.c:38): set_myuidpre: (uid=0, euid=0, gid=615, egid=615) 3830 Aug 28 23:46:43 athlon login[15550]: pam_mount(misc.c:38): set_myuidpost: (uid=0, euid=0, gid=615, egid=615) 3831 Aug 28 23:46:44 athlon login[26999]: pam_mount(mount.c:340): waiting for umount 3832 Aug 28 23:46:44 athlon login[26999]: pam_mount(mount.c:676): unmount of /dev/disk/by-id/usb-Hitachi_HTS543232L9A300_09
Bug#525358: clamav: clamscan --exclude option stopped working
Package: clamav Version: 0.94.dfsg.2-1lenny2 Severity: normal Was using the option --exclude=//sys/ in clamscan to not scan the /sys directory, when running a scan of the entire system (clamscan -r /). This worked in clamscan 0.90.x and 0.92.1. After upgrade to lenny, my clamscan report now includes a bunch of open errors on things in /sys . Old clamscan doc used to say to add an extra '/' to the beginning of the exclude pattern, to indicate that the pattern was in a root directory, and did not require any wildcards. Faster testcase: Try to prevent scanning of the /sys/block directory's contents, when scanning the /sys directory tree: # clamscan -r /sys scans everything under /sys, as it should None of the following variants prevent scanning the /sys/block directory: # clamscan -r --exclude=/block/ /sys # clamscan -r --exclude=block /sys # clamscan -r --exclude='block' /sys # clamscan -r --exclude='.*block.*' /sys # clamscan -r --exclude='\.*block\.*' /sys # clamscan -r --exclude='/.*block.*/' /sys # clamscan -r --exclude='*block*' /sys -- Package-specific info: --- configuration --- /etc/clamav/clamd.conf: clamd directives -- LogFile = /var/log/clamav/clamav.log LogFileUnlock = no LogFileMaxSize = 0 LogTime = yes LogClean = no LogVerbose = no LogSyslog = no LogFacility = LOG_LOCAL6 PidFile = /var/run/clamav/clamd.pid TemporaryDirectory = /tmp ScanPE = yes ScanELF = yes DetectBrokenExecutables = no ScanMail = yes MailFollowURLs = no ScanPartialMessages = no PhishingSignatures = yes PhishingScanURLs = yes PhishingAlwaysBlockCloak = no PhishingAlwaysBlockSSLMismatch = no HeuristicScanPrecedence = no DetectPUA = no ExcludePUA not set IncludePUA not set StructuredDataDetection = no StructuredMinCreditCardCount = 3 StructuredMinSSNCount = 3 StructuredSSNFormatNormal = yes StructuredSSNFormatStripped = no AlgorithmicDetection = yes ScanHTML = yes ScanOLE2 = yes ScanPDF = yes ScanArchive = yes MaxScanSize = 104857600 MaxFileSize = 26214400 MaxRecursion = 16 MaxFiles = 1 ArchiveLimitMemoryUsage = no ArchiveBlockEncrypted = no DatabaseDirectory = /var/lib/clamav TCPAddr not set TCPSocket not set LocalSocket = /var/run/clamav/clamd.ctl MaxConnectionQueueLength = 15 StreamMaxLength = 10485760 StreamMinPort = 1024 StreamMaxPort = 2048 MaxThreads = 12 ReadTimeout = 180 IdleTimeout = 30 MaxDirectoryRecursion = 15 ExcludePath not set FollowDirectorySymlinks = no FollowFileSymlinks = no ExitOnOOM = no Foreground = no Debug = no LeaveTemporaryFiles = no FixStaleSocket = yes User = clamav AllowSupplementaryGroups = yes SelfCheck = 3600 VirusEvent not set ClamukoScanOnAccess not set ClamukoScanOnOpen not set ClamukoScanOnClose not set ClamukoScanOnExec not set ClamukoIncludePath not set ClamukoExcludePath not set ClamukoMaxFileSize = 5242880 DevACOnly not set DevACDepth not set *** MailMaxRecursion is DEPRECATED *** *** ArchiveMaxFileSize is DEPRECATED *** *** ArchiveMaxRecursion is DEPRECATED *** *** ArchiveMaxFiles is DEPRECATED *** *** ArchiveMaxCompressionRatio is DEPRECATED *** *** ArchiveBlockMax is DEPRECATED *** /etc/clamav/freshclam.conf: freshclam directives -- LogFileMaxSize = 0 LogTime = no LogVerbose = no LogSyslog = no LogFacility = LOG_LOCAL6 PidFile = /var/run/clamav/freshclam.pid DatabaseDirectory = /var/lib/clamav/ Foreground = no Debug = no AllowSupplementaryGroups = no DatabaseOwner = clamav Checks = 24 UpdateLogFile = /var/log/clamav/freshclam.log DNSDatabaseInfo = current.cvd.clamav.net DatabaseMirror = db.local.clamav.net DatabaseMirror = database.clamav.net MaxAttempts = 5 ScriptedUpdates = yes CompressLocalDatabase = no HTTPProxyServer not set HTTPProxyPort not set HTTPProxyUsername not set HTTPProxyPassword not set HTTPUserAgent not set NotifyClamd not set OnUpdateExecute not set OnErrorExecute not set OnOutdatedExecute not set LocalIPAddress not set ConnectTimeout = 30 ReceiveTimeout = 30 SubmitDetectionStats not set DetectionStatsCountry not set Engine and signature databases -- Engine version: 0.94.2 Database directory: /var/lib/clamav/ main db: Format: .cld, Version: 50, Build time: Sun Feb 15 16:47:25 2009 daily db: Format: .cld, Version: 9280, Build time: Thu Apr 23 14:37:01 2009 --- data dir --- total 46184 -rw-r--r-- 1 clamav clamav 2839552 2009-04-23 15:45:32 daily.cld -rw-r--r-- 1 clamav clamav 44391424 2009-04-20 05:08:16 main.cld -rw--- 1 clamav clamav 780 2009-04-23 17:45:32 mirrors.dat -- System Information: Debian Release: 5.0.1 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686-bigmem (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages clamav depends on: ii clamav-freshclam [cl 0.94.dfsg.2-1lenny2 anti-virus
Bug#524148: lenny release-notes and Wiki Etch2LennyUpgrade give contradictory pin-priority advice
Package: release-notes Version: 5.0.1 Severity: normal http://wiki.debian.org/Etch2LennyUpgrade section Backports says: If you do not use one of these exceptions, you can safely upgrade to lenny. If you use one of these exceptions, set the pin-priority (see man apt_preferences) temporarily to 1001 for all packages from etch, and you should be able to do a safe dist-upgrade too. The corresponding paragraph in 4.2.5.1. Using backports.org packages of http://www.debian.org/releases/stable/i386/release-notes/ch-upgrading.en.html says: If you do not use one of these exceptions, you can safely upgrade to lenny. If you use one of these exceptions, set the Pin-Priority (see apt_preferences(5)) temporarily to 1001 for all packages from lenny, and you should be able to do a safe dist-upgrade too. See the backports FAQ. Note that one says to pin etch, the other says to pin lenny. http://backports.org/dokuwiki/doku.php?id=faq (the backports FAQ) says: If you do not use one of these exceptions, you can safely upgrade to etch. If you use one of these exceptions, set the pin-priority (see man apt_preferences) temporarily to 1001 for all packages from etch, and you should be able to do a safe dist-upgrade too. But the backports FAQ says it is talking about upgrading from sarge-backports to etch. So, I'm guessing that it means to pin the version that you're upgrading TO, but I'm not sure. Please fix these documents to be consistent. -- System Information: Debian Release: 5.0 Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.26-bpo.1-686-bigmem Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#295469: centericq: Jabber/PGP doesn't decrypt when receiving multiple x tags
Package: centericq Version: 4.20.0-1 Severity: important if a jabber message sent by an advanced client (e.g. psi) contains extra x-tags besides the content (e.g. for composing), centericq doesn't correctly detect the fact that the message is encrypted, and doesn't decrypt it (losing the message's content as well as the 'pgp-enabled' flag for that user). while it works with all other users, it makes Jabber/PGP unusable for the corresponding subset of users using this feature. a fix is already available in CVS, but a release doesn't seem to be forthcoming soon. please integrate a patch ... thanks in advance! -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.10-rc3-fltln-fltln Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages centericq depends on: ii centericq-common4.20.0-1 A text-mode multi-protocol instant ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii libcurl37.13.0-1 Multi-protocol file transfer libra ii libgcc1 1:3.4.3-9GCC support library ii libgnutls11 1.0.16-13GNU TLS library - runtime library ii libgpg-error0 1.0-1library for common error values an ii libgpgme11 1.0.2-1 GPGME - GnuPG Made Easy ii libidn110.5.2-3 GNU libidn library, implementation ii libjpeg62 6b-9 The Independent JPEG Group's JPEG ii libncurses5 5.4-4Shared libraries for terminal hand ii libssl0.9.7 0.9.7e-3 SSL shared libraries ii libstdc++5 1:3.3.5-8The GNU Standard C++ Library v3 ii zlib1g 1:1.2.2-4compression library - runtime -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
