Bug#403341: munin-node: missing ~ in postfix_mailstats:239 breaks plugin
Package: munin-node Version: 1.2.5-1 Severity: normal when I make this change the plugin works: o9:~# diff postfix_mailstats /usr/share/munin/plugins/postfix_mailstats 239c239 $cause = 'OTHER' unless $1 =/^\d+$/; --- $cause = 'OTHER' unless $1 =~ /^\d+$/; the original line tries to assign the rhs to the read-only $1... -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages munin-node depends on: ii adduser 3.100 Add and remove users and groups ii libnet-server-perl0.94-1 An extensible, general perl server ii lsb-base 3.1-22 Linux Standard Base 3.1 init scrip ii perl 5.8.8-7Larry Wall's Practical Extraction ii procps1:3.2.7-3 /proc file system utilities Versions of packages munin-node recommends: pn libnet-snmp-perl none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#398978: amavisd-new: Please leave my aliases file alone in postinst
Package: amavisd-new Version: 1:2.4.2-4 Severity: minor Adds amavis alias to /etc/aliases without asking. This might work for some configurations, but not all. Can you ask first please? Or maybe check for a commented-out entry in the file as well as an alternate pre-existing alias. Thanks. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages amavisd-new depends on: ii adduser 3.99 Add and remove users and groups ii debconf [debconf-2.0] 1.5.8 Debian configuration management sy ii file 4.17-4 Determines file type using magic ii libarchive-tar-perl 1.30-1 Archive::Tar - manipulate tar file ii libarchive-zip-perl 1.16-1 Module for manipulation of ZIP arc ii libberkeleydb-perl0.29-1 use Berkeley DB 4 databases from P ii libcompress-zlib-perl 1.42-1 Perl module for creation and manip ii libconvert-tnef-perl 0.17-5 Perl module to read TNEF files ii libconvert-uulib-perl 1.06-1 Perl interface to the uulib librar pn libdigest-md5-perlnone (no description available) ii libio-stringy-perl2.110-1Perl5 modules for IO from scalars ii libmailtools-perl 1.74-0.1 Manipulate email in perl programs pn libmime-base64-perl none (no description available) ii libmime-perl 5.420-0.1 Perl5 modules for MIME-compliant m ii libnet-perl 1:1.19-3 Implementation of Internet protoco ii libnet-server-perl0.94-1 An extensible, general perl server ii libunix-syslog-perl 0.100-5Perl interface to the UNIX syslog( ii perl [libtime-hires-perl] 5.8.8-6.1 Larry Wall's Practical Extraction ii perl-modules [libnet-perl]5.8.8-6.1 Core Perl modules ii postfix [mail-transport-agent 2.3.4-1A high-performance mail transport amavisd-new recommends no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#377597: entries in /var/run/utmp are not removed by ajaxterm daemon
Package: ajaxterm Version: 0.7-3 Severity: normal Each login to ajaxterm leaves a login entry in /var/run/utmp; however, each subsequent logout is not recorded in the file. This confuses programs like talk, biff, finger, etc which use the data to locate users logged in to the system. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages ajaxterm depends on: ii python2.3.5-11 An interactive high-level object-o ii python-support0.3.8 automated rebuilding support for p ii python2.3 2.3.5-14 An interactive high-level object-o Versions of packages ajaxterm recommends: ii apache2 2.0.55-4 next generation, scalable, extenda ii apache2-mpm-prefork [httpd] 2.0.55-4 traditional model for Apache2 -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#348990: amavisd-new not tagging messages as SPAM except when quarantining messages
Package: amavisd-new Version: 1:2.3.3-3 Severity: normal Per subject, amavis is not tagging unless the mail is put in the spam quarantine (score exceeds sa_tag2_levl_deflt). Here is the relevant configuration, a log entry and sample headers of a mail which amavis considered spam, but didn't tag: (from 20-debian_defaults) use strict; # COMMONLY ADJUSTED SETTINGS: $QUARANTINEDIR = $MYHOME/quarantine/; $log_recip_templ = undef;# disable by-recipient level-0 log entries $DO_SYSLOG = 1; # log via syslogd (preferred) $SYSLOG_LEVEL = 'mail.debug'; # switch to mail.info to drop debug output, etc $enable_db = 1; # enable use of BerkeleyDB/libdb (SNMP and nanny) $enable_global_cache = 1;# enable use of libdb-based cache if $enable_db=1 $inet_socket_port = 10024; # default listenting socket $sa_spam_subject_tag = '***SPAM*** '; $sa_tag_level_deflt = -10; # add spam info headers if at, or above that level $sa_tag2_level_deflt = 5; # add 'spam detected' headers at that level $sa_kill_level_deflt = 15; # triggers spam evasive actions $sa_dsn_cutoff_level = 0; # spam level beyond which a DSN is not sent $sa_mail_body_size_limit = 500*1024; # don't waste time on SA if mail is larger $sa_local_tests_only = 0;# only tests which do not require internet access? # Quota limits to avoid bombs (like 42.zip) $MAXLEVELS = 14; $MAXFILES = 1500; $MIN_EXPANSION_QUOTA = 100*1024; # bytes $MAX_EXPANSION_QUOTA = 300*1024*1024; # bytes # OTHER MORE COMMON SETTINGS (defaults may suffice): # You should: # Use D_DISCARD to discard data (viruses) # Use D_BOUNCE to generate local bounces by amavisd-new # Use D_REJECT to generate local or remote bounces by the calling MTA # Use D_PASS to deliver the message # # Whatever you do, *NEVER* use D_REJECT if you have other MTAs *forwarding* # mail to your account. Use D_BOUNCE instead, otherwise you are delegating # the bounce work to your friendly forwarders, which might not like it at all. # # On dual-MTA setups, one can often D_REJECT, as this just makes your own # MTA generate the bounce message. Test it first. # # Bouncing viruses is stupid, always discard them after you are sure the AV # is working correctly. Bouncing real SPAM is also useless, if you cannot # D_REJECT it (and don't D_REJECT mail coming from your forwarders!). $final_virus_destiny = D_DISCARD; # (data not lost, see virus quarantine) $final_banned_destiny = D_DISCARD; # D_REJECT when front-end MTA $final_spam_destiny = D_DISCARD; $final_bad_header_destiny = D_PASS; # False-positive prone (for spam) $virus_admin = [EMAIL PROTECTED]; # due to D_DISCARD default # Leave empty (undef) to add no header $X_HEADER_LINE = Debian $myproduct_name at $mydomain; [rest of 20-debian_defaults unchanged from the distributed version] Log entry indicates spam which should be tagged: Jan 20 04:58:19 o9 amavis[25469]: (25469-08) Passed SPAM, [81.199.49.228] [EMAIL PROTECTED] - [EMAIL PROTECTED], Message-ID: [EMAIL PROTECTED], mail_id: 0YsPs5Ury+RQ, Hits: 13.114, 5661 ms But no header tag, no Subject: tag: From [EMAIL PROTECTED] Fri Jan 20 04:58:19 2006 Return-Path: [EMAIL PROTECTED] X-Original-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Received: from localhost (localhost [127.0.0.1]) by o9.88.net (Postfix) with ESMTP id 01F3C430008 for [EMAIL PROTECTED]; Fri, 20 Jan 2006 04:58:19 + (GMT) Received: from o9.88.net ([127.0.0.1]) by localhost (o9.88.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25469-08 for [EMAIL PROTECTED]; Fri, 20 Jan 2006 04:58:13 + (GMT) Received: from hotmail.com (bay7-f5.bay7.hotmail.com [64.4.11.5]) by o9.88.net (Postfix) with ESMTP id EE1E4430007 for [EMAIL PROTECTED]; Fri, 20 Jan 2006 04:58:12 + (GMT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 19 Jan 2006 20:57:04 -0800 Message-ID: [EMAIL PROTECTED] Received: from 81.199.49.228 by by7fd.bay7.hotmail.msn.com with HTTP; Fri, 20 Jan 2006 04:57:04 GMT X-Originating-IP: [81.199.49.228] X-Originating-Email: [EMAIL PROTECTED] X-Sender: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] From: Williams Adenuga [EMAIL PROTECTED] Subject: Real Offer Date: Fri, 20 Jan 2006 04:57:04 + Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-OriginalArrivalTime: 20 Jan 2006 04:57:04.0878 (UTC) FILETIME=[F53708E0:01C61D7D] To: undisclosed-recipients:; X-Virus-Scanned: Debian amavisd-new at 88.net Thanks, Thomas -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages amavisd-new depends on: ii adduser 3.80 Add and remove users and groups ii file 4.15-2 Determines
Bug#348990: amavisd-new not tagging messages as SPAM except when quarantining messages
On Fri, 20 Jan 2006, Henrique de Moraes Holschuh wrote: As you can see, it was tagged. Which one are you using: sendmail milter, or a dual-MTA setup? It's postfix with a dual-MTA (forwarder) setup. It has been operating fine before the recent major upgrade to amavis. What further information would you like? I can tar up /etc/amavis for you as a start. Thanks, Thomas -- Thomas Lakofski +4470 9228 8229'Reality is that which, gnupg550C DD74 4C38 FAC2 E870when you stop believing in it, 1024D/527D151D 360C A37B BB79 527D 151Ddoesn't go away' --PKD -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#348990: amavisd-new not tagging messages as SPAM except when quarantining messages
On Fri, 20 Jan 2006, Henrique de Moraes Holschuh wrote: amavisd-new won't tag mail for non-local recipients. You need to define a proper @local_domains_acl (I notice we didn't ship this in the conf.d files and use the amavis builtin defaults. That's broken and it will be fixed in the next upload), or another member of the @local_domains_maps, which is \%local_domains, [EMAIL PROTECTED], \$local_domains_re. Try adding this: @local_domains_acl = qw( .domain1 .domain2 .domain3 ); to one of the config files (change the domains to the domains that machine is responsible for). Does that fix your problem? I added @local_domains_acl = ( .$mydomain ); # $mydomain and its subdomains It's working again...and now I know a bit more about amavis. many thanks, Thomas -- Thomas Lakofski +4470 9228 8229'Reality is that which, gnupg550C DD74 4C38 FAC2 E870when you stop believing in it, 1024D/527D151D 360C A37B BB79 527D 151Ddoesn't go away' --PKD -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#348990: amavisd-new not tagging messages as SPAM except when quarantining messages
On Fri, 20 Jan 2006, Henrique de Moraes Holschuh wrote: What's the output of: hostname --fqdn and of head -n 1 /etc/mailname ? [EMAIL PROTECTED]:~$ hostname --fqdn o9.88.net [EMAIL PROTECTED]:~$ cat /etc/mailname 88.net [EMAIL PROTECTED]:~$ ok, looks like this'll be causing the problem. I'll define a @local_domains_acl by reference to my old configuration prior to the upgrade. amavisd-new won't tag mail for non-local recipients. You need to define a proper @local_domains_acl (I notice we didn't ship this in the conf.d files and use the amavis builtin defaults. That's broken and it will be fixed in the next upload), or another member of the @local_domains_maps, which is \%local_domains, [EMAIL PROTECTED], \$local_domains_re. Try adding this: @local_domains_acl = qw( .domain1 .domain2 .domain3 ); to one of the config files (change the domains to the domains that machine is responsible for). Does that fix your problem? Will let you know. Thanks! Thomas -- Thomas Lakofski +4470 9228 8229'Reality is that which, gnupg550C DD74 4C38 FAC2 E870when you stop believing in it, 1024D/527D151D 360C A37B BB79 527D 151Ddoesn't go away' --PKD -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#348667: procmail: ignores COMSAT option, sets to 'no' regardless of configuration.
Package: procmail
Version: 3.22-13
Severity: normal
[top of .procmailrc]
SHELL=/bin/sh
PATH=/bin:/usr/bin:/usr/bin
PMDIR=$HOME/.procmail
MAILDIR=$HOME/mail/lists
LOGFILE=$PMDIR/log
DEFAULT=/home/thomas/mail/default/bcc
LOGABSTRACT=all
VERBOSE=no
COMSAT=no
[snip all the rules in the middle]
:0
* ^X-Original-To: [EMAIL PROTECTED]
{
COMSAT=
:0:
/var/mail/thomas
}
COMSAT in this section can be set to 'yes' or 'y' or blank as previously
suggested from a prior bugreport, but regardless of setting the log
reads as follows:
procmail: Match on ^X-Original-To: [EMAIL PROTECTED]
procmail: Assigning COMSAT=yes
procmail: Assigning COMSAT=no
procmail: Locking /var/mail/thomas.lock
procmail: Assigning LASTFOLDER=/var/mail/thomas
procmail: Opening /var/mail/thomas
procmail: Acquiring kernel-lock
procmail: Unlocking /var/mail/thomas.lock
This has happened since the recent upgrades this month.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Versions of packages procmail depends on:
ii libc6 2.3.5-12 GNU C Library: Shared libraries an
Versions of packages procmail recommends:
ii postfix [mail-transport-agent 2.2.8-4A high-performance mail transport
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#348667: acknowledged by developer (Re: Bug#348667: procmail: ignores COMSAT option, sets to 'no' regardless of configuration.)
OK. But if I use COMSAT=yes, the same behaviour is seen. What more information would you need to examine the problem? On Wed, 18 Jan 2006, Debian Bug Tracking System wrote: From: Debian Bug Tracking System [EMAIL PROTECTED] To: Thomas Lakofski [EMAIL PROTECTED] Date: Wed, 18 Jan 2006 04:18:13 -0800 Subject: Bug#348667 acknowledged by developer (Re: Bug#348667: procmail: ignores COMSAT option, sets to 'no' regardless of configuration.) Reply-To: [EMAIL PROTECTED] This is an automatic notification regarding your Bug report #348667: procmail: ignores COMSAT option, sets to 'no' regardless of configuration., which was filed against the procmail package. It has been closed by one of the developers, namely Santiago Vila [EMAIL PROTECTED]. Their explanation is attached below. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact the developer, by replying to this email. Debian bug tracking system administrator (administrator, Debian Bugs database) Received: (at 348667-done) by bugs.debian.org; 18 Jan 2006 12:10:30 + From [EMAIL PROTECTED] Wed Jan 18 04:10:30 2006 Return-path: [EMAIL PROTECTED] Received: from pizarro.unex.es ([158.49.8.2] ident=postfix) by spohr.debian.org with esmtp (Exim 4.50) id 1EzC12-0007Yg-85 for [EMAIL PROTECTED]; Wed, 18 Jan 2006 04:02:20 -0800 Received: from localhost (almendralejo.unex.es [158.49.8.199]) by pizarro.unex.es (Postfix/MJ-1.08) with ESMTP id 1C3DCD13C9; Wed, 18 Jan 2006 13:02:15 +0100 (CET) Received: from pizarro.unex.es ([158.49.8.2]) by localhost (emilio [158.49.17.20]) (amavisd-new, port 10024) with ESMTP id 10480-10; Wed, 18 Jan 2006 13:05:17 +0100 (CET) Received: from guadiana.unex.es (guadiana.unex.es [158.49.17.23]) by pizarro.unex.es (Postfix/MJ-1.08) with ESMTP id BEDB9D1398; Wed, 18 Jan 2006 13:02:10 +0100 (CET) Received: from cantor.unex.es ([158.49.18.105]) by guadiana.unex.es with esmtp (Exim 3.35 #1 (Debian)) id 1EzC0w-00035q-00; Wed, 18 Jan 2006 13:02:10 +0100 Date: Wed, 18 Jan 2006 13:01:02 +0100 (CET) From: Santiago Vila [EMAIL PROTECTED] To: Thomas Lakofski [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: Bug#348667: procmail: ignores COMSAT option, sets to 'no' regardless of configuration. In-Reply-To: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] References: [EMAIL PROTECTED] MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at unex.es X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Level: X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02 On Wed, 18 Jan 2006, Thomas Lakofski wrote: Package: procmail Version: 3.22-13 Severity: normal [...] COMSAT= [...] COMSAT in this section can be set to 'yes' or 'y' or blank as previously suggested from a prior bugreport, but regardless of setting the log reads as follows: procmail: Match on ^X-Original-To: [EMAIL PROTECTED] procmail: Assigning COMSAT=yes procmail: Assigning COMSAT=no procmail: Locking /var/mail/thomas.lock procmail: Assigning LASTFOLDER=/var/mail/thomas procmail: Opening /var/mail/thomas procmail: Acquiring kernel-lock procmail: Unlocking /var/mail/thomas.lock This has happened since the recent upgrades this month. I don't know where you got the idea that COMSAT= is acceptable. This is what the manual says: When assigning boolean values to variables like VERBOSE, DELIVERED or COMSAT, procmail accepts as true every string starting with: a non-zero value, `on', `y', `t' or `e'. False is every string starting with: a zero value, `off', `n', `f' or `d'. My reading of this is that the behaviour of COMSAT= is undefined and you should not rely on it. Please use yes or no, or anything which is properly documented. -- Thomas Lakofski +4470 9228 8229'Reality is that which, gnupg550C DD74 4C38 FAC2 E870when you stop believing in it, 1024D/527D151D 360C A37B BB79 527D 151Ddoesn't go away' --PKD -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#348667: procmail: ignores COMSAT option, sets to 'no' regardless of configuration.
On Wed, 18 Jan 2006, Santiago Vila wrote: From: Santiago Vila [EMAIL PROTECTED] To: Thomas Lakofski [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Date: Wed, 18 Jan 2006 14:12:25 +0100 (CET) Subject: Re: Bug#348667: procmail: ignores COMSAT option, sets to 'no' regardless of configuration. On Wed, 18 Jan 2006, Thomas Lakofski wrote: I found the origin of the COMSAT= null configuration -- it was related to the resolution of a previous bugrep on procmail from 2001: I see. That was a workaround for a bug which procmail had in 2001. The current procmail does not have that bug, so it is in your own interest that you stop using the workaround, as it was never guaranteed to work. OK. I have removed it. I tend to leave configuration alone until something breaks... Not bad going at 4+ years. Thanks, thomas -- Thomas Lakofski +4470 9228 8229'Reality is that which, gnupg550C DD74 4C38 FAC2 E870when you stop believing in it, 1024D/527D151D 360C A37B BB79 527D 151Ddoesn't go away' --PKD -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#324874: still depends on libfwbuilder6
Message-ID: [EMAIL PROTECTED] Date: Thu, 25 Aug 2005 08:05:27 -0700 From: Jeremy T. Bouse [EMAIL PROTECTED] Yes, a new upload is needed. I was waiting for the library to get into the mirrors before I uploaded the new GUI build. Thanks for being so observant as I wasn't aware of the issue yet. So the new GUI build is ready for upload? -- Thomas Lakofski +44 70 9228 8229 'Reality is that which, when you stop believing in it, doesn't go away' --PKD gpg: 1024D/81FD4B43 2B72 53DB 8104 2041 BDB4 F053 4AE5 01DF 81FD 4B43 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#326053: postfix-policyd: Doesn't appear to handle address extensions / VERP correctly
Package: postfix-policyd Version: 1.55-1 Severity: normal I have my address extension in postfix set to '.' for various reasons -- mostly due to address 'validators' often choking on a '+'. I have mailman accordingly set to do VERP using a '.' Unfortunately the policyd doesn't seem to have a facility to take this into account; a sanitised log extract of the problem follows: Sep 1 13:26:00 o9 postfix-policyd: connection from: 127.0.0.1 port: 43457 slots: 1 of 1023 used Sep 1 13:26:00 o9 postfix-policyd: invalid host_array[fd][2]: (recipient): Sep 1 13:26:00 o9 postfix/smtpd[4183]: warning: premature end-of-input on 127.0.0.1:10031 while reading input attribute name Sep 1 13:26:00 o9 postfix/smtpd[4183]: warning: problem talking to server 127.0.0.1:10031: Success Sep 1 13:26:00 o9 postfix/smtpd[4183]: NOQUEUE: reject: RCPT from xxx.x.ch[130.60.xxx.xxx]: 450 Server configuration problem; from= to=[EMAIL PROTECTED] proto=ESMTP helo=xxx.x.ch Thanks for the packaging, it's working well other than this small problem. Thomas -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.12-mh2 Locale: LANG=en_GB.ISO-8859-15, LC_CTYPE=en_GB.ISO-8859-15 (charmap=ISO-8859-15) Versions of packages postfix-policyd depends on: ii libc6 2.3.5-6GNU C Library: Shared libraries an ii libmysqlclient12 4.0.24-10 mysql database client library ii zlib1g1:1.2.3-4 compression library - runtime postfix-policyd recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#307472: patch for rrd COMMENT colon issue
this is probably ugly but it got my graphs back:
--- munin-graph.orig2005-04-03 01:54:11.0 +0100
+++ munin-graph 2005-08-23 17:24:14.0 +0100
@@ -848,10 +848,10 @@
elsif ($global_headers == 1)
{
push (@rrd, COMMENT: . ( x $max_field_len));
- push (@rrd, COMMENT: Cur:);
- push (@rrd, COMMENT:Min:);
- push (@rrd, COMMENT:Avg:);
- push (@rrd, COMMENT:Max: \\j);
+ push (@rrd, COMMENT:Cur\\:);
+ push (@rrd, COMMENT:Min\\:);
+ push (@rrd, COMMENT:Avg\\:);
+ push (@rrd, COMMENT:Max\\: \\j);
$global_headers++;
}
@@ -924,13 +924,13 @@
}
else
{
- push (@rrd, COMMENT: Cur:) unless $global_headers;
+ push (@rrd, COMMENT:Cur\\:) unless $global_headers;
push (@rrd, GPRINT:c$rrdname:LAST:%6.2lf . (munin_get_bool_val
($node-{client}-{$service}-{graph_scale}, yes)?%s:) . );
- push (@rrd, COMMENT: Min:) unless $global_headers;
+ push (@rrd, COMMENT:Min\\:) unless $global_headers;
push (@rrd, GPRINT:i$rrdname:MIN:%6.2lf . (munin_get_bool_val
($node-{client}-{$service}-{graph_scale}, 1)?%s:) . );
- push (@rrd, COMMENT: Avg:) unless $global_headers;
+ push (@rrd, COMMENT:Avg\\:) unless $global_headers;
push (@rrd, GPRINT:g$rrdname:AVERAGE:%6.2lf . (munin_get_bool_val
($node-{client}-{$service}-{graph_scale}, 1)?%s:) . );
- push (@rrd, COMMENT: Max:) unless $global_headers;
+ push (@rrd, COMMENT:Max\\:) unless $global_headers;
push (@rrd, GPRINT:a$rrdname:MAX:%6.2lf . (munin_get_bool_val
($node-{client}-{$service}-{graph_scale}, 1)?%s:) . \\j);
push (@{$total_pos{'min'}}, i$rrdname);
push (@{$total_pos{'avg'}}, g$rrdname);
@@ -991,26 +991,30 @@
push (@rrd, CDEF:dpostotal=ipostotal,UN,ipostotal,UNKN,IF);
push (@rrd, LINE1:dpostotal#00: . $node-{client}-{$service}-{graph_total} .
( x ($max_field_len - length ($node-{client}-{$service}-{graph_total}) + 1)));
- push (@rrd, COMMENT: Cur:) unless $global_headers;
+ push (@rrd, COMMENT:Cur\\:) unless $global_headers;
push (@rrd, GPRINT:gpostotal:LAST:%6.2lf . (munin_get_bool_val
($node-{client}-{$service}-{graph_scale}, 1)?%s:) . );
- push (@rrd, COMMENT: Min:) unless $global_headers;
+ push (@rrd, COMMENT:Min\\:) unless $global_headers;
push (@rrd, GPRINT:ipostotal:MIN:%6.2lf . (munin_get_bool_val
($node-{client}-{$service}-{graph_scale}, 1)?%s:) . );
- push (@rrd, COMMENT: Avg:) unless $global_headers;
+ push (@rrd, COMMENT:Avg\\:) unless $global_headers;
push (@rrd, GPRINT:gpostotal:AVERAGE:%6.2lf . (munin_get_bool_val
($node-{client}-{$service}-{graph_scale}, 1)?%s:) . );
- push (@rrd, COMMENT: Max:) unless $global_headers;
+ push (@rrd, COMMENT:Max\\:) unless $global_headers;
push (@rrd, GPRINT:apostotal:MAX:%6.2lf . (munin_get_bool_val
($node-{client}-{$service}-{graph_scale}, 1)?%s:) . \\j);
}
for my $time (keys %times) {
next unless ($draw{$time});
my @complete;
+my $fixtime;
logger (Processing $name - $time) if $DEBUG;
# Do the header (title, vtitle, size, etc...)
push @complete, @{get_header ($node, $config, $domain, $name,
$service, $time)};
push @complete, @rrd;
- push (@complete, COMMENT:Last update: . localtime($lastupdate) .
\\r);
+$fixtime = localtime($lastupdate);
+$fixtime =~ s/\:/\\:/g;
+
+ push (@complete, COMMENT:Last update\\: . $fixtime . \\r);
if (time - 300 $lastupdate)
{
@@ -1033,6 +1037,7 @@
{
next unless ($draw{sum.$time});
my @rrd_sum;
+my $fixtime;
push @rrd_sum, @{get_header ($node, $config, $domain, $name,
$service, $time, 1)};
if (time - 300 $lastupdate)
@@ -1040,7 +1045,11 @@
push @rrd_sum,
--end,(int($lastupdate/$resolutions{$time}))*$resolutions{$time};
}
push @rrd_sum, @rrd;
- push (@rrd_sum, COMMENT:Last update: . localtime($lastupdate) .
\\r);
+
+$fixtime = localtime($lastupdate);
+$fixtime =~ s/\:/\\:/g;
+
+ push (@rrd_sum, COMMENT:Last update\\: . $fixtime . \\r);
my $labelled = 0;
my @defined = ();
--
Thomas Lakofski +44 70 9228 8229
'Reality is that which, when you stop believing in it, doesn't go away' --PKD
gpg: 1024D/81FD4B43 2B72 53DB 8104 2041 BDB4 F053 4AE5 01DF 81FD 4B43
--
To UNSUBSCRIBE, email to [EMAIL
