Bug#1010737: logwatch: dhcpd service doesn't output anything

2022-05-08 Thread Jefferson Cowart
Package: logwatch Version: 7.5.5-1 Severity: normal Running logwatch with the dhcpd service doesn't result in any output despite there being lots of dhcpd log lines. I've spent a little while trying to understand how dhcpd parsing is supposed to work, but I'm not quickly able to figure out wher

Bug#563449: More Data

2010-01-19 Thread Jefferson Cowart
ies it's a problem with the peer setup. Perhaps something along the lines of "Jan 2 16:27:00 artemis dhcpd: DHCPDISCOVER from 00:24:14:2e:15:19 via 134.173.131.254: client member of class denied access to pool" or something like that would be helpful. -- Thank You Jefferson C

Bug#563449: dhcp3-server: Incorrect "peer holds all free leases" log entries

2010-01-02 Thread Jefferson Cowart
Package: dhcp3-server Version: 3.1.1-6+lenny3 Severity: normal I have a pair of servers running the dhcp3-server package using the failover funcationality. Periodically I get log entries like the following: Jan 2 16:27:00 artemis dhcpd: DHCPDISCOVER from 00:24:14:2e:15:19 via 134.173.131.254: pe

Bug#493016: libc6: ldd doesn't work with ACLs

2008-08-06 Thread Jefferson Cowart
= 1 read(0, "\n", 1)= 1 write(2, "+ test -r ./pdficon\n", 20+ test -r ./pdficon ) = 20 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0 stat64("./pdficon", {st_mode=S_IFREG|0770, st_size=17209, ...}) = 0 rt_sigprocmask(SIG_SETMASK, [],

Bug#493016: libc6: ldd doesn't work with ACLs

2008-07-31 Thread Jefferson Cowart
set -o pipefail + case $# in + single_file=t + result=0 + for file in '"$@"' + test t = t + case $file in + file=./pdficon + test '!' -f ./pdficon + test -r ./pdficon + echo ldd: 'error: you do not have read permission for' '`./pdficon'\''&#

Bug#493050: libapache-htpasswd-perl: Allow setting passwords to sha1

2008-07-30 Thread Jefferson Cowart
Package: libapache-htpasswd-perl Version: 1.8-0.1 Severity: normal Starting with version 1.7 this module has support for checking SHA1 passwords. It would be nice if it would let me write SHA1 passwords. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable')

Bug#493016: libc6: ldd doesn't work with ACLs

2008-07-30 Thread Jefferson Cowart
Package: libc6 Version: 2.3.6.ds1-13etch7 Severity: normal ldd doesn't work properly with ACLs. As you can see below I have read access to the pdficon file. However ldd insists I don't. [EMAIL PROTECTED]:/srv/ccdl.libraries.claremont.edu/Content4.3/bin$ ldd pdficon ldd: error: you do not have r

Bug#486385: clamav-freshclam: logcheck rules out of date with virus db extension change

2008-06-15 Thread Jefferson Cowart
Package: clamav-freshclam Version: 0.93.1.dfsg-volatile1 Severity: minor Tags: patch With the update to clamav 0.93, the file extension that is used to store the database files on disk changed. Currently the following line exists in the /etc/logcheck/ignore.d.server/clamav-freshclam file: ^\w{3}

Bug#435199: clamav-freshclam: logcheck updates for freshclam

2007-07-29 Thread Jefferson Cowart
Package: clamav-freshclam Version: 0.91.1-1~volatile1 Severity: minor Tags: patch At some point freshclam started logging lines like this: Jul 22 18:38:21 p450 freshclam[24475]: Downloading daily-3737.cdiff [100%] Here is a rule that supresses those messages from logcheck: ^\w{3} [ :0-9]{11} [.

Bug#420391: Also seeing this

2007-04-21 Thread Jefferson Cowart
47376. They then seem to level off. Perhaps there is a memory leak somewhere? -- Thanks Jefferson Cowart [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#415073: clamav-freshclam: logcheck updates for freshclam

2007-03-15 Thread Jefferson Cowart
Package: clamav-freshclam Version: 0.90.1-2 Severity: minor Tags: patch The current clamav-freshclam package includes the following line in the logcheck ignore file: ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ freshclam\[[0-9]+\]: (daily|main)\.cvd (is up to date|updated) \(version: [0-9]+, sigs: [0-9]+,

Bug#405786: logcheck-database: extended DSN status missing in postfix ignore lines

2007-01-09 Thread Jefferson Cowart
I haven't needed to make any modifications to any of those. (So either they are fine or postfix hasn't thrown that message.) ==== Thanks Jefferson Cowart [EMAIL PROTECTED] Index: violations.ignore.d/log

Bug#253293: Status with Apache2.2

2007-01-07 Thread Jefferson Cowart
I just tried to build and use this with apache2.2. It was able to build, but I got a 500 server error when trying to access the page. (I got the error independent of if I entered the proper username/password.) -- Thanks Jefferson Cowart [EMAIL PROTECTED] -- To UNSUBSCRIBE

Bug#405786: logcheck-database: extended DSN status missing in postfix ignore lines

2007-01-06 Thread Jefferson Cowart
pace:]]+>)? proto=E?SMTP( helo=<[^[:space:]]+>)?$ ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ postfix/[ls]mtp\[[0-9]+\]: [[:upper:][:digit:]]+: to=<[^[:space:]]+>,( orig_to=<[^[:space:]]+>,)* relay=[^[:space:]]+,( conn_use=[[:digit:]]+,)? delay=[.0-9]+,( delays=[.0-9/]+, dsn=[0-9.]+,)? status=sent

