On Wed, Aug 26, 2009 at 7:11 AM, Bill Moran wrote:
> Adam Vande More wrote:
> >
> > On Tue, Aug 25, 2009 at 2:43 PM, Bill Moran >wrote:
> >
> > > In response to Adam Vande More :
> > >
> > > > On Tue, Aug 25, 2009 at 12:06 PM, Bill Moran <
> wmo...@potentialtech.com
> > > >wrote:
> > > >
> > > >
Adam Vande More wrote:
>
> On Tue, Aug 25, 2009 at 2:43 PM, Bill Moran wrote:
>
> > In response to Adam Vande More :
> >
> > > On Tue, Aug 25, 2009 at 12:06 PM, Bill Moran > >wrote:
> > >
> > > > In response to Adam Vande More :
> > > >
> > > > > On Tue, Aug 25, 2009 at 11:05 AM, Bill Moran <
>
ed
.bash/ Contents here:
http://silenceisdefeat.com/~cbrace/www_badstuff-3.gz
Sorry about the multiple tarballs.
-
Colin Brace
Amsterdam
http://lim.nl
--
View this message in context:
http://www.nabble.com/what-www-perl-script-is-running--tp25112050p25149559.html
Sent from the freebsd-que
y directory.
Oops, I missed six more files written by www to /tmp. Here they are:
http://silenceisdefeat.com/~cbrace/www_badstuff-2.gz
-
Colin Brace
Amsterdam
http://lim.nl
--
View this message in context:
http://www.nabble.com/what-www-perl-script-is-running--tp25112050
Steve Bertrand said the following on 08/26/2009 01:33 AM:
In this case, OP, look for:
- directories named as such:
-- ...
-- . ..
-- . .
-- etc, particularly under:
-- /var/tmp
-- /tmp
-- or anywhere else the [gu]id of the webserver could possibly write to
Thanks for the comments, Steve.
src/usr.sbin/cron/crontab/crontab.c,v 1.24
> 2006/09/03 17:52:19 ru Exp $)
> */1 * * * * perl /tmp/tmpfile
>
> I removed it, so now at least the script stops relaunching.
>
> /tmp/tmpfile is of course the script.
>
> In a subdirectory of tmp, there is a whole bunch of source co
mised in the past (several times), and
experience based on having an installed Perl-based httpd program tells
me thus:
- it is likely a PHP script that was the root cause
- it is likely that the script had access to a MySQL database
- bulletin boards, mailer apps and blog software was often the cu
sage in context:
http://www.nabble.com/what-www-perl-script-is-running--tp25112050p25143778.html
Sent from the freebsd-questions mailing list archive at Nabble.com.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
On Tue, Aug 25, 2009 at 2:43 PM, Bill Moran wrote:
> In response to Adam Vande More :
>
> > On Tue, Aug 25, 2009 at 12:06 PM, Bill Moran >wrote:
> >
> > > In response to Adam Vande More :
> > >
> > > > On Tue, Aug 25, 2009 at 11:05 AM, Bill Moran <
> wmo...@potentialtech.com
> > > >wrote:
> > > >
In response to Adam Vande More :
> On Tue, Aug 25, 2009 at 12:06 PM, Bill Moran wrote:
>
> > In response to Adam Vande More :
> >
> > > On Tue, Aug 25, 2009 at 11:05 AM, Bill Moran > >wrote:
> > >
> > > > In response to Paul Schmehl :
> > > >
> > > > > --On Tuesday, August 25, 2009 08:30:17 -050
On Tue, Aug 25, 2009 at 12:06 PM, Bill Moran wrote:
> In response to Adam Vande More :
>
> > On Tue, Aug 25, 2009 at 11:05 AM, Bill Moran >wrote:
> >
> > > In response to Paul Schmehl :
> > >
> > > > --On Tuesday, August 25, 2009 08:30:17 -0500 Colin Brace
> > > wrote:
> > > >
> > > > > Bill Mor
ster and reinstall.
> # (cron.job installed on Tue Jul 28 23:49:28 2009)
> # (Cron version -- $FreeBSD: src/usr.sbin/cron/crontab/crontab.c,v 1.24
> 2006/09/03 17:52:19 ru Exp $)
> */1 * * * * perl /tmp/tmpfile
>
> I removed it, so now at least the script stops relaunching.
>
>
In response to Adam Vande More :
> On Tue, Aug 25, 2009 at 11:05 AM, Bill Moran wrote:
>
> > In response to Paul Schmehl :
> >
> > > --On Tuesday, August 25, 2009 08:30:17 -0500 Colin Brace
> > wrote:
> > >
> > > > Bill Moran wrote:
> > > >>
> > > >> You can add an ipfw rule to prevent the scrip
On Tue, Aug 25, 2009 at 11:05 AM, Bill Moran wrote:
> In response to Paul Schmehl :
>
> > --On Tuesday, August 25, 2009 08:30:17 -0500 Colin Brace
> wrote:
> >
> > > Bill Moran wrote:
> > >>
> > >> You can add an ipfw rule to prevent the script from calling home,
> which
> > >> will effectively r
In response to Paul Schmehl :
> --On Tuesday, August 25, 2009 08:30:17 -0500 Colin Brace wrote:
>
> > Bill Moran wrote:
> >>
> >> You can add an ipfw rule to prevent the script from calling home, which
> >> will effectively render it neutered until you can track down and actually
> >> _fix_ the
In response to Paul Schmehl :
> --On Tuesday, August 25, 2009 07:26:04 -0500 Bill Moran
> wrote:
> >>
> >> I am currently killing the process with the following bash command while I
> >> decide what to do next:
> >>
> >> $ while x=1 ; do sudo killall -9 perl5.8.9 && echo "killed..." ; sleep 15;
--On Tuesday, August 25, 2009 08:30:17 -0500 Colin Brace wrote:
Bill, one more thing:
Bill Moran wrote:
You can add an ipfw rule to prevent the script from calling home, which
will effectively render it neutered until you can track down and actually
_fix_ the problem.
Mike Bristow above
--On Tuesday, August 25, 2009 05:46:43 -0500 Colin Brace wrote:
Olivier Nicole wrote:
Am I correct in assuming that my system has been hacked and I am running
an
IRC server or something?
IRC client at least. And yes, I would think that your system has been
compromised.
Thanks Olivier
eBSD: src/usr.sbin/cron/crontab/crontab.c,v 1.24
2006/09/03 17:52:19 ru Exp $)
*/1 * * * * perl /tmp/tmpfile
I removed it, so now at least the script stops relaunching.
/tmp/tmpfile is of course the script.
In a subdirectory of tmp, there is a whole bunch of source code, all owned
by 'www'
--On Tuesday, August 25, 2009 04:41:33 -0500 Ruben de Groot
wrote:
On Tue, Aug 25, 2009 at 10:19:37AM +0100, Mike Bristow typed:
On Tue, Aug 25, 2009 at 01:00:53AM -0700, Colin Brace wrote:
> Ok, here is what lsof tells me:
>
> $ sudo lsof | grep perl
> perl5.8.9 4272 www
Ruben de Groot wrote:
>
> Which is exactly what the rogue perl script was using to connect to it's
> "home".
> Once established this connection could have been used for allmost
> anything,
> including downloading other malicious software or setting up a tunnel i
--On Tuesday, August 25, 2009 07:26:04 -0500 Bill Moran
wrote:
I am currently killing the process with the following bash command while I
decide what to do next:
$ while x=1 ; do sudo killall -9 perl5.8.9 && echo "killed..." ; sleep 15;
done
You can add an ipfw rule to prevent the script fr
n gif0 inet6 proto icmp6
> block in log
>
> That is to say: nothing is allowed in unless explicitly allowed
> Everything allowed out.
Which is exactly what the rogue perl script was using to connect to it's "home".
Once established this connection could have been us
hrough one of the above ports?
That's certainly possibly. But not my first guess.
> Any suggestions as to where to start looking for the breach would be most
> welcome; I am quite new to this game.
My guess (not much more than that) is that someone used a vulnerable web page,
maybe some p
hat is to say: nothing is allowed in unless explicitly allowed
Everything allowed out.
(plus some ipv6 stuff I was testing with a tunnel)
Merci
-
Colin Brace
Amsterdam
http://lim.nl
--
View this message in context:
http://www.nabble.com/what-www-perl-script-is-running--tp25112050p2
rough one of the above ports?
Any suggestions as to where to start looking for the breach would be most
welcome; I am quite new to this game.
Thanks.
-
Colin Brace
Amsterdam
http://lim.nl
--
View this message in context:
http://www.nabble.com/what-www-perl-script-is-running--tp25112050p2
In response to Colin Brace :
>
> Olivier Nicole wrote:
> >
> >> Am I correct in assuming that my system has been hacked and I am running
> >> an
> >> IRC server or something?
> >
> > IRC client at least. And yes, I would think that your system has been
> > compromised.
> >
>
> Thanks Olivier.
Colin,
> I suppose this calls for a "bare-metal" reinstall.
> Is it worth first trying to determine how my system was broken into?
It really depends on:
- what is installed on that machine (how long it would take to
reinstall, how many softwares, ports, specially configured stuff).
- how impo
m was broken into?
-
Colin Brace
Amsterdam
http://lim.nl
--
View this message in context:
http://www.nabble.com/what-www-perl-script-is-running--tp25112050p25132123.html
Sent from the freebsd-questions mailing list archive at Nabble.com.
__
Hi Colin,
> Am I correct in assuming that my system has been hacked and I am running an
> IRC server or something?
IRC client at least. And yes, I would think that your system has been
compromised.
Good luck,
Olivier
___
freebsd-questions@freebsd.org
Mike Bristow wrote:
>
> On Tue, Aug 25, 2009 at 01:00:53AM -0700, Colin Brace wrote:
>> Ok, here is what lsof tells me:
>>
>> $ sudo lsof | grep perl
>> perl5.8.9 4272 www3uIPv4 0xc33cf0000t0 TCP
>> gw:51295->94.102.51.57:afs3-f
On Tue, Aug 25, 2009 at 10:19:37AM +0100, Mike Bristow typed:
> On Tue, Aug 25, 2009 at 01:00:53AM -0700, Colin Brace wrote:
> > Ok, here is what lsof tells me:
> >
> > $ sudo lsof | grep perl
> > perl5.8.9 4272 www3uIPv4 0xc33cf0000t0 TCP
>
On Tue, Aug 25, 2009 at 01:00:53AM -0700, Colin Brace wrote:
> Ok, here is what lsof tells me:
>
> $ sudo lsof | grep perl
> perl5.8.9 4272 www3uIPv4 0xc33cf0000t0 TCP
> gw:51295->94.102.51.57:afs3-fileserver (ESTABLISHED)
>
> The last line would
Ok, here is what lsof tells me:
$ sudo lsof | grep perl
perl5.8.9 4272 www cwd VDIR 0,76512 2 /
perl5.8.9 4272 www rtd VDIR 0,76512 2 /
perl5.8.9 4272 www txt VREG 0,82 4428 3015044
/usr/local/bin/perl
perl5.8.9
On Monday 24 August 2009 10:07:50 Olivier Nicole wrote:
> > Is there a command like fuser or lsof which can be used to determine
> > what files this perl instance is using? Any other ideas on how to figure
> > out what is going on here?
>
> lsof is in the ports.
>
> Is there a command like fuser or lsof which can be used to determine
> what files this perl instance is using? Any other ideas on how to figure
> out what is going on here?
lsof is in the ports.
best regards,
Olivier
___
freebsd-
Hi all,
I noticed this morning that a perl script was using a lot of CPU time on
my FreeBSD webserver. By the time I killed it, it had run up 400 mins of
system time according to top.
However, simply killing 'perl5.8.9' didn't accomplish much, it was back
running again moment
Steve Bertrand wrote:
> Hey all,
>
> I've been migrating all of my projects from CVS to SVN (starting over
> from the beginning).
>
> All of the projects in question are Perl modules.
[..snip..]
> Any guidance to fix the version numbering (especially to fix the FreeBS
> differently -- svn keeping a repository wide version and cvs keeping a
> version
> per file. Consult the svn documentation on how to embed the version number
> into the file -- once that is working, producing a perl one-liner to
> initialise
> $VERSION will be pretty easy.
>
wrong, and it is entirely possible that the revision numbers will behave
differently -- svn keeping a repository wide version and cvs keeping a version
per file. Consult the svn documentation on how to embed the version number
into the file -- once that is working, producing a perl one-liner to
Jason Helfman wrote:
> Have you heard of cvs2svn? I am not sure if this could be a good candidate
> for your migration, or not, but we used it successfully at a company I used
> to work for.
>
> http://cvs2svn.tigris.org/
Thanks Jason, but it's too late for that.
Essentially, I rm'd the CVS dire
Hey all,
I've been migrating all of my projects from CVS to SVN (starting over
from the beginning).
All of the projects in question are Perl modules.
Can someone give me a tip on what I have to do in order to prevent the
following when I do a ``make install''?:
FreeB
Hi Jerry,
Jerry wrote:
Perl-5.10 was released to the public over a year ago. Another year
transpired before it was released into the ports system. There was an
immediate problem that was corrected when the maintainer switched to
'bison' from 'YACC'. Other than that, it has
On Tue, May 12, 2009 at 11:05 AM, Tsu-Fan Cheng wrote:
> I have two arrays, each has two columns (so its A1, B1 and A2, B2). As
> are the positions while Bs are the values. I need to get the ratio
> between B1 and B2 if their As are the same or close to each other
> within a certain distance.
Wel
same or close to each other
within a certain distance. This sounds pretty straight forward but I
am not an experienced programmer. Can anybody show me how to do it by
perl? thank you!!
TFC
___
freebsd-questions@freebsd.org mailing list
http
On Sat, 9 May 2009 08:31:45 -0500 (CDT)
Lars Eighner wrote:
>On Sat, 9 May 2009, Jos Chrispijn wrote:
>
>> Lars Eighner wrote:
>>> On Sat, 9 May 2009, Jos Chrispijn wrote:
>>>
>>> You must be new around here.
>> Yes, I am L-)
>>> The proce
Lars Eighner wrote:
On Sat, 9 May 2009, Matthew Seaman wrote:
I concur. If you do the pkg_info thing and the list of stuff
depending on
perl is very short, by all means upgrade before it gets long.
After having some investigation on this subject, it comes clear to me
that Perl is a very
On Sat, 9 May 2009, Matthew Seaman wrote:
However, I expect the consensus on the minimum supported version to change
over time and more use to be made of 5.10 specific features, so I'd certainly
recommend installing brand new machines with perl-5.10 in order to minimize
the potential for f
On Sat, 9 May 2009, Jos Chrispijn wrote:
Lars Eighner wrote:
On Sat, 9 May 2009, Jos Chrispijn wrote:
You must be new around here.
Yes, I am L-)
The process described in UPDATING for upgrading to Perl 5.10 is relatively
painless compared to previous perl upgrades. So much stuff depends
Jos Chrispijn wrote:
Lars Eighner wrote:
On Sat, 9 May 2009, Jos Chrispijn wrote:
The process described in UPDATING for upgrading to Perl 5.10 is
relatively
painless compared to previous perl upgrades. So much stuff depends upon
perl that:
Do you recommend having Perl updated or should
Lars Eighner wrote:
On Sat, 9 May 2009, Jos Chrispijn wrote:
You must be new around here.
Yes, I am L-)
The process described in UPDATING for upgrading to Perl 5.10 is
relatively
painless compared to previous perl upgrades. So much stuff depends upon
perl that:
[snip]
Do you recommend
On Sat, 9 May 2009, Jos Chrispijn wrote:
Not that I am that paranoid, but can someone tell me why Perl 5.8 is not
automatically updated to 5.10 thru the ports, but (accordingly by UPDATING)
has to be updated by some manual interaction?
You must be new around here.
The process described in
On Sat, 09 May 2009 13:05:32 +0200
Jos Chrispijn wrote:
> Not that I am that paranoid, but can someone tell me why Perl 5.8 is
> not automatically updated to 5.10 thru the ports, but (accordingly by
> UPDATING) has to be updated by some manual interaction?
That's the way the por
Not that I am that paranoid, but can someone tell me why Perl 5.8 is not
automatically updated to 5.10 thru the ports, but (accordingly by
UPDATING) has to be updated by some manual interaction?
--
Jos Chrispijn
___
freebsd-questions@freebsd.org
Tsu-Fan Cheng wrote:
Hi,
I guess this is not a REAL freebsd problem, but I am running a perl
script on freebsd7.0/perl 5.10 system. This script failed with
"segmentation fault" at different stages with different input files,
and sometimes the script actually finishes and gives the
Hi,
I guess this is not a REAL freebsd problem, but I am running a perl
script on freebsd7.0/perl 5.10 system. This script failed with
"segmentation fault" at different stages with different input files,
and sometimes the script actually finishes and gives the reasonable
output. So
; > Can anyone tell me how to fix this one:
> > > >
> > > > Stale dependency: bsdpan-Pod-Perldoc-3.15 -> perl-5.8.9_2
> > > > (lang/perl5.8): can't convert nil into string
> > > >
> > > >
> > > > My update to 10 see
On Sun, Apr 12, 2009 at 12:05:50PM -0700, David Southwell typed:
> On Saturday 11 April 2009 17:20:56 Chris Rees wrote:
> > > I hope it is not too far off topic but:
> > >
> > > Can anyone tell me how to fix this one:
> > >
> > > Stale dependenc
--On April 12, 2009 2:05:50 PM -0500 David Southwell
wrote:
>
> I hope it is not too far off topic but:
It is, so note the change of subject
>
> Can anyone tell me how to fix this one:
>
> Stale dependency: bsdpan-Pod-Perldoc-3.15 -> perl-5.8.9_2
> (lang/perl5.8)
> wrote:
> >> >> According to /usr/ports/UPDATING, if you want to upgrade to perl5.10,
> >> >> you do
> >> >> the following:
> >> >>
> >> >> Portupgrade users:
> >> >> 0) Fix pkgdb.db (for
de to perl5.10,
>> >> you do
>> >> the following:
>> >>
>> >> Portupgrade users:
>> >> 0) Fix pkgdb.db (for safety):
>> >> pkgdb -Ff
>> >>
>> >> 1) Reinstall perl with new 5.10:
>> &
Your mail to 'Perl-XML' with the subject
Returned mail: Data format error
Is being held until the list moderator can review it for approval.
The reason it is being held:
Post by non-member to a members-only list
Either the message will get posted to the list, or you wi
Leslie Jensen wrote:
Hello list.
When one updates perl, one should rebuild all ports dependend on perl
according to the UPDATING file.
I'm just wondering, isn't the script "perl-after-upgrade" supposed to do
the work needed, so that one can save the time of upgrading the
Hello list.
When one updates perl, one should rebuild all ports dependend on perl
according to the UPDATING file.
I'm just wondering, isn't the script "perl-after-upgrade" supposed to do
the work needed, so that one can save the time of upgrading the ports
:portmaster -r perl\*
===>>> No ORIGIN in /var/db/pkg/perl-5.10.0_1/+CONTENTS:@comment
ORIGIN:lang/per
l5.10 /var/db/pkg/perltidy-20071205/+CONTENTS:@comment
ORIGIN:devel/perltidy/+CO
NTENTS
===>>> Aborting update
I've been looking in the +CONTENTS files for
I updated Perl and it went ok. But when I want to rebuild the ports
depending on perl I get the error below.
portmaster -o lang/perl5.10 lang/perl5.8
===> Cleaning for perl-5.10.0_1
===>>> Updating package dependency entry for each dependent port
===>>> Delete perl
I've had good luck using tha cpan script to add perl moduals
"cpan XML::Parser" will add it and the needed moduals
check man cpan
--- On Mon, 3/30/09, af300...@gmail.com wrote:
> From: af300...@gmail.com
> Subject: Re: Re: Where is the Perl XML::Parser port
> To:
On Mar 29, 2009 4:21pm, "Paul B. Mahol" wrote:
On 3/29/09, af300...@gmail.com af300...@gmail.com> wrote:
> Hi,
>
> I'm installing the latest gimp and get to a point in the install where
it
> says:
>
> checking for perl... /usr/bi
On Sun, 29 Mar 2009 22:07:42 +, af300...@gmail.com wrote:
awgc> So, I've done some searches at freshports.org and I cannot find the
awgc> XML::Parser perl module anywhere in the ports tree. What is it under?
/usr/ports/textproc/p5-XML-Parser/
--
Anton
On 3/29/09, af300...@gmail.com wrote:
> Hi,
>
> I'm installing the latest gimp and get to a point in the install where it
> says:
>
> checking for perl... /usr/bin/perl
> checking for XML::Parser... configure: error: XML::Parser perl module is
> required for intl
Hi,
I'm installing the latest gimp and get to a point in the install where it
says:
checking for perl... /usr/bin/perl
checking for XML::Parser... configure: error: XML::Parser perl module is
required for intltool
So, I've done some searches at freshports.org and I cannot find
On Fri, March 27, 2009 19:59, Tobias Rehbein wrote:
> Am Thu, Mar 26, 2009 at 10:11:28PM + schrieb Bruce Cran:
>>
> Hm. Tried this and got ineresting results:
>
>> use POSIX;
>> sysopen(CD,"/dev/cd0", O_RDONLY|O_NONBLOCK) || perror("sysopen")
> works fine, but
>> use POSIX;
>> sysopen(CD,"/dev/
Am Fri, Mar 27, 2009 at 09:19:53PM +0100 schrieb Joost Bekkers:
> On Fri, March 27, 2009 19:59, Tobias Rehbein wrote:
> > Am Thu, Mar 26, 2009 at 10:11:28PM + schrieb Bruce Cran:
> >>
> > Hm. Tried this and got ineresting results:
> >
> >> use POSIX;
> >> sysopen(CD,"/dev/cd0", O_RDONLY|O_NONBL
device nodes created
> with and without atapicam, has checked he has permission to access the
> appropriate device and has come across a problem with perl itself.
You are right. Normally I use atapicam and let devfs hide /dev/acd0.
As I have written in another message in this thread sysopen ac
Bruce Cran wrote:
>cd0 is also what you get if you use atapicam (ATAPI is SCSI over ATA
>from what I remember) - for example cdrecord has traditionally used it
No, with CAM on FreeBSD /dev/xpt is opened and then the route to the device is
extablished via the SCSI address.
>when writing CDs. A
On Fri, 27 Mar 2009 10:44:07 +
Vincent Hoffman wrote:
> On 27/3/09 10:32, Mel Flynn wrote:
> > On Thursday 26 March 2009 22:20:45 Tobias Rehbein wrote:
> >
> >> Hi all.
> >>
> >> I have a perl script which seems to work fine under Linux but
>
Am Thu, Mar 26, 2009 at 10:11:28PM + schrieb Bruce Cran:
>
> sysopen certainly works on FreeBSD:
>
> > perl
> use POSIX;
> sysopen(CD,"/dev/acd0", O_RDONLY|O_NONBLOCK) || perror("sysopen")
>
> and before I fixed the permissions:
>
> &
On 27/3/09 10:32, Mel Flynn wrote:
> On Thursday 26 March 2009 22:20:45 Tobias Rehbein wrote:
>
>> Hi all.
>>
>> I have a perl script which seems to work fine under Linux but fails on
>> FreeBSD. The Problem is the line:
>>
>> sysopen(CD, &quo
On Thursday 26 March 2009 22:20:45 Tobias Rehbein wrote:
> Hi all.
>
> I have a perl script which seems to work fine under Linux but fails on
> FreeBSD. The Problem is the line:
>
> sysopen(CD, "/dev/cd0", O_RDONLY | O_NONBLOCK)
>
> After this li
On Thu, 26 Mar 2009 18:17:46 -0400
Robert Huff wrote:
>
> Glen Barber writes:
>
> > > I have a perl script which seems to work fine under Linux but
> > > fails on FreeBSD. The Problem is the line:
> > >
> > > sysopen(CD, "/dev/cd0
On Thu, 26 Mar 2009 22:20:45 +0100
Tobias Rehbein wrote:
> Hi all.
>
> I have a perl script which seems to work fine under Linux but fails
> on FreeBSD. The Problem is the line:
>
> sysopen(CD, "/dev/cd0", O_RDONLY | O_NONBLOCK)
>
> After this li
Glen Barber writes:
> > I have a perl script which seems to work fine under Linux but
> > fails on FreeBSD. The Problem is the line:
> >
> > sysopen(CD, "/dev/cd0", O_RDONLY | O_NONBLOCK)
> >
> > After this line the following evaluates
On Thu, Mar 26, 2009 at 5:20 PM, Tobias Rehbein wrote:
> Hi all.
>
> I have a perl script which seems to work fine under Linux but fails on
> FreeBSD.
> The Problem is the line:
>
> sysopen(CD, "/dev/cd0", O_RDONLY | O_NONBLOCK)
>
> After this
Hi all.
I have a perl script which seems to work fine under Linux but fails on FreeBSD.
The Problem is the line:
sysopen(CD, "/dev/cd0", O_RDONLY | O_NONBLOCK)
After this line the following evaluates to true:
$! eq "No such file or directory."
/dev/cd0 is r
>> On Mon, 02 Mar 2009 17:21:53 -0800,
>> Andrew Moran said:
A> Thank you for your suggestion. I'll try compiling Perl and it's
A> dependencies without using PERL_MALLOC.
I've had similar memory problems using Hyperestraier to index
collections ex
UIDTHR PRI NICE SIZERES STATE C TIME WCPU
COMMAND
1611 1030 1 680 15062M 818M CPU2 2 0:44 20.65%
perl5.8.9
At this point, have your cd to a partition large enough to hold a
few 100
megs, and type:
ktrace -p 1611
where 1611 is the PID of the perl pro
> >>> because
> >>> I don't fully understand what the 'correct' values for my setup are.
> >>
> >> Could you show kenv kern.maxdsiz and if unset limits -H -d? Looks
> >> like it's
> >> 32G on my 6.x amd64, in which case
oot/loader.conf
echo 'kern.defdsiz="4G"' >> /boot/loader.conf
Thank you for helping me. The earlier suggestion of toggling
Perl Malloc didn't work, nor did syncing sources and installing new
kernel and new world which is what I did lsat night.
As for kernel
x27; >> /boot/loader.conf
Thank you for helping me. The earlier suggestion of toggling Perl
Malloc didn't work, nor did syncing sources and installing new kernel
and new world which is what I did lsat night.
As for kernel settings, I don't have anything in my loader.conf
On Monday 02 March 2009 16:21:53 Andrew Moran wrote:
> > What's even weirder is that the process gets that far. Did you play
> > with
> > kern.maxdsiz loader tuneable?
> > If so, set it lower, so you can at least have the machine in a
> > usable state at
> > all times. 4G should be enough for any
On Mar 2, 2009, at 3:39 PM, Mel wrote:
This is hard to debug, but I'd first toggle the PERL_MALLOC option
in the
configuration dialog for the perl port. If this doesn't solve the
problem,
then you'd have to get a ktrace to get some indication of what is
allocating
the m
I thought maybe it had something to do with
> the fact that I was using multithreaded perl (which I wasn't before I
> jumped into 7.1/ZFS), but rebuilding perl (and all its' dependencies)
> without threads didn't help.
>
> I have 8GB of physical memory and 16GB of swa
Andrew Moran wrote:
[...]
> Has anyone heard of this? Or any pointers on what I can do to figure
> out what is causing it?
>
> Your advice is much appreciated.
As an alternative:
You could try mail/mimedefang. It calls spamassassin to evaluate an
e-mail but without having it running all th
that SpamAssassin seems to be periodically eating
up all my memory, causing the server to slow to a crawl until the
kernel kills the process and then I have enormous amounts of free
memory. Rinse, repeat. I thought maybe it had something to do with
the fact that I was using multithreaded
Valerio Daelli writes:
> is there anyone working on a port of perl5.10?
> I can only see ports of 5.8 and 5.6.
> I can make a port of 5.10, it seems to compile flawlessly on
> FreeBSD 7.
_Many_ ports depend on perl, and each must be tested (and
if broken hopefully fixed)
Hi
is there anyone working on a port of perl5.10?
I can only see ports of 5.8 and 5.6.
I can make a port of 5.10, it seems to compile flawlessly on FreeBSD 7.
Have a good day
Valerio
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.or
On 08/02/09 Matthew Seaman said:
> I'd wager that 'pkg_info -l p5-Module-Giving-You-Trouble' says everything
> is installed under ${LOCALBASE}/lib/perl5/site-perl/5.8.8 but that if you
> run 'perl -v' the number 5.8.9 is prominently displayed.
>
> Ple
Matthew Seaman wrote:
Michael P. Soulier wrote:
On 08/02/09 Glen Barber said:
Have you tried manually `make deinstall; make install'?
Yes, and the make install pulled in dependencies on other perl
modules that
resulted in the same error message that _they_ had to be reinstalled.
Foll
Michael P. Soulier wrote:
On 08/02/09 Glen Barber said:
Have you tried manually `make deinstall; make install'?
Yes, and the make install pulled in dependencies on other perl modules that
resulted in the same error message that _they_ had to be reinstalled.
Following those depende
On 08/02/09 Glen Barber said:
> Have you tried manually `make deinstall; make install'?
Yes, and the make install pulled in dependencies on other perl modules that
resulted in the same error message that _they_ had to be reinstalled.
Following those dependencies resulted in the same, a
301 - 400 of 1505 matches
Mail list logo
