[12330] in Perl-Users-Digest
Perl-Users Digest, Issue: 5930 Volume: 8
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Wed Jun 9 11:07:28 1999
Date: Wed, 9 Jun 99 08:00:14 -0700
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Wed, 9 Jun 1999 Volume: 8 Number: 5930
Today's topics:
Re: _Please_ improve localtime! (Bart Lateur)
ActivePerl Win98 CGI Problem the1bob@my-deja.com
Re: Binary File Uploading - Part 2 (I.J. Garlick)
Re: fork for DNS lookup - help <gellyfish@gellyfish.com>
Re: fork for DNS lookup - help (Malcolm Ray)
Re: Get Date in Perl <jeromeo@atrieva.com>
How to reopen STDOUT once closed nblew@my-deja.com
Re: How to reopen STDOUT once closed (Randal L. Schwartz)
Re: Perl on win32 <camerond@mail.uca.edu>
perlcc compiling problems <gulli@ideare.com>
Re: Problems sorting. I'm stupid and I'll die (Larry Rosler)
Telnet monitor <kjcox@vii.com>
Re: Why does $blabla = <STDIN> not work in VMS Perl 5? <droby@copyright.com>
Special: Digest Administrivia (Last modified: 12 Dec 98 (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Wed, 09 Jun 1999 14:53:19 GMT
From: bart.lateur@skynet.be (Bart Lateur)
Subject: Re: _Please_ improve localtime!
Message-Id: <37607f7b.3573200@news.skynet.be>
Russell Schulz wrote:
>I agree -- obviously, changing localtime() is a bad idea.
>
>But once you write this realtime(), _please_ submit it to perlbug, so it
>can become part of the standard distribution (helping the poor interface
>on localtime die an all-too-late death).
Hah, modernising Perl....
Why not call the newer version "mytime()"?
:-) :-) :-)
Bart.
------------------------------
Date: Wed, 09 Jun 1999 13:37:05 GMT
From: the1bob@my-deja.com
Subject: ActivePerl Win98 CGI Problem
Message-Id: <7jlqm0$jk5$1@nnrp1.deja.com>
Folks,
I realize this may be a configuration question, which is why I already
persued some other newsgroups and listservs before coming here. Any
help would be truly appreciated...
I have ActivePerl build 516 installed on a Win98 PC running the default
PWS web server software. I need to get Perl CGI scripts working. All
of my scripts run perfectly from the command line.
Here is the simple CGI script that I am testing:
print "Content-Type: html\/text\n\n";
print "<html>\n";
print "<head> <\/head>\n";
print "<body> Test <\/body>\n";
print "<\/html>\n";
Here is the error returned to the browser:
"One of the library files needed to run this application cannot be
found."
The following solution(s) did not correct the error:
Set the following:{
\HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\W3Svc\Parameters\S
criptMap:
Name: ".pl"
Data: "C:\perl\bin\perl.exe %s %s"
Name: ".plx"
Data: "C:\perl\bin\perlis.dll"
\HKEY_CLASSES_ROOT\CLSID\{EE09B103-97E0-11CF-978F-00A02463E06F}\InprocSe
rver32:
Change the named value for ThreadingModel from "Both" to "Apartment"
}
NOTE: 1) I did NOT set the .plx value in the ScriptMap key because I do
not plan to run PerlScript scripts on this particular machine. 2)
ThreadingModel was already set to Apartment by default. 3) My cgi-bin
directory is set for Read/Execute/Run Scripts.
Also.....I decided to search for all of the logs that might possibly be
effected by the error and I found the following entry in the
WAM.event.log:
6/8/99, 21:13:50, WAM Instance Started with Process Id -69061. [0]
6/8/99, 21:13:51, The HTTP server was unable to load the ISAPI
Application 'C:\perl5\bin\PerlIS.dll'. The data is the error. [485]
I looked through the registry and all of my INI files and DID NOT FIND
ANY INSTANCE of c:\Perl5. HELP!!!!! I am practically bald from pulling
my hair out now!
Background: Before installing the latest ActivePerl, I had installed
the Win32 PERL from Sam's Publishing - Teach Yourself Perl 5 for Windows
NT in 21 Days. I tried to UNINSTALL it by running the uninstall.bat
that was created in the C:\Perl5 directory. The uninstall abended with
multiple errors. I then edited the registry and removed all keys and
values pertinent to Perl5.
After cleaning up the registry and deleting the c:\Perl5
directory/subdirectories, I rebooted and installed ActivePerl build 516.
I then used PPM to update all of my modules and installed the
Mail-Sender module. Active Perl now resides in my C:\Perl
directory/subdirectory structure.
I appreciate any help that you kind folks can provide. The last resort
will be to uninstall PWS and PERL. This may effect my FrontPage 98
installation as well, so I may have to re-install it also. C'est la
vie. :-(
TIA,
Bob Raymond
Solid Edge Webmaster
http://www.solid-edge.com
256-705-2545 FAX 256-705-2690
-----
Unigraphics Solutions
675 Discovery Drive Suite 100
Huntsville, AL 35806-2801
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
Date: Wed, 9 Jun 1999 14:24:02 GMT
From: ijg@csc.liv.ac.uk (I.J. Garlick)
Subject: Re: Binary File Uploading - Part 2
Message-Id: <FD2DC2.JKE@csc.liv.ac.uk>
In article <01beb265$2fc60460$f031a2d1@ryano-ke>,
"Ryan" <dfs@thegrid.net> writes:
>
> Ok, I thought I had it worked out with the help of Will Smith (Thanks for
> your time Will!)
>
> I am trying to get a web based binary (.jpg) file upload script to work.
> Unfortunately, I do not have access to the server logs. I am receiving a
> 500 internal error and I am hoping someone can look at these two snips and
> see what is wrong..
>
Not sure, and without error logs it gets real fun real quick (not to
mention tedious).
So have you tried something like this
use CGI::Carp 'fatalsToBrowser';
Hopefully this will print any errors to your browser. I think there is a
way of doing it for warn as well. At any rate you will see what the die is
returning (assuming it is the die that causes it to stop prematurely).
>
> Humbly spoken...Help!? <G>
> Thanks for your time
> Ryan
--
--
Ian J. Garlick
ijg@csc.liv.ac.uk
The function of the expert is not to be more right than other people,
but to be wrong for more sophisticated reasons.
-- Dr. David Butler, British psephologist
------------------------------
Date: 9 Jun 1999 15:18:43 +0100
From: Jonathan Stowe <gellyfish@gellyfish.com>
Subject: Re: fork for DNS lookup - help
Message-Id: <375e77c3@newsread3.dircon.co.uk>
kayec <delete.the.nospam.kayec@gov.ns.ca> wrote:
> Malcolm Ray wrote in message ...
>>See perlipc, which gives a fair amount of guidance about using fork. If
>>you have problems, post the relevant parts of your code here with a
>>description of what happens (and what you want to happen).
>
> Sorry... what's perlipc ?
>
>
Its a piece of Perl documentation about Inter Process Communication - you
should be be able to type:
man perlipc
or
perldoc perlipc
at some command prompt.
/J\
--
Jonathan Stowe <jns@gellyfish.com>
------------------------------
Date: 9 Jun 1999 14:35:28 GMT
From: M.Ray@ulcc.ac.uk (Malcolm Ray)
Subject: Re: fork for DNS lookup - help
Message-Id: <slrn7lsutg.a1o.M.Ray@carlova.ulcc.ac.uk>
On Wed, 9 Jun 1999 10:50:03 -0300, kayec <delete.the.nospam.kayec@gov.ns.ca>
wrote:
>Sorry... what's perlipc ?
Part of the documentation distributed with perl - in this case, documentation
about interprocess communication. If you have perl, you have perlipc, and
it's definitely worth a read.
>From a command line, type:
perldoc perlipc
Alternatively, if you have ActiveState perl under Windohs, you should find
the documentation accessible from your 'start' menu.
Since you haven't heard of perlipc, I presume you're unaware of the rest
of the perl documentation. You're programming with one hand tied behind
your back. I suggest you start from here:
perldoc perl
--
Malcolm Ray University of London Computer Centre
------------------------------
Date: Wed, 09 Jun 1999 07:48:05 -0700
From: Jerome O'Neil <jeromeo@atrieva.com>
To: outlaw_torn <outlaw_torn@mailexcite.com>
Subject: Re: Get Date in Perl
Message-Id: <375E7EA5.F75FFAF7@atrieva.com>
outlaw_torn wrote:
>
> Blah blah blah...let me get my violin for your sob story.
>
> Apathy is a mans best friend. Populate the world with y2k bugs I
> say...hahahahah...lets see some fuckers squirm then. It won't bother me
> none.
>
<* plonk *>
--
Jerome O'Neil, Operations and Information Services
Atrieva Corporation, 600 University St., Ste. 911, Seattle, WA 98101
jeromeo@atrieva.com - Voice:206/749-2947
The Atrieva Service: Safe and Easy Online Backup http://www.atrieva.com
------------------------------
Date: Wed, 09 Jun 1999 13:04:42 GMT
From: nblew@my-deja.com
Subject: How to reopen STDOUT once closed
Message-Id: <7jlop3$irm$1@nnrp1.deja.com>
Hi,
I've been trying to find a means to reopen STDOUT after I have closed
it. I am unable to find the syntax for indicating the screen as a
device. Can anyone lend their expertise?
Many thanks.
- Nathan
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
Date: 09 Jun 1999 07:48:51 -0700
From: merlyn@stonehenge.com (Randal L. Schwartz)
Subject: Re: How to reopen STDOUT once closed
Message-Id: <m14skhbfak.fsf@halfdome.holdit.com>
>>>>> "nblew" == nblew <nblew@my-deja.com> writes:
nblew> Hi,
nblew> I've been trying to find a means to reopen STDOUT after I have closed
nblew> it. I am unable to find the syntax for indicating the screen as a
nblew> device. Can anyone lend their expertise?
You should probably not close it, because once it is gone, it is gone.
"the screen" is not always STDOUT, by the way... it certainly isn't
in this pipeline:
... | foo | YOURPROGRAM | bar | ...
In this case, closing YOURPROGRAM's STDOUT is irrecoverable.
Can you explain why you closed STDOUT when you didn't want to do that? :)
print "Just another Perl hacker,"
--
Name: Randal L. Schwartz / Stonehenge Consulting Services (503)777-0095
Keywords: Perl training, UNIX[tm] consulting, video production, skiing, flying
Email: <merlyn@stonehenge.com> Snail: (Call) PGP-Key: (finger merlyn@teleport.com)
Web: <A HREF="http://www.stonehenge.com/merlyn/">My Home Page!</A>
Quote: "I'm telling you, if I could have five lines in my .sig, I would!" -- me
------------------------------
Date: Wed, 09 Jun 1999 09:00:30 -0500
From: Cameron Dorey <camerond@mail.uca.edu>
To: Steffen Beyer <sb@engelschall.com>
Subject: Re: Perl on win32
Message-Id: <375E737E.A1B1AA5F@mail.uca.edu>
[cc'd to sb]
Steffen Beyer wrote:
>
> [snip]
> But is there another way, apart from a "$dummy = <STDIN>;" statement at
> the end of the script, to avoid the automatic closing of the MSDOS window
> after the script terminated (on Windows NT 4.0)?
If you open a DOS window and run your script from the command line,
instead of clicking on the name in Explorer or using the Start -> Run ->
{Insert name here} method, the DOS box will not close automatically. You
(or at least I) absolutely HAVE to do this when you are (I am)
writing/debugging a script for the obvious reasons.
Cameron
--
Cameron Dorey
Associate Professor of Chemistry
University of Central Arkansas
Phone: 501-450-5938
camerond@mail.uca.edu
------------------------------
Date: Tue, 08 Jun 1999 14:03:49 +0000
From: Antonio Gulli <gulli@ideare.com>
To: editing@ideare.com
Subject: perlcc compiling problems
Message-Id: <375D22C5.4C985DF7@ideare.com>
Hello, i-m not a perlcc guru so hope someone could help me
to understand the meaning of these error messages ... And to
compile.
Thank you !
[gulli@egadi]..uname -a
SunOS egadi 5.6 Generic_105181-05 sun4m sparc SUNW,SPARCstation-20
gcc -v
Reading specs from
/usr/local/lib/gcc-lib/sparc-sun-solaris2.6/2.8.0/specs
gcc version 2.8.0
Before .c code generation
1) What substconf stands for .. ? where can i find references to the
meaning?
2) SearchServer is a module which uses XSUB .. Socket ? What is the
problem ?
After .c code generation i got
1) A lot of warning: incompatible pointer assignment ... related to
this generated code.
static XRV xrv_list[17] = {
{ Nullsv },
{ Nullsv },
{ Nullsv },
{ Nullsv },
{ (HV*)&sv_list[6181] },
{ (HV*)&sv_list[6183] },
{ (HV*)&sv_list[6193] },
{ (HV*)&sv_list[6191] },
{ (HV*)&sv_list[6322] },
{ (HV*)&sv_list[6640] },
{ (HV*)&sv_list[6651] },
{ (HV*)&sv_list[6653] },
{ (HV*)&sv_list[6858] },
{ (HV*)&sv_list[6861] },
{ (HV*)&sv_list[6864] },
{ (HV*)&sv_list[6879] },
{ (HV*)&sv_list[6877] },
};
2) i got an internal compiler error !!!
perlcc classifierController.pl
--------------------------------------------------------------------------------
Compiling classifierController.pl:
--------------------------------------------------------------------------------
Making C(classifierController.pl.c) for classifierController.pl!
/usr/local/bin/perl -I/usr/local/lib/perl5/5.00503/sun4-solaris
-I/usr/local/lib/perl5/5.00503
-I/usr/local/lib/perl5/site_perl/5.005/sun4-solaris
-I/usr/local/lib/perl5/site_perl/5.005 -I.
-MO=CC,-oclassifierController.pl.c classifierController.pl
classifierController.pl syntax OK
substcont: op = LOGOP (0x343b60) pp_substcont, pmop = PMOP (0x3496c0)
pp_subst
pmopsym = (OP*)&pmop_list[17]
substcont: op = LOGOP (0x343dc0) pp_substcont, pmop = PMOP (0x349700)
pp_subst
pmopsym = (OP*)&pmop_list[18]
substcont: op = LOGOP (0x3b1840) pp_substcont, pmop = PMOP (0x349740)
pp_subst
pmopsym = (OP*)&pmop_list[19]
No definition for sub SearchServer::SQL_SUCCESS
No definition for sub SearchServer::SQL_SUCCESS (unable to autoload)
substcont: op = LOGOP (0x454540) pp_substcont, pmop = PMOP (0x3aad80)
pp_subst
pmopsym = (OP*)&pmop_list[23]
fulcrumIR has method new: -ufulcrumIR assumed
No definition for sub SearchServer::SQL_FETCH_FIRST
No definition for sub SearchServer::SQL_FETCH_FIRST (unable to autoload)
No definition for sub SearchServer::SQL_FETCH_LAST
No definition for sub SearchServer::SQL_FETCH_LAST (unable to autoload)
No definition for sub SearchServer::SQL_SUCCESS_WITH_INFO
No definition for sub SearchServer::SQL_SUCCESS_WITH_INFO (unable to
autoload)
No definition for sub SearchServer::SQL_FETCH_RELATIVE
No definition for sub SearchServer::SQL_FETCH_RELATIVE (unable to
autoload)
No definition for sub SearchServer::SQL_FETCH_PREV
No definition for sub SearchServer::SQL_FETCH_PREV (unable to autoload)
No definition for sub SearchServer::SQL_FETCH_ABSOLUTE
No definition for sub SearchServer::SQL_FETCH_ABSOLUTE (unable to
autoload)
No definition for sub SearchServer::SQL_NO_DATA_FOUND
No definition for sub SearchServer::SQL_NO_DATA_FOUND (unable to
autoload)
No definition for sub SearchServer::SQL_INVALID_HANDLE
No definition for sub SearchServer::SQL_INVALID_HANDLE (unable to
autoload)
No definition for sub SearchServer::SQL_FETCH_PRIOR
No definition for sub SearchServer::SQL_FETCH_PRIOR (unable to autoload)
No definition for sub SearchServer::SQL_FETCH_NEXT
No definition for sub SearchServer::SQL_FETCH_NEXT (unable to autoload)
No definition for sub SearchServer::SQL_ERROR
No definition for sub SearchServer::SQL_ERROR (unable to autoload)
altavistaIR has method new: -ualtavistaIR assumed
No definition for sub Socket::MSG_EOF
No definition for sub Socket::MSG_EOF (unable to autoload)
No definition for sub Socket::MSG_FIN
No definition for sub Socket::MSG_FIN (unable to autoload)
No definition for sub Socket::AF_APPLETALK
No definition for sub Socket::AF_APPLETALK (unable to autoload)
No definition for sub Socket::SO_DONTROUTE
No definition for sub Socket::SO_DONTROUTE (unable to autoload)
No definition for sub Socket::MSG_OOB
No definition for sub Socket::MSG_OOB (unable to autoload)
No definition for sub Socket::AF_SNA
No definition for sub Socket::AF_SNA (unable to autoload)
No definition for sub Socket::AF_DATAKIT
No definition for sub Socket::AF_DATAKIT (unable to autoload)
No definition for sub Socket::PF_IMPLINK
No definition for sub Socket::PF_IMPLINK (unable to autoload)
No definition for sub Socket::SO_RCVTIMEO
No definition for sub Socket::SO_RCVTIMEO (unable to autoload)
No definition for sub Socket::PF_ECMA
No definition for sub Socket::PF_ECMA (unable to autoload)
No definition for sub Socket::SCM_CONNECT
No definition for sub Socket::SCM_CONNECT (unable to autoload)
No definition for sub Socket::MSG_EOR
No definition for sub Socket::MSG_EOR (unable to autoload)
No definition for sub Socket::MSG_CTLIGNORE
No definition for sub Socket::MSG_CTLIGNORE (unable to autoload)
No definition for sub Socket::PF_X25
No definition for sub Socket::PF_X25 (unable to autoload)
No definition for sub Socket::MSG_ERRQUEUE
No definition for sub Socket::MSG_ERRQUEUE (unable to autoload)
No definition for sub Socket::AF_UNSPEC
No definition for sub Socket::AF_UNSPEC (unable to autoload)
No definition for sub Socket::SOL_SOCKET
No definition for sub Socket::SOL_SOCKET (unable to autoload)
No definition for sub Socket::PF_LAT
No definition for sub Socket::PF_LAT (unable to autoload)
No definition for sub Socket::AF_OSINET
No definition for sub Socket::AF_OSINET (unable to autoload)
No definition for sub Socket::MSG_MAXIOVLEN
No definition for sub Socket::MSG_MAXIOVLEN (unable to autoload)
No definition for sub Socket::AF_IMPLINK
No definition for sub Socket::AF_IMPLINK (unable to autoload)
No definition for sub Socket::SO_OOBINLINE
No definition for sub Socket::SO_OOBINLINE (unable to autoload)
No definition for sub Socket::PF_OSI
No definition for sub Socket::PF_OSI (unable to autoload)
No definition for sub Socket::PF_NIT
No definition for sub Socket::PF_NIT (unable to autoload)
No definition for sub Socket::SO_TYPE
No definition for sub Socket::SO_TYPE (unable to autoload)
No definition for sub Socket::SO_SNDBUF
No definition for sub Socket::SO_SNDBUF (unable to autoload)
No definition for sub Socket::PF_UNSPEC
No definition for sub Socket::PF_UNSPEC (unable to autoload)
No definition for sub Socket::AF_X25
No definition for sub Socket::AF_X25 (unable to autoload)
No definition for sub Socket::PF_OSINET
No definition for sub Socket::PF_OSINET (unable to autoload)
No definition for sub Socket::AF_LAT
No definition for sub Socket::AF_LAT (unable to autoload)
No definition for sub Socket::SO_DEBUG
No definition for sub Socket::SO_DEBUG (unable to autoload)
No definition for sub Socket::MSG_PROXY
No definition for sub Socket::MSG_PROXY (unable to autoload)
No definition for sub Socket::AF_GOSIP
No definition for sub Socket::AF_GOSIP (unable to autoload)
No definition for sub Socket::PF_PUP
No definition for sub Socket::PF_PUP (unable to autoload)
No definition for sub Socket::PF_CCITT
No definition for sub Socket::PF_CCITT (unable to autoload)
No definition for sub Socket::SO_SNDLOWAT
No definition for sub Socket::SO_SNDLOWAT (unable to autoload)
No definition for sub Socket::PF_802
No definition for sub Socket::PF_802 (unable to autoload)
No definition for sub Socket::MSG_DONTWAIT
No definition for sub Socket::MSG_DONTWAIT (unable to autoload)
No definition for sub Socket::AF_NIT
No definition for sub Socket::AF_NIT (unable to autoload)
No definition for sub Socket::AF_OSI
No definition for sub Socket::AF_OSI (unable to autoload)
No definition for sub Socket::PF_APPLETALK
No definition for sub Socket::PF_APPLETALK (unable to autoload)
No definition for sub Socket::SO_BROADCAST
No definition for sub Socket::SO_BROADCAST (unable to autoload)
No definition for sub Socket::MSG_WAITALL
No definition for sub Socket::MSG_WAITALL (unable to autoload)
No definition for sub Socket::AF_CHAOS
No definition for sub Socket::AF_CHAOS (unable to autoload)
No definition for sub Socket::MSG_CTRUNC
No definition for sub Socket::MSG_CTRUNC (unable to autoload)
No definition for sub Socket::AF_HYLINK
No definition for sub Socket::AF_HYLINK (unable to autoload)
No definition for sub Socket::SO_DONTLINGER
No definition for sub Socket::SO_DONTLINGER (unable to autoload)
No definition for sub Socket::PF_NBS
No definition for sub Socket::PF_NBS (unable to autoload)
No definition for sub Socket::AF_DECnet
No definition for sub Socket::AF_DECnet (unable to autoload)
No definition for sub Socket::AF_PUP
No definition for sub Socket::AF_PUP (unable to autoload)
No definition for sub Socket::AF_ECMA
No definition for sub Socket::AF_ECMA (unable to autoload)
No definition for sub Socket::SO_REUSEADDR
No definition for sub Socket::SO_REUSEADDR (unable to autoload)
No definition for sub Socket::AF_802
No definition for sub Socket::AF_802 (unable to autoload)
No definition for sub Socket::MSG_NOSIGNAL
No definition for sub Socket::MSG_NOSIGNAL (unable to autoload)
No definition for sub Socket::SO_LINGER
No definition for sub Socket::SO_LINGER (unable to autoload)
No definition for sub Socket::PF_HYLINK
No definition for sub Socket::PF_HYLINK (unable to autoload)
No definition for sub Socket::AF_NS
No definition for sub Socket::AF_NS (unable to autoload)
No definition for sub Socket::PF_DECnet
No definition for sub Socket::PF_DECnet (unable to autoload)
No definition for sub Socket::SO_RCVBUF
No definition for sub Socket::SO_RCVBUF (unable to autoload)
No definition for sub Socket::AF_NBS
No definition for sub Socket::AF_NBS (unable to autoload)
No definition for sub Socket::MSG_DONTROUTE
No definition for sub Socket::MSG_DONTROUTE (unable to autoload)
No definition for sub Socket::MSG_PEEK
No definition for sub Socket::MSG_PEEK (unable to autoload)
No definition for sub Socket::SCM_CREDENTIALS
No definition for sub Socket::SCM_CREDENTIALS (unable to autoload)
No definition for sub Socket::SOCK_RDM
No definition for sub Socket::SOCK_RDM (unable to autoload)
No definition for sub Socket::MSG_TRUNC
No definition for sub Socket::MSG_TRUNC (unable to autoload)
No definition for sub Socket::SO_RCVLOWAT
No definition for sub Socket::SO_RCVLOWAT (unable to autoload)
No definition for sub Socket::SOMAXCONN
No definition for sub Socket::SOMAXCONN (unable to autoload)
No definition for sub Socket::SCM_TIMESTAMP
No definition for sub Socket::SCM_TIMESTAMP (unable to autoload)
No definition for sub Socket::PF_NS
No definition for sub Socket::PF_NS (unable to autoload)
No definition for sub Socket::MSG_CTLFLAGS
No definition for sub Socket::MSG_CTLFLAGS (unable to autoload)
No definition for sub Socket::PF_GOSIP
No definition for sub Socket::PF_GOSIP (unable to autoload)
No definition for sub Socket::SO_USELOOPBACK
No definition for sub Socket::SO_USELOOPBACK (unable to autoload)
No definition for sub Socket::PF_MAX
No definition for sub Socket::PF_MAX (unable to autoload)
No definition for sub Socket::SO_ACCEPTCONN
No definition for sub Socket::SO_ACCEPTCONN (unable to autoload)
No definition for sub Socket::MSG_RST
No definition for sub Socket::MSG_RST (unable to autoload)
No definition for sub Socket::MSG_SYN
No definition for sub Socket::MSG_SYN (unable to autoload)
No definition for sub Socket::PF_CHAOS
No definition for sub Socket::PF_CHAOS (unable to autoload)
No definition for sub Socket::SO_SNDTIMEO
No definition for sub Socket::SO_SNDTIMEO (unable to autoload)
No definition for sub Socket::PF_INET
No definition for sub Socket::PF_INET (unable to autoload)
No definition for sub Socket::SO_ERROR
No definition for sub Socket::SO_ERROR (unable to autoload)
No definition for sub Socket::AF_MAX
No definition for sub Socket::AF_MAX (unable to autoload)
No definition for sub Socket::PF_DLI
No definition for sub Socket::PF_DLI (unable to autoload)
No definition for sub Socket::SOCK_SEQPACKET
No definition for sub Socket::SOCK_SEQPACKET (unable to autoload)
No definition for sub Socket::SCM_RIGHTS
No definition for sub Socket::SCM_RIGHTS (unable to autoload)
No definition for sub Socket::SCM_CREDS
No definition for sub Socket::SCM_CREDS (unable to autoload)
No definition for sub Socket::MSG_URG
No definition for sub Socket::MSG_URG (unable to autoload)
No definition for sub Socket::SO_KEEPALIVE
No definition for sub Socket::SO_KEEPALIVE (unable to autoload)
No definition for sub Socket::PF_SNA
No definition for sub Socket::PF_SNA (unable to autoload)
No definition for sub Socket::PF_DATAKIT
No definition for sub Socket::PF_DATAKIT (unable to autoload)
No definition for sub Socket::PF_UNIX
No definition for sub Socket::PF_UNIX (unable to autoload)
No definition for sub Socket::AF_CCITT
No definition for sub Socket::AF_CCITT (unable to autoload)
No definition for sub Socket::AF_DLI
No definition for sub Socket::AF_DLI (unable to autoload)
searchIR has method new: -usearchIR assumed
netSum has method new: -unetSum assumed
ranker has method new: -uranker assumed
HTMLout has method new: -uHTMLout assumed
summarizer has method new: -usummarizer assumed
getCatTree has method new: -ugetCatTree assumed
sumConfig has method new: -usumConfig assumed
basicHandle has method new: -ubasicHandle assumed
langide has method new: -ulangide assumed
htmlHandle has method new: -uhtmlHandle assumed
netManage has method new: -unetManage assumed
memDoc has method new: -umemDoc assumed
tagger has method new: -utagger assumed
clusterBuilder has method new: -uclusterBuilder assumed
keywordsIR has method new: -ukeywordsIR assumed
AGML has method new: -uAGML assumed
netDebug has method new: -unetDebug assumed
substcont: op = LOGOP (0x2e3a60) pp_substcont, pmop = PMOP (0x2c9440)
pp_subst
pmopsym = (OP*)&pmop_list[29]
substcont: op = LOGOP (0x2e39e0) pp_substcont, pmop = PMOP (0x2c9400)
pp_subst
pmopsym = (OP*)&pmop_list[30]
substcont: op = LOGOP (0x2ca160) pp_substcont, pmop = PMOP (0x2c9380)
pp_subst
pmopsym = (OP*)&pmop_list[31]
substcont: op = LOGOP (0x3fb6a0) pp_substcont, pmop = PMOP (0x3ff640)
pp_subst
pmopsym = (OP*)&pmop_list[84]
substcont: op = LOGOP (0x10e900) pp_substcont, pmop = PMOP (0x102680)
pp_subst
pmopsym = (OP*)&pmop_list[97]
substcont: op = LOGOP (0x107240) pp_substcont, pmop = PMOP (0x157840)
pp_subst
pmopsym = (OP*)&pmop_list[98]
substcont: op = LOGOP (0x107180) pp_substcont, pmop = PMOP (0x157880)
pp_subst
pmopsym = (OP*)&pmop_list[99]
Compiling C(classifierController) for classifierController.pl!
/usr/local/bin/perl -I/usr/local/lib/perl5/5.00503/sun4-solaris
-I/usr/local/lib/perl5/5.00503
-I/usr/local/lib/perl5/site_perl/5.005/sun4-solaris
-I/usr/local/lib/perl5/site_perl/5.005 -I.
/tmp/classifierController.pl.tst
gcc -I/usr/local/include -O
-I/usr/local/lib/perl5/5.00503/sun4-solaris/CORE
/usr/local/lib/perl5/5.00503/sun4-solaris/auto/Fcntl/Fcntl.so
/usr/local/lib/perl5/site_perl/5.005/sun4-solaris/auto/Time/HiRes/HiRes.so
/usr/local/lib/perl5/site_perl/5.005/sun4-solaris/auto/SearchServer/SearchServer.so
/usr/local/lib/perl5/5.00503/sun4-solaris/auto/Socket/Socket.so
/usr/local/lib/perl5/site_perl/5.005/sun4-solaris/auto/DBI/DBI.so -o
classifierController classifierController.pl.c -L/usr/local/lib
-L/usr/local/lib/perl5/5.00503/sun4-solaris/CORE -lperl -lsocket -lnsl
-lgdbm -ldl -lm -lc -lcrypt
classifierController.pl.c:16211: warning: initialization from
incompatible pointer type
classifierController.pl.c:16212: warning: initialization from
incompatible pointer type
classifierController.pl.c:16213: warning: initialization from
incompatible pointer type
classifierController.pl.c:16214: warning: initialization from
incompatible pointer type
classifierController.pl.c:16215: warning: initialization from
incompatible pointer type
classifierController.pl.c:16216: warning: initialization from
incompatible pointer type
classifierController.pl.c:16217: warning: initialization from
incompatible pointer type
classifierController.pl.c:16218: warning: initialization from
incompatible pointer type
classifierController.pl.c:16219: warning: initialization from
incompatible pointer type
classifierController.pl.c:16220: warning: initialization from
incompatible pointer type
classifierController.pl.c:16221: warning: initialization from
incompatible pointer type
classifierController.pl.c:16222: warning: initialization from
incompatible pointer type
classifierController.pl.c:16223: warning: initialization from
incompatible pointer type
gcc: Internal compiler error: program cc1 got fatal signal 11
ERROR: In compiling code for classifierController.pl.c !
------------------------------
Date: Wed, 9 Jun 1999 07:00:07 -0700
From: lr@hpl.hp.com (Larry Rosler)
Subject: Re: Problems sorting. I'm stupid and I'll die
Message-Id: <MPG.11c8132ed2c30288989b9e@nntp.hpl.hp.com>
In article <375e2d3a.4121716@news.demon.co.uk> on Wed, 09 Jun 1999
09:07:16 GMT, Stuart Wright
<stuw@dial.pipex.com.remove.everything.after.com> says...
> I have some script which I copied from a resource somewhere and it doesn't
> work because the version of Perl on my host's server doesn't like the '->'
> syntax.
That sounds like Perl 4. Ugh. However...
> I have an array @record which contains about 500 records, each made up of
> $manufacturer,$model,$rating,$date
> I need to do a case insensitive sort by $rating.
> I have read the Perl documentation and I simply don't understand it. I'm
> sorry - I'm stupid and I'll die.
> In the brief spell before I expire, could someone please give me the script
> to sort my array?
> like @records = (sort {uc($rating{a}) cmp uc($rating{b})} @records) type
> stuff. Nice and simple.
> I'd love to get this script to work so I can go back to killing my brain
> with beer. Many thanks in advance.
Would one 'line of code' (one statement) do the job for you?
The following Orcish-Maneuver sort works with Perl 4, which doesn't seem
to have an 'lc' function, or a 'split' function that I can make work, or
lots of other goodies in regexes that we take for granted. Hence the
ugliness in the sortkey extraction.
It was an interesting exercise in 'retro' programming. Save some beer
for me!
#!/usr/local/bin/perl4.036 -w
print sort {
($cache{$a} = (($x) = $a =~ /,.*,(.*),/, "\L$x"))
cmp
($cache{$b} = (($x) = $b =~ /,.*,(.*),/, "\L$x"))
} <DATA>;
__END__
Geo,Metro,D,1990
Mercedes,S2000,a,1999
Mercury,Sable,b,1994
Toyota,Camry,A,1984
Volkswagen,Jetta,c,2000
Output:
Toyota,Camry,A,1984
Mercedes,S2000,a,1999
Mercury,Sable,b,1994
Volkswagen,Jetta,c,2000
Geo,Metro,D,1990
--
(Just Another Larry) Rosler
Hewlett-Packard Company
http://www.hpl.hp.com/personal/Larry_Rosler/
lr@hpl.hp.com
------------------------------
Date: Wed, 09 Jun 1999 14:40:18 +0000
From: "Kerry J. Cox" <kjcox@vii.com>
Subject: Telnet monitor
Message-Id: <375E7CD2.8CE7A782@vii.com>
Quick question. I'm looking for some sort of script (I'm sure it
would be easy enough to write but I'm not a programmer) that would
monitor who is telnetting into my server and from what domain that are
coming from. Maybe by doing a "who" and checking either their IP
address or domain name. If it falls outside an acceptable range, as
determined by a flat file or something similiar, then I could either be
notified immediately by a write to my terminal. This can either be a
cron job that runs every 5 minutes or so or a daemon that runs in the
background.
Also, perhaps this script could be modified to also monitor ftp
processes. If anyone knows of a script that might do this or something
similiar that I could then modify, I would be much appreciative.
Thanks.
KJ
--
.-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-.
| Kerry J. Cox Vyzynz International Inc. |
| kjcox@vii.com Systems Administrator |
| (801) 596-7795 http://www.vii.com |
| ICQ# 37681165 http://quasi.vii.com/linux/ |
`-------------------------------------------------------'
------------------------------
Date: Wed, 09 Jun 1999 13:59:58 GMT
From: Don Roby <droby@copyright.com>
Subject: Re: Why does $blabla = <STDIN> not work in VMS Perl 5?
Message-Id: <7jls0m$k5v$1@nnrp1.deja.com>
In article <375E233C.1757F6C1@ebi.ac.uk>,
Peter Sterk <sterk@ebi.ac.uk> wrote:
> Hi,
>
> I was surprised that the following simple script which works on all
sort
> of OS's doesn't work under VMS Perl 5.003_24 (the first two and the
last
> line are necessary to run perl scripts on VMS):
> ------------------------------
> $ perl -x
> $ deck/dollar="_END_"
>
No. The above lines and the _END_ flag line are not necessary to run
perl scripts on VMS. And the $DECK command redefines STDIN so that the
Perl program is read from STDIN. Doing that makes it rather difficult
to deal with STDIN within the program.
> #! /usr/bin/perl -w
> print "What's your name? \n";
> chop($my_name = <STDIN>);
> print "My name is $my_name\n";
> _END_
> ------------------------------
>
> When this script is run, it does not pause for input from the
terminal?
Because the terminal isn't STDIN.
> Couldn't find any explanation in any FAQ or VMS Perl document. Anyone
> with a suggestion (other than 'don't bother with VMS')?
>
Put just the Perl program into a file, and invoke it using
perl -w filename
(looks familiar, eh?)
If Perl is installed right, this should work. It worked fine for me.
--
Don Roby
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
Date: 12 Dec 98 21:33:47 GMT (Last modified)
From: Perl-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Special: Digest Administrivia (Last modified: 12 Dec 98)
Message-Id: <null>
Administrivia:
Well, after 6 months, here's the answer to the quiz: what do we do about
comp.lang.perl.moderated. Answer: nothing.
]From: Russ Allbery <rra@stanford.edu>
]Date: 21 Sep 1998 19:53:43 -0700
]Subject: comp.lang.perl.moderated available via e-mail
]
]It is possible to subscribe to comp.lang.perl.moderated as a mailing list.
]To do so, send mail to majordomo@eyrie.org with "subscribe clpm" in the
]body. Majordomo will then send you instructions on how to confirm your
]subscription. This is provided as a general service for those people who
]cannot receive the newsgroup for whatever reason or who just prefer to
]receive messages via e-mail.
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.
To submit articles to comp.lang.perl.misc (and this Digest), send your
article to perl-users@ruby.oce.orst.edu.
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.
The Meta-FAQ, an article containing information about the FAQ, is
available by requesting "send perl-users meta-faq". The real FAQ, as it
appeared last in the newsgroup, can be retrieved with the request "send
perl-users FAQ". Due to their sizes, neither the Meta-FAQ nor the FAQ
are included in the digest.
The "mini-FAQ", which is an updated version of the Meta-FAQ, is
available by requesting "send perl-users mini-faq". It appears twice
weekly in the group, but is not distributed in the digest.
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 V8 Issue 5930
**************************************