Bug#405786: logcheck-database: extended DSN status missing in postfix ignore lines

2007-01-06 Thread Jefferson Cowart
Package: logcheck-database Version: 1.2.52 Severity: normal Tags: patch At least one of the postfix logcheck ignore lines is missing the extended dsn. I had to modify the following one. There may be others. ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ postfix/smtpd\[[0-9]+\]: NOQUEUE: reject: [[:upper:]]+

Bug#405745: logcheck-database: postfix violations.ignore entries missing between sarge/etch

2007-01-05 Thread Jefferson Cowart
Package: logcheck-database Version: 1.2.51 Severity: minor Tags: patch The sarge version of logcheck-database has a few violations.ignore entries for postfix that appear to be missing in etch. Scanning the changelogs and related bug reports I don't see a reason that they disappeared. These entries

Bug#285406: Back with Etch

2007-01-05 Thread Jefferson Cowart
heck: spamd: result: . -2 - AWL,BAYES_00,NORMAL_HTTP_TO_IP,NO_RELAYS scantime=13.2,size=1157,user=jeff,uid=110,required_score=5.0,rhost=P450,raddr=127.0.0.1,rport=59428,mid=<[EMAIL PROTECTED]>,bayes=5.55111512312578e-17,autolearn=ham -- ==== Thanks Jefferson Cowart [EMAIL P

Bug#404921: fail2ban: wrong default log for postfix

2006-12-29 Thread Jefferson Cowart
EMAIL PROTECTED]> proto=SMTP helo= Thus I'd say that regex is proper. -- ==== Thanks Jefferson Cowart [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#404921: fail2ban: wrong default log for postfix

2006-12-29 Thread Jefferson Cowart
Package: fail2ban Version: 0.7.5-2 Severity: normal By default the postfix log looks at /var/log/postfix.log. By default postfix logs to /var/log/mail.log. (The other two mail server entries properly look at /var/log/mail.log.) -- System Information: Debian Release: 4.0 APT prefers testing AP

Bug#377711: fail2ban: Add postfix rules

2006-07-10 Thread Jefferson Cowart
Package: fail2ban Severity: wishlist I've been having problems with some abusive clients running dictionary attacks against my mail servers for a few years. It would be nice if fail2ban had support for postfix and could automatically ban these IPs. I've included a sample line below: Jul 10 12:39:

Bug#377461: Acknowledgement (owl-dms: two config files present)

2006-07-09 Thread Jefferson Cowart
-l html lrwxrwxrwx 1 root root 18 Jul 8 23:41 html -> /usr/share/owl-dms maybe you had problem,, because owl use file() function in php, I had some problems with it,, if you try to use ln -sf /usr/share/owl-dms /var/www/www When you try to access it in browser,, you will has a pr

Bug#377461: Acknowledgement (owl-dms: two config files present)

2006-07-09 Thread Jefferson Cowart
/owl-dms/config/owl.php file: $default->owl_root_url = "/owl-dms"; This is part of my confusion here. We have the same parameter in both places, and it appears that I have to actually modify the file in /usr/share/owl-dms to get the desired settings. -- ---

