[26519] in Perl-Users-Digest

home help back first fref pref prev next nref lref last post

Perl-Users Digest, Issue: 8670 Volume: 10

daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Nov 15 21:05:14 2005

Date: Tue, 15 Nov 2005 18:05:04 -0800 (PST)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)

Perl-Users Digest           Tue, 15 Nov 2005     Volume: 10 Number: 8670

Today's topics:
        "Killed" Message On Linux (Running From BASH) <hal@thresholddigital.com>
    Re: "Killed" Message On Linux (Running From BASH) <1o4ibj70m3vooae@jetable.org>
    Re: Grouping like items together <dillon@SpamMinuSaccessdenied.darktech.org>
    Re: LOESS (aka LOWESS) <1usa@llenroc.ude.invalid>
        Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)

----------------------------------------------------------------------

Date: Tue, 15 Nov 2005 20:41:20 -0500
From: Hal Vaughan <hal@thresholddigital.com>
Subject: "Killed" Message On Linux (Running From BASH)
Message-Id: <DMCdnQTIHO-jE-fenZ2dnUVZ_sGdnZ2d@comcast.com>

I've tried Googling this and get a high noise-to-signal ratio.

I'm running Perl scripts on Linux (Debian, Sarge), from the command line (in
bash), and I get a "Killed" message.  I can't find enough to verify this is
coming from Perl or bash or where.  Sometimes the program runs fine,
sometimes it doesn't.  When I run it with one data file that didn't work
before, it runs just fine the 2nd time.  The only module I'm using that
isn't mine is Term::VT102, and I've grep'ed and found NO occurance of the
word "Killed".

I'm used to getting crashes that tell me the line numbers and errors, but
not just a simple "Killed."

At the least, I'd like to know what is issuing this "Killed" message (is
this what happens when another program kills a Perl script?), or what could
be causing this.

Thanks for any help!

Hal


------------------------------

Date: Tue, 15 Nov 2005 19:58:02 -0600
From: Lars Kellogg-Stedman <1o4ibj70m3vooae@jetable.org>
Subject: Re: "Killed" Message On Linux (Running From BASH)
Message-Id: <t1132105717.p3351.r22151173.lars@jetable.org>

> At the least, I'd like to know what is issuing this "Killed" message (is
> this what happens when another program kills a Perl script?), or what could
> be causing this.

Some shells (e.g., bash) print this message if a process dies due to
receiving a SIGKILL.  Try this:

  In xterm 1, run:

    sleep 30

  In xterm 2, run:

    killall -9 sleep

You'll probably see the message "Killed" in xterm 1.  I'm not sure what
would be causing this -- it is unlikely that something is sending
spontaneous KILL signals to your processes, unless (a) you're running
extremely low on memory and (b) the Linux OOM killer kills processes in
this fashion.

-- Lars

-- 
Lars Kellogg-Stedman <1o4ibj70m3vooae@jetable.org>
This email address will expire on 2005-11-22.



------------------------------

Date: Wed, 16 Nov 2005 10:01:07 +0800
From: AcCeSsDeNiEd <dillon@SpamMinuSaccessdenied.darktech.org>
Subject: Re: Grouping like items together
Message-Id: <t54ln1lkbs530rt8a6t003ad14ib9qk9sr@4ax.com>

On Tue, 15 Nov 2005 08:48:14 -0600, Tad McClellan <tadmc@augustmail.com> wrote:

Well, I've just given up doing this programmatically.
I've taken a closer look at the naming conventions.
One method I thought off was to split the name from the numbers.
But I've come across files that do not have numbers just after the client's name.
The client name always comes on the left of the filename, but the rest of the filename is just too
'gibberish'.

Not gonna happen. At least not until computers are capable of AI.

Thx for the help anyways.

My coy will just have to hire temp staff to clean up this mess.

Btw, we have 400k files.
So good luck on the manual process.

To e-mail, remove the obvious


------------------------------

Date: Tue, 15 Nov 2005 23:19:24 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: LOESS (aka LOWESS)
Message-Id: <Xns970FBA65EE57Basu1cornelledu@127.0.0.1>

"Mr. No Address" <no_given_address@landofthelost.net> wrote in news:dldq1l$tkt$1@news.nems.noaa.gov:

> Been some time since I was here and now I'm almost fearful to post. 
> Have I googled enough?  Have I searched CPAN enough?  Did I read all the 
> books?  Have I done everything reasonable to try and answer my question 
> before posting here?  Ah, what the hell...

Interesting attitude.

> Locally Weighted Robust Regression (LOWESS or LOESS).  Boss says it's 
> the thing to use for a particular job that needs to be done.  Is there a 
> Perl module out there that does this?

I am not sure why one would use Perl for this task. There is a regression 
module which I have used in the past, and could be used to compute the 
local weighted regressions at each point.

http://www.mathworks.com/access/helpdesk/help/toolbox/curvefit/ch_data7.html
http://www.itl.nist.gov/div898/handbook/pmd/section1/pmd144.htm

I would be much more inclined to use a numeric computation package for 
this, say, S-Plus (or R), MatLab (or Octave), Mathematica, Gauss, SAS, or 
even use some Fortran code from netlib:

See also:

http://cm.bell-labs.com/cm/ms/departments/sia/wsc/smoothsoft.html

Sinan
-- 
A. Sinan Unur <1usa@llenroc.ude.invalid>
(reverse each component and remove .invalid for email address)

comp.lang.perl.misc guidelines on the WWW:
http://mail.augustmail.com/~tadmc/clpmisc/clpmisc_guidelines.html



------------------------------

Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin) 
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>


Administrivia:

#The Perl-Users Digest is a retransmission of the USENET newsgroup
#comp.lang.perl.misc.  For subscription or unsubscription requests, send
#the single line:
#
#	subscribe perl-users
#or:
#	unsubscribe perl-users
#
#to almanac@ruby.oce.orst.edu.  

NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice. 

To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.

#To request back copies (available for a week or so), send your request
#to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
#where x is the volume number and y is the issue number.

#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.


------------------------------
End of Perl-Users Digest V10 Issue 8670
***************************************


home help back first fref pref prev next nref lref last post