Whether it is possible to fix this problem in the stable version?
FILTER[ not vlan ] --> FILTER[ vlan ] == not empty (Why?)
FILTER[ ip ] --> FILTER[ vlan ] == not empty (Why?)
FILTER[ ether[12:2]=0x800 ] --> FILTER[ vlan ] == not empty (Why?)
tcpdump -p -i eth0 not vlan -w - | tcpdump
Package: tcpdump
Version: 4.1.1-1
Severity: important
"tcpdump -i bond0 ip"
and
"tcpdump -i bond0 not vlan"
captures non-ip (vlan) packets...
# tcpdump -i bond0 -c 1 -w test-dump-ip ip
tcpdump: listening on bond0, link-type EN10MB (Ethernet), capt
Small problem...
$ apt-cache policy lvm2
lvm2:
Installed: 2.02.39-8
Candidate: 2.02.39-8
Version table:
*** 2.02.39-8 0
500 http://ftp.debian.org lenny/main Packages
500 http://security.debian.org lenny/updates/main Packages
100 /var/lib/dpkg/status
2010/12/6 Alas
2010/12/5 Andrew Shirrayev
> At first time i move 300Gb mail storage to new disk, and lost all data. :-(
> Transfer complite at 300Gb/sec speed...
>
> Kernel logs:
>
> omega:~# ls -l /dev/mapper/ | grep move
> omega:~# dmesg | tail -2
> [11762.790363] drbd5: pe
At first time i move 300Gb mail storage to new disk, and lost all data. :-(
Transfer complite at 300Gb/sec speed...
Kernel logs:
omega:~# ls -l /dev/mapper/ | grep move
omega:~# dmesg | tail -2
[11762.790363] drbd5: peer( Secondary -> Primary )
[11764.552933] drbd2: peer( Secondary -> Primary )
o
Package: courier-ssl
Version: 0.53.3-5
Severity: important
1) connect to server over imap-ssl
2) login
3) start search or other hard work task with delayed response
4) drop connection...
5) repeat from 1
After each breakage of connection starttls comes to the end and
cause SIGCHLD. couriertcpd, p
Adding correct HTTPProxyServer & HTTPProxyPort solve this problem.
w/o proxy (timeout):
==
$ strace /usr/bin/freshclam
fcntl64(5, F_GETFL) = 0x2 (flags O_RDWR)
fcntl64(5, F_SETFL, O_RDWR|O_NONBLOCK) = 0
gettimeofday({1208970842,
Package: mhonarc
Version: 2.6.10-1
Severity: normal
*** Please type your report below this line ***
Mbox (echo =?us-ascii?B?`echo -n "base64 subj"|base64-encode`?=)
--
.
Subject: =?us-ascii?B?YmFzZTY0IHN1Ymo=?=
.
--
RC-file
---
On Fri, 7 Oct 2005, Jeff Breidenbach wrote:
> Is the fundamental problem in perl, mhonarc, or both?
>
fundamental problem in perl:
s{...}{...;;}g operation on 10Mb string require about 1Gb memory.
fundamental problem in mhonarc:
using perl... :-)
Perl operation don't regulate memory usage
Package: mhonarc
Version: 2.6.10-1
Severity: normal
*** Please type your report below this line ***
On my system (512Mb RAM & 1300Mb swap) mhonarc fail
with "out of memory" error. Mailbox size for processing
approximately 30Mb.
Huge memory need for "s{}{}" operator at /usr/share/mhonarc/MHonAr
Package: perl-debug
Version: 5.8.4-8
Severity: normal
*** Please type your report below this line ***
Get "usemymalloc" from Config.
$debugperl -MConfig -le 'print "usemymalloc is ".$Config::Config{usemymalloc}'
usemymalloc is n
Review debian perl source:
$ grep -A6 debugperl perl-5.8.4/debian
Package: perl
Version: 5.8.4-8
Severity: normal
*** Please type your report below this line ***
Small perl program for demonstration problem:
my $nop;
print "1st:",`grep ^VmSize /proc/$$/status`;
my $s="A" x 500;
print "2nd:",`grep ^VmSize /proc/$$/status`;
$s =~s{(.)}{$1}gxe
Package: perl
Version: 5.8.4-8
Severity: normal
*** Please type your report below this line ***
Small perl program:
$a="AAA\n";
$b=$a x 100;
print "Length = ".length($b)."\n";
system("top -b -n 1 |grep \" *$$ \"");
$b=$a x 10
13 matches
Mail list logo