Bug#377461: Acknowledgement (owl-dms: two config files present)

2006-07-09 Thread Jefferson Cowart
I just realized that the one in /etc/owl-dms is actually called config.php. In any case it looks very similar to the other file. -- Thanks Jefferson Cowart [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Troubl

Bug#377202: owl-dms: php4 depedancy too tight

2006-07-09 Thread Jefferson Cowart
help. -- Thanks Jefferson Cowart [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#377461: owl-dms: two config files present

2006-07-09 Thread Jefferson Cowart
Package: owl-dms Version: 0.90-1 Severity: normal There are two copies of owl.php shipped in this package. Onc ends up in /etc/owl-dms. Another ends up in /usr/share/owl-dms/config. It looks like owl is sometimes reading the latter. I suspect the latter should simply be a symlink to the former.

Bug#377202: owl-dms: php4 depedancy too tight

2006-07-07 Thread Jefferson Cowart
. (It would make life substantially easier for people that want to run the package on sarge.) Regards JOse Carlos -- Thanks Jefferson Cowart [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#377202: owl-dms: php4 depedancy too tight

2006-07-07 Thread Jefferson Cowart
Package: owl-dms Severity: wishlist I would like to use the owl-dms package on a sarge system. At the moment the only thing that prevents me from doing so is the fact that it depends on a version of php4 newer than what is in sarge. The upstream website seems to say that it would work with the ver

Bug#349943: iptables: ROUTE and CONNMARK options don't seem to work

2006-01-28 Thread Jefferson Cowart
Reopen 349943 I was running the stock Debian sarge 2.6 kernel. The documentation in sarge says that option exists. If it doesn't (which appears to be the case) there should be a note in the docs saying you need at least kernel 2.6.x. Thanks Jefferson Cowart [EMAIL PROT

Bug#349943: iptables: ROUTE and CONNMARK options don't seem to work

2006-01-25 Thread Jefferson Cowart
Package: iptables Version: 1.2.11-10 Severity: normal The CONNMARK and ROUTE targets for the mangle table don't appear to work. I have the iptable_mangle module loaded, but when I try to add a rule using that target I get an error: jcc02003-1:/home/jeff# /sbin/iptables -t mangle -A POSTROUTING -o

Bug#270376: Appears fixed in 2.6.14

2006-01-02 Thread Jefferson Cowart
I just installed 2.6.14 (from backports) and it appears that all the problems are fixed. I would close this bug, but I don't know how to do it properly so the version tracking and such works. -- Thanks Jefferson Cowart [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [

Bug#345149: spamassassin: Error Message: "prefork: select returned error on server filehandle:"

2005-12-29 Thread Jefferson Cowart
Package: spamassassin Version: 3.1.0a-1bpo1 Severity: minor I've been getting the above error message with some frequency in my spamassassin logs. It appears that it usually happens right after the master spamassassin process cleans up a child process. I've pasted 2 examples below. Let me know if

Bug#344953: Fixing Submitter E-Mail

2005-12-28 Thread Jefferson Cowart
submitter 344953 ! -- Fixing my submitter e-mail address. Thanks Jefferson Cowart [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#344953: spamassassin: Minor logcheck adjustments

2005-12-27 Thread Jefferson Cowart
Package: spamassassin Version: 3.1.0a-1bpo1 Severity: minor The logcheck files in spamassassin need a few minor tweaks. 1. The following rules appear to be out of date and don't match anything anymore: a)^\w{3} [ :0-9]{11} [._[:alnum:]-]+ spamd\[[0-9]+\]:( spamd:)? server hit by SIGCHLD$ b)^\w{3

Bug#253293: Patch Works

2005-12-26 Thread Jefferson Cowart
I just wanted to note that this patch appeared to work for me. If someone that is a DD could actually package it that would be great. -- Thanks Jefferson Cowart [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Troubl

Bug#333793: Fixed Upstream

2005-12-24 Thread Jefferson Cowart
tags 333793 +fixed-upstream +patch I also got bit by this one and I just wanted to record that the patch upstream (http://issues.apache.org/SpamAssassin/attachment.cgi?id=3310) appears to apply cleanly against 3.1.0a-1bpo1 (from backports.org). -- Thanks Jefferson Cowart

Bug#339133: fail2ban: Race condition in default fwstart

2005-11-14 Thread Jefferson Cowart
Package: fail2ban Version: 0.5.4-7 Severity: minor There is a minor race condition in the default iptables rules in fwstart. Right now it creates the new chain, creates a rule at the start of INPUT to the new chain, and then puts a rule in the new chain with a result of RETURN. It should instead,

Bug#270376: Status Update?

2005-07-13 Thread Jefferson Cowart
I was just wondering what the status of this bug is? Do the current kernels in Sid fix this? Thanks Jefferson Cowart [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#312279: Error Message on 2.4.27 boot

2005-07-04 Thread Jefferson Cowart
(Sorry this took so long for me to get. The person I was hoping was going to be able to get it for me was on vacation for a while and then I forgot about it. In any case below is what I get when trying to boot 2.4.27.) hda3: bad access: block=4, count=4 end_request: I/O error, dev 03:03 (hda),

Bug#285406: Fixed on Sarge Upgrade

2005-07-04 Thread Jefferson Cowart
For the record this bug appears to have gone away when I upgraded the rest of my system to Sarge. Don't know what exactly fixed it, but it is now showing up in syslog as spamd. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#283231: Seconded

2005-06-19 Thread Jefferson Cowart
I'd just like to add that I'd also really like to see this. Just trying to manage a sudoers file across 10 systems is getting to be a pain. If I could centralize it that would be very very nice. ---- Thanks Jefferson Cowart [EMAIL PROTECTED] -- To UNSUBSCRIBE, email

Bug#313279: base-config: Should reload daemons that depend on timezone after setting the timezone

2005-06-12 Thread Jefferson Cowart
Package: base-config Version: 2.53.10 Severity: normal After doing a fresh sarge install a few days ago I noticed that both my syslogs and cron seemed to be running in UTC. (The time stamps in my logs were in UTC and the crontabs were being interpreted as UTC rather than local time.) Running the d

Bug#312279: kernel-image-2.4.27-2-586tsc: System fails to boot with 2.4.27 installed

2005-06-07 Thread Jefferson Cowart
when I do an upgrade on 2.6.8 I have some other kernel around to fall back on. ---- Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: Horms [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 07, 2005 03:09 > To: Jefferson Cowart; [EMAIL PR

Bug#312279: Error Message

2005-06-07 Thread Jefferson Cowart
I am not physically in front of the system at the moment and I just discovered the person I was going to ask to record the exact error message and pass it on to me is away for a few days. As such it might take me a little longer to get you the exact error sorry. Thanks Jefferson

Bug#312279: kernel-image-2.4.27-2-586tsc: System fails to boot with 2.4.27 installed

2005-06-06 Thread Jefferson Cowart
Package: kernel-image-2.4.27-2-586tsc Version: 2.4.27-10 Severity: important I installed kernel-image-2.4.27-2-586tsc on my system. After rebooting the system failed to boot with a kernel panic and something about killing init. (Sorry I don't remember the exact error, but it is the kind of error I

Bug#310389: analog: Upgrade from woody->sarge fails

2005-05-23 Thread Jefferson Cowart
Package: analog Version: 2:5.32-13 Severity: important Tags: sarge Upgrading from the woody version of analog to the version in sarge fails: # aptitude install Reading Package Lists... Done Building Dependency Tree Reading extended state information Initializing package states... Done Reading tas

Bug#308650: xserver-xfree86: Machine crashed applying latest security update. (DSA-723)

2005-05-11 Thread Jefferson Cowart
Package: xserver-xfree86 Version: 4.1.0-16woody6 Severity: important Tags: woody unreproducible This morning when I applied the latest security update for the xfree86 package (DSA-723) my machine crashed. I was sshed into the system and lost connectivity to the system. When I looked at the compute

Bug#308300: clamav-freshclam: freshclam tries to connect to non-existing clamd

2005-05-09 Thread Jefferson Cowart
ure clamav-freshclam to tell it not to notify clamd.) ---- Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: Thilo Pfennig [mailto:[EMAIL PROTECTED] > Sent: Monday, May 09, 2005 02:09 > To: Debian Bug Tracking System > Subject: Bug

Bug#307189: Status?

2005-05-08 Thread Jefferson Cowart
Now that .84-2 is in sarge is a -3 upload expected anytime soon? As the logcheck entries for clamav are quite good it would be nice to see this little bug fixed (preferably for sarge). Thanks Jefferson Cowart [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED

Bug#301587: apt: Odd recommendation on dist-upgrade (upgrade gets it right)

2005-04-15 Thread Jefferson Cowart
s/etc problems, that might fix this problem. Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: Vincent Lefevre [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 14, 2005 15:20 > To: Jefferson Cowart > Cc: [EMAIL PROTECTED] > Subje

Bug#304761: New Postfix package version (2.2.2-1) conflicts with postfix-tls

2005-04-15 Thread Jefferson Cowart
ian source package (2.2.2-0|1) don't generate a postfix-tls package, I would presume that tls support is now in the main package. ---- Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: Cedric Blancher [mailto:[EMAIL PROTECTED] > Sent: Frid

Bug#270376: PCMCIA Nic stops working after upgrading to 2.6.6/7/8

2005-04-13 Thread Jefferson Cowart
I thought the freeze at this point was on ABI changes? I would assume this doesn't change the ABI and thus wouldn't be as big of a problem. ---- Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: Horms [mailto:[EMAIL PROTECTED] >

Bug#304123: Bug in digest handling code leads to infinite loop

2005-04-10 Thread Jefferson Cowart
a new bug to track the status of this in sarge. (Sorry to handle this in a non-standard way, but I believe the thread below explains why this is needed.) ---- Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: Stephen Gran [mailto:[EMAIL PR

Bug#270376: PCMCIA Nic stops working after upgrading to 2.6.6/7/8

2005-04-10 Thread Jefferson Cowart
integrated into the Debian kernel packages. Thanks to everyone for their help. ---- Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: maximilian attems [mailto:[EMAIL PROTECTED] > Sent: Sunday, April 10, 2005 05:48 > To: Jefferso

Bug#270376: PCMCIA Nic stops working after upgrading to 2.6.6/7/8

2005-04-10 Thread Jefferson Cowart
hanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: maximilian attems [mailto:[EMAIL PROTECTED] > Sent: Saturday, April 09, 2005 07:34 > To: Jefferson Cowart > Cc: 'Daniel Ritz'; 'Dominik Brodowski'; > [EMAIL PROTECTED]; [EMAIL P

Bug#270376: PCMCIA Nic stops working after upgrading to 2.6.6/7/8

2005-04-08 Thread Jefferson Cowart
a related note now my second NIC works so it looks like they were indeed the same bug (or at least a related one). ---- Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: maximilian attems [mailto:[EMAIL PROTECTED] > Sent: Friday, April

Bug#270376: PCMCIA Nic stops working after upgrading to 2.6.6/7/8

2005-04-08 Thread Jefferson Cowart
Looks like the patch fixed the problem. What are the chances of getting this included in sarge? Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: maximilian attems [mailto:[EMAIL PROTECTED] > Sent: Friday, April 08, 2005 12:07 > T

Bug#270376: PCMCIA Nic stops working after upgrading to 2.6.6/7/8

2005-04-07 Thread Jefferson Cowart
Thanks for the response. maximilian attems - Let me know when the kernel is built and I'll go ahead and try that. Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: maximilian attems [mailto:[EMAIL PROTECTED] > Sent: Thursday, Apr

Bug#270376: PCMCIA Nic stops working after upgrading to 2.6.6/7/8

2005-04-05 Thread Jefferson Cowart
* 080 7020 2844 3822 0ba4 090 82c0 6062 0a0 0001 7e21 0080 0809 001e 0b0 * 100 Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Mess

Bug#270376: PCMCIA Nic stops working after upgrading to 2.6.6/7/8

2005-04-01 Thread Jefferson Cowart
Daniel Ritz wrote: On Friday 01 April 2005 19:52, Dominik Brodowski wrote: Seems to be the IRQ storm issue again... Daniel, IIRC you worked on that issue before: do you have an idea on how to write a proper patch for this issue? nope it looks more like something else. looking at the debian bug re

Bug#270376: PCMCIA Nic stops working after upgrading to 2.6.6/7/8

2005-04-01 Thread Jefferson Cowart
u can help to resolve that issue. i volountary test build kernels for bug reporter with proposed patches. On Thu, 31 Mar 2005, Jefferson Cowart wrote: (For reference my primary card is a 3C574. My secondary is a 3C589.) .. (I put that card into a Windows XP laptop and it worked fine the

Bug#270376: PCMCIA Nic stops working after upgrading to 2.6.6/7/8

2005-03-31 Thread Jefferson Cowart
> -Original Message- > From: maximilian attems [mailto:[EMAIL PROTECTED] > On Wed, 30 Mar 2005, Jefferson Cowart wrote: > > I'm downloading and testing all 3 now. > > > > The short version is none of the 3 worked (same problem as > what I've alrea

Bug#270376: PCMCIA Nic stops working after upgrading to 2.6.6/7/8

2005-03-30 Thread Jefferson Cowart
I'm downloading and testing all 3 now. The short version is none of the 3 worked (same problem as what I've already seen on 2.6.6-10. Further details, dmsg, etc. below. ---- Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: maximilia

Bug#301587: apt: Odd recommendation on dist-upgrade (upgrade gets it right)

2005-03-27 Thread Jefferson Cowart
known issue that doesn't have a programmable solution at the moment. -------- Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: Matt Zimmerman [mailto:[EMAIL PROTECTED] > Sent: Sunday, March 27, 2005 20:04 > To: Jefferson Cowart; [EMAIL

Bug#301587: apt: Odd recommendation on dist-upgrade (upgrade gets it right)

2005-03-26 Thread Jefferson Cowart
Package: apt Version: 0.5.28.1 Severity: normal This afternoon when I ran a dist-upgrade on my sarge box I got an odd recommendation about upgrading php4: # apt-get dist-upgrade -u Reading Package Lists... Done Building Dependency Tree... Done Calculating Upgrade... Done The following NEW packag

Bug#300716: kernel-image-2.4.27-powerpc-pmac: Error messages about ip length disagreeing

2005-03-21 Thread Jefferson Cowart
Package: kernel-image-2.4.27-powerpc-pmac Version: 2.4.27-1 Severity: minor I'm running the 2.4.27 kernel image from sarge on my debian woody system. For the most part it is working properly, however I'm getting odd error messages in my system log from dhcpd. I see error messages similar to the fo

Bug#299546: clamav-freshclam: Missing logcheck line

2005-03-14 Thread Jefferson Cowart
hclam freshclam\[[0-9]+\]: ClamAV update process started at freshclam\[[0-9]+\]: Received signal 14, wake up freshclam\[[0-9]+\]: (daily|main).cvd is up to date I think you just need to add a 4th line to that to ignore the line of -'s. ---- Thanks Jefferson Cowart [EMAIL

Bug#299546: clamav-freshclam: Missing logcheck line

2005-03-14 Thread Jefferson Cowart
05 fairygm freshclam[2484]: -- ---- Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: Stephen Gran [mailto:[EMAIL PROTECTED] > Sent: Monday, March 14, 2005 19:08 > To: Jefferson Cowart; [EMAIL PROTECTED] &g

Bug#299469: Tagging

2005-03-14 Thread Jefferson Cowart
appears that this was due to clamd consuming all the CPU so other messages were not able to be scanned. Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: Stephen Gran [mailto:[EMAIL PROTECTED] > Sent: Monday, March 14, 2005 18:48 > T

Bug#299469: Tagging

2005-03-14 Thread Jefferson Cowart
tags 299469 +security Thanks As this bug can lead to a DOS condition I'm tagging it as a security bug. (I got bit by this one this morning when this bug was created with the bad message attached.) Thanks Jefferson Cowart [EMAIL PROTECTED] -- To UNSUBSCRIBE, ema

Bug#299546: clamav-freshclam: Missing logcheck line

2005-03-14 Thread Jefferson Cowart
Package: clamav-freshclam Version: 0.83-3 Severity: wishlist I get the following lines in my hourly logcheck e-mail. They should probably be added the default ignore file. freshclam: -- -- System Information: Debian Release: 3.1 APT prefers testing APT pol

Bug#296674: mysql-server: Security bug in MySQL in woody (CAN-2004-0957)

2005-02-23 Thread Jefferson Cowart
Package: mysql-server Version: 3.23.49-8.9 Severity: grave Tags: security woody Justification: user security hole See http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-0957 for more information. Based on that writeup any version of MySQL prior to 3.23.58 is vulnerable. I have checked through

Bug#295046: kernel-image-2.4.18-newpmac: Network dies after "/etc/init.d/networking restart"

2005-02-13 Thread Jefferson Cowart
far as this bug goes if you want to mark it wontfix, that seems to be the best option to me. Hopefully then other people that have the same problem will be able to see the solution that I was able to get working. ---- Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original M

Bug#295046: kernel-image-2.4.18-newpmac: Network dies after "/etc/init.d/networking restart"

2005-02-13 Thread Jefferson Cowart
a constant flux. Sven Luther wrote: On Sun, Feb 13, 2005 at 07:51:54AM -0800, Jefferson Cowart wrote: tags 295046 + woody thanks (Sorry meant to tag this woody originally.) I've been trying to install 2.6 from sarge, but have been running into some problems. I haven't been able to find Powe

Bug#295046: kernel-image-2.4.18-newpmac: Network dies after "/etc/init.d/networking restart"

2005-02-13 Thread Jefferson Cowart
module-init-tools I would be happy to install the 2.6.8 kernel from sarge. (However I don't want to upgrade the entire machine to sarge.) ---- Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: Sven Luther [mailto:[EMAIL PROTECTED] > Sent: Su

Bug#295046: kernel-image-2.4.18-newpmac: Network dies after "/etc/init.d/networking restart"

2005-02-13 Thread Jefferson Cowart
Package: kernel-image-2.4.18-newpmac Version: 2.4.18-1woody5 Severity: critical Justification: breaks the whole system When I run /etc/init.d/networking restart on my system the network dies. It appears to come up properly - the interface is up and configured, the routing tables appear proper, etc

Bug#270376: PCMCIA Nic stops working after upgrading to 2.6.6/7/8

2005-02-12 Thread Jefferson Cowart
Any update on this? Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: maximilian attems [mailto:[EMAIL PROTECTED] > Sent: Sunday, February 06, 2005 07:04 > To: Jefferson Cowart > Subject: Re: PCMCIA Nic stops working after upgradi

Bug#270376: PCMCIA Nic stops working after upgrading to 2.6.6/7/8

2005-02-12 Thread Jefferson Cowart
The machine I'm running this on is an old Cyrix 233 (or maybe 266). As such I really don't want to compile my own kernel as in my experience that takes a few days. Any chance you could provide an appropriate kernel? ---- Thanks Jefferson Cowart [EMAIL PROTECTED] >

Bug#270376: PCMCIA Nic stops working after upgrading to 2.6.6/7/8

2005-02-06 Thread Jefferson Cowart
--- Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: maximilian attems [mailto:[EMAIL PROTECTED] > Sent: Sunday, February 06, 2005 02:54 > To: Jefferson Cowart > Cc: [EMAIL PROTECTED] > Subject: Re: PCMCIA Nic stops working after upgradin

Bug#270376: 2.6.10 Log

2005-02-05 Thread Jefferson Cowart
interrupts. Fish. Please report. 1 jcc02003-hawk kernel: Yenta: ISA IRQ mask 0x0010, PCI irq 0 Thanks Jefferson Cowart [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#284732: Clamav-freshclam logcheck entries disappeared

2005-02-05 Thread Jefferson Cowart
downloads clamav virus databases from the Internet # locate clam|grep logch # Thanks Jefferson Cowart [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#270376: PCMCIA Nic stops working after upgrading to 2.6.6/7/8

2005-02-05 Thread Jefferson Cowart
I'm still having the same problem. It says it brings the link up, but it doesn't seem to actually get any packets onto the wire. ---- Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: maximilian attems [mailto:[EMAIL PROTECTED]

Bug#293731: honeyd: Inconsistent information in README.Debian

2005-02-05 Thread Jefferson Cowart
Package: honeyd Version: 1.0-4 Severity: normal The section below has been copied out of the README.Debian file that ships with honeyd. It appears to be inconsistent. The first section says the default configuration in debian uses the honeyd user. The next section says that it runs as nobody/no

Bug#292487: clamav-freshclam: Freshclam died

2005-01-27 Thread Jefferson Cowart
Package: clamav-freshclam Version: 0.80-6.backports.org.1 Severity: normal This may be related to 274255 or 274646, but I'm not sure so I'll report it seperately and I'll let you merge as appropriate. This afternoon I noticed that one of my servers was not putting stuff into syslog about having

Bug#290520: spamassassin: please do not criminalise end users, users behind dynamic IP, lower or remove DUL test default score

2005-01-16 Thread Jefferson Cowart
/spamassassin/HowScoresAreAssigned Thanks Jefferson Cowart [EMAIL PROTECTED] > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Sunday, January 16, 2005 11:47 > To: Michelle Konzack > Cc: [EMAIL PROTECTED] > Subject: Bug#29