activestate perl on cygwin

[Kevin T Cella]

I understand the trouble with using Activestate perl on cygwin is the path
conversion problem. Searching online I found the following wrapper script
useful for most perl commands:

#! /bin/sh

# This is necessary to make perl work with cygwin.  Cygwin passes
# "cygwin style" paths to the program in the #! statement and
ActiveState
# perl does not know what /cygwin/d/... means.
#
# So, we put #!/usr/local/bin/perl in the perl script and this is
called
# This routine translates the path name to something of type d:/
#
args=""
while [ $# -gt 0 ]
do
var="$1"
shift
   
if test "`echo $var | grep '/'`" = "$var"
then
# cygpath does the /cygwin/d/ to d:/ conversion
var=`cygpath -w $var`

# Then we have to swap \ for / (extra \ needed because the
# shell makes a first pass at removing the \.
  #
var=`echo "$var" | sed 's/\\\/\\//g'`
fi
args="$args $var"
done

# Finally the command is to call perl with the name of the script
and the args.
#
/c/Perl/bin/perl.exe $args


An example of one that does not work is as follows:

perl -e 'print join "\n", @INC, "\n";'


For some reason, the script above strips the single quotes from the command
and therefore does not execute the command properly. Please advise.

Thanks,
Kevin


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

RE: activestate perl on cygwin

[Kevin T Cella]

I don't actually install through cygwin, but use the ppm installer from
Activestate. I still need to know how to solve the issue that occurs with
the command I mentioned in my original post. Using the version of perl
installed with cygwin is not really an option since I already have scripts
written that utilize windows specific modules.

Thanks,
Kevin

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
DePriest, Jason R.
Sent: Tuesday, January 09, 2007 12:13 PM
To: cygwin@cygwin.com
Subject: Re: activestate perl on cygwin

On 1/9/07, Brian Dessent  wrote:
> moka at hol dot gr wrote:
> >
> > But how do you then install modules? Just like in unix from the tarballs
> >  that are intended for unix?
>
> Essentially, yes.  Just run CPAN (perl -MCPAN -e shell) and type
> "install Foo::Bar" just as you would on any unix system.  You don't have
> to actually know or care about tarballs, CPAN does all that for you.

One caveat.  If you are behind a proxy server that requires
authentication, ActiveState's PPM install tools are much easier to get
reliably working than the various command-line tools that CPAN uses
(wget, lynx, ncftp, Net::FTP, etc).

-Jason

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

RE: activestate perl on cygwin

[Kevin T Cella]

Win32::Mechanize
Win32::OLE
Win32::GuiTest
Win32::Process

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Yitzchak Scott-Thoennes
Sent: Tuesday, January 09, 2007 10:58 PM
To: cygwin@cygwin.com
Subject: Re: activestate perl on cygwin

Kevin T Cella  nycap.rr.com> writes:
> Using the version of perl installed with cygwin is not really an option
> since I already have scripts written that utilize windows specific
modules.

Out of curiousity, which modules are those?


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

RE: activestate perl on cygwin

[Kevin T Cella]

Offer an alternative. As I mentioned in my original post, I got this script
online. In using it I found it was not sufficient, I started this thread in
the hopes that someone would provide me with a better wrapper script.
Instead I got a bunch of replies about how it is a bad idea to use
Activestate with cygwin. My scripts are written to make my life on Windows
easier, so that means using Windows specific code to automate common tasks.
Ideally I'd prefer to stay in a pure Linux environment, but for reasons I do
not need to go into, I am stuck with Windows. It was my understanding that
the intent of this mailing list was to offer a place to discuss issues
involving cygwin and develop solutions to those problems. Seeing as I do not
have a whole lot of free time to research a better solution, I hoped a quick
answer would be provided via this medium. While I appreciate the suggestions
that have been made on this thread, I want to install two copies of the perl
interpreter or port my existing scripts to cygwin as that appears to be the
compromise. Are there any other ideas?

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Igor Peshansky
Sent: Wednesday, January 10, 2007 9:06 AM
To: Kevin T Cella
Cc: cygwin@cygwin.com
Subject: Re: activestate perl on cygwin

On Mon, 8 Jan 2007, Kevin T Cella wrote:

> I understand the trouble with using Activestate perl on cygwin is the
> path conversion problem. Searching online I found the following wrapper
> script useful for most perl commands:
>
>   #! /bin/sh
>
>   # This is necessary to make perl work with cygwin.  Cygwin passes
>   # "cygwin style" paths to the program in the #! statement and
ActiveState
>   # perl does not know what /cygwin/d/... means.
>   #
>   # So, we put #!/usr/local/bin/perl in the perl script and this is
called
>   # This routine translates the path name to something of type d:/
>   #
>   args=""
>   while [ $# -gt 0 ]
>   do
>   var="$1"
>   shift
>
>   if test "`echo $var | grep '/'`" = "$var"
>   then
>   # cygpath does the /cygwin/d/ to d:/ conversion
>   var=`cygpath -w $var`
>
>   # Then we have to swap \ for / (extra \ needed because the
>   # shell makes a first pass at removing the \.
> #
>   var=`echo "$var" | sed 's/\\\/\\//g'`
>   fi
>   args="$args $var"
>   done
>
>   # Finally the command is to call perl with the name of the script
and the args.
>   #
>   /c/Perl/bin/perl.exe $args
>
> An example of one that does not work is as follows:
>
>   perl -e 'print join "\n", @INC, "\n";'
>
> For some reason, the script above strips the single quotes from the
> command and therefore does not execute the command properly. Please
> advise.

The reason the script above strips the single quotes from the command is
because it's buggy.  Not only that, it'll be pretty slow, as it'll spawn a
'test' and a 'sed' for every argument.  And, judging from the comments,
its intended purpose is to allow invoking perl with a script filename, not
with a literal script.  Oh, and there's a typo in the comment --
"/cygwin/d" should be "/cygdrive/d".

However, none of these issues are Cygwin-specific (with a possible
exceptions of the typo and using "cygpath -m" instead of "cygpath -w" to
save yourself the trouble of the extra backslash translation).  Any good
tutorial on bash should show you how to properly quote the arguments.
You may also want to search the Cygwin list archives, where this exact
issue comes up once in a while (usually in the context of paths with
spaces).
HTH,
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED] |
[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_Igor Peshansky, Ph.D. (name
changed!)
 |,4-  ) )-,_. ,\ (  `'-'   old name: Igor Pechtchanski
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Freedom is just another word for "nothing left to lose"...  -- Janis Joplin

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

RE: activestate perl on cygwin

[Kevin T Cella]

> .  Thanks.

Seeing as I do not know how to configure this, I cannot oblige.

>> Offer an alternative. As I mentioned in my original post, I got this
>> script online. In using it I found it was not sufficient, I started this
>> thread in the hopes that someone would provide me with a better wrapper
>> script.

> I did.  .

This also does not appear to work for the example I gave.

> ... there is nothing Cygwin-specific about writing such a wrapper
> script.  As I said, any good bash tutorial would have contained enough
> information for you to write one.  Since this is not a bash support list,
> discussion of techniques for making such scripts work is off-topic.

That's debatable, the distinction is vague at best.

> Besides, it's been discussed to death at least 3 times that I recall --
> and it's all in the archives of this very list.  The script in my message
> above has definitely been posted before, and even in a similar context.
> In fact, that discussion is the 5th match when searching the list archives
> for "activestate wrapper", and the 1st (yes, first) match when Googling
> for "activestate wrapper site:cygwin.com inurl:ml" (or even for
> "activestate wrapper cygwin").  That's why we have the web archives -- to
> hopefully avoid rehashing the same issues over and over again.

>> Seeing as I do not have a whole lot of free time to research a better
solution,
>> I hoped a quick answer would be provided via this medium.
[snip]

HTH,
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED] |
[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_Igor Peshansky, Ph.D. (name
changed!)
 |,4-  ) )-,_. ,\ (  `'-'   old name: Igor Pechtchanski
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Freedom is just another word for "nothing left to lose"...  -- Janis Joplin

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

RE: activestate perl on cygwin

[Kevin T Cella]

> But it is a bad idea to use ActiveState under Cygwin. Would you prefer 
> if we lied to you?

No, I'd prefer you answer my question. I can't use Activestate perl on
cygwin by not using Activestate perl on cygwin. Do you see the
contradiction?

>> My scripts are written to make my life on Windows easier, so that 
>> means using Windows specific code to automate common tasks.
> But you really don't need to do such things in a "Windows specific" way! 
> I used to run my whole domain under Cygwin. Apache for my web server, 
> exim for a mail server, Cygwin's own inetutils for ftp, ssh, etc. 
> Everything ran fine albeit a bit slower due to the fact that Cygwin is 
> an emulation environment.

Seeing as how you don't know what common tasks I am trying to automate,
I don't see how you can presume to know the scripts do not have to be
written in a Windows specific way. Suppose your theory is that any script
written for Windows can be written to work with Linux. As I stated earlier,
I do not wish to port my existing scripts to cygwin.

> And if the real, long term, more portable solution is to use a Cygwin 
> based, thus more normal Perl...

I'm asking for the short term solution.

> Answers were provided to you. Apparently they don't tickle your fancy. 
> People have commented on that wrapper script that you posted. I still 
> don't see what your problem is. If your Perl script expects 
> C:\mydir\foo.dat then give it C:\mydir\foo.dat. Of course you'll need to 
> do that under a cmd shell or, for Cygwin's bash shell you'll need to 
> double the backslashes (C:\\mydir\\foo.dat) or use forward slashes 
> (C:/mydir/foo.dat). If you insist on giving your Perl script 
> /cygdrive/c/mydir/foo.dat then perhaps your Perl script should expect 
> that and translate it. A quick Perl subroutine to do that shouldn't be 
> that hard to code.

Other posts have indicated how this is not possible. Executing a script
That appears in my $PATH will automatically expand using cygwin style
pathing. Answers were provided, but not to my original question. I still
have no way to execute the command below and a regular script on cygwin
using Activestate.

perl -e 'print join "\n", @INC, "\n";'



--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

RE: activestate perl on cygwin

[Kevin T Cella]

> Actually, being technical about this and looking at your OP there is no 
> question there at all! Search for it. Look for a question mark. There is 
> none. There is merely the sentence "Please advise" and that's what you
got!

Congratulations! I was wondering when someone would point that out; and
for the record, "?".

> "I can't use this pair of pliers to tow this boat. Please advise". - 
> Well how about cha use a tow instead?

Clever.

>> Seeing as how you don't know what common tasks I am trying to 
>> automate, I don't see how you can presume to know the scripts do not 
>> have to be written in a Windows specific way.

>It's pretty much a given unless you simply insist on doing it in a 
>Windows specific way.

My operating system is Windows and therefore many of my applications are
only compatible with Windows. In order to interact with the application
through their SDKs, I need to use Win32 modules.

> I gave you an answer for your "short term solution". If you insist on 
> using a Windows oriented product such as ActiveState then fire up cmd 
> and type in Windows specific path names to your Windows only ActiveState 
> Perl scripts. Where's the problem?

I'm lazy, it's inconvenient.

>> Executing a script That appears in my $PATH will automatically expand 
>> using cygwin style pathing.

> This statement doesn't even make sense. What exactly is expanding? If 
> you type myscript.pl 'C:\\Cygwin\\tmp\\file' and myscript.pl echoes out 
> the first arg what do *you* get?

That example I can simply handle in the application, but I mean more when
I invoke the script. When it is in my $PATH and I type myscript.pl, the
full path is expanded and passed to the interpreter with cygwin style paths.



--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

RE: activestate perl on cygwin

[Kevin T Cella]

> [snip] you only need the wrapper script to transform the script name from
> POSIX path style to Win32 style, and only if it's in the #! (shebang)
> line of a perl script.  That was what my wrapper script was designed to do
> (as shown by the example usage). You do NOT need a wrapper to run the
> command above -- just invoke ActiveState perl directly.

This is brilliant! I have no idea why I did not see it before, but this
solves
my problem in a very concise way. My wrapper script can mimic yours if the
number
of arguments is exactly 2. If they are greater than 2, then I will invoke
Activestate
perl directly making sure to use Windows style paths when appropriate (ie:
perl -c ).

On another, more apologetic note...

I cannot believe I have not been kicked off this mailing list yet. Everyone
has been
more than helpful and I have just been a complete ass. Honestly, I could not
tell you
why, but for whatever reason it was kind of fun trying to find an angry
retort. Maybe
I finally snapped, all too often I post technical questions to forums or
mailing lists
without any solutions to my problems. I swear this is not me being
sarcastic. You have
my word I will continue to be less caustic. My rant is over. Thanks!







--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

RE: activestate perl on cygwin

[Kevin T Cella]

> [snip] but the point of this little story is that you
> are short sighted if you believe that the only platform you'll
> encounter and thus need to deal with is Windows...

I agree completely. This is for personal use.

> As has been pointed out to you already there is Win32 modules for
> Cygwin's Perl.

Sorry, I missed that.

> Although this is thorough off topic, perhaps you can explain it better
> to me as I don't use ActiveState therefore I don't see what you are
> claiming. Exactly which "full path" is expanded to "what" and passed to
> (guess) ActiveState Perl interpreter as, again, what? Is it $0 that you
> speak of that may be a Cygwin path? I'm confused however if it is $0
> then why couldn't that also be handled in the Perl script?

The error is as follows:

[~] $ myscript.pl 
Can't open perl script "/home/kcella/bin/myscript.pl": No such file or
directory

[~] $ ls -l /home/kcella/bin/myscript.pl 
-rwxr-xr-x 1 kcella None 651 Jan 12 07:33 /home/kcella/bin/myscript.pl


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

RE: activestate perl on cygwin

[Kevin T Cella]

> That particular case is handled by the wrapper script I posted.  Note
> that
> you *don't* need to use the wrapper script to invoke perl on the
> command
> line -- only in the #! (shebang) line of your script file.

I know. Thanks. I was just trying to oblige the request from Mr. DeFaria.


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

RE: activestate perl on cygwin

[Kevin T Cella]

> Well, I run perl scripts on cygwin with no problem. Did not do anything
> special,
> except
> make sure NOT to install perl when installing cygwin(and making sure
>  the activestate perl is in the path)

I tried this, but it still does not work.


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

RE: activestate perl on cygwin

[Kevin T Cella]

> What does that matter? It's still short sited.

Yes, I don't disagree. Personally I do not care. I will deal with
having to port something when it happens.

> And what does #! look like?

#! /usr/bin/perl

> what does ls portion after #! in your script return?

Before the conversion using cygpath, it returns the same as
in the error: /home/kcella/bin/myscript.pl

But I think, there is some confusion here. My script will correctly execute
the
program using Activestate perl. The example I gave is for when I have no
wrapper script and just create a symlink in /usr/bin/perl that points
to /c/Perl/bin/perl.exe. The root cause of the example is the reason
for the initial post. The wrapper script was the solution I happened to
choose to get around the path problem, but quickly found out that it does
not work properly with: perl -e 'print join "\n", @INC, "\n";'

> Oh and what is PATH set to?

/home/kcella/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/c/Perl/bin/:/c
/WINDOWS/system32:/c/WINDOWS:/c/WINDOWS/System32/Wbem


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

RE: activestate perl on cygwin

[Kevin T Cella]

> > >  And what does #! look like?
> > #! /usr/bin/perl
> Is there something that the space after the "!" and before the "/" buys
> you?

Readability. It is simply a question of style. I prefer the space. Has
it come to that?
 
> So your specifically saying by your shebang line - execute Cygwin's
> perl.

As I state later, I use a symlink so I am infact executing Activestate perl.
Seriously, are you trying to attack me or understand the problem? I am
trying to be nice, I already apologized for my behavior earlier.

> >> what does ls portion after #! in your script return?
> > Before the conversion using cygpath, it returns the same as in the
> > error: /home/kcella/bin/myscript.pl
> So then you are saying that you have no /usr/bin/perl? Is so then why
> do
> you put "#! /usr/bin/perl" in your script at all?

I think I misunderstood the question. I had taken it to mean had I
executed an ls on the incoming argument to my wrapper script (ie: the
script filename), what would be the output. Now I see what you were
trying to get at was if the interpreter referenced by the #! line exists
on my system. As I state later, I use a symlink:

$ ls -l /usr/bin/perl
lrwxrwxrwx 1 kcella None 20 Jan 13 00:19 /usr/bin/perl ->
/c/Perl/bin/perl.exe

> So now you are saying that you have no problem?!?

Keep reading...

> > The example I gave is for when I have no wrapper script and just
> > create a symlink in /usr/bin/perl that points to
> /c/Perl/bin/perl.exe.
> Huh? There is no /c/... although I've heard of a way to do that I've
> also heard that it's not supported. Futher, why would you want to
> symlink /usr/bin/perl -> /c/Perl/bin/perl.exe?!? Or, since you insist
> on
> using ActiveState, then why not specifically specify something like
> #!C:/Perl/bin/perl.exe or something like that?

Again, it is just a question of style. I have done it both ways, I
prefer using linux style pahts. I mount c: to /c because it is
much faster to type than /cygdrive/c/ and it makes more sense from
a readability standpoint.
 
> > The root cause of the example is the reason for the initial post. The
> > wrapper script was the solution I happened to choose to get around
> the
> > path problem, but quickly found out that it does not work properly
> > with: perl -e 'print join "\n", @INC, "\n";'
> >> Oh and what is PATH set to?
> >
> /home/kcella/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/c/Perl/bi
> n/:/c
> > /WINDOWS/system32:/c/WINDOWS:/c/WINDOWS/System32/Wbem
> You could probably also simply use #!perl since C:/Perl/bin is in your
> path...

Another question of style. Although for me it is more habitual
than stylistic. Your questions are very subjective with an insulting tone.
I'm sorry if I have offended you in some way. Do you at least understand
Why the cygwin style paths are causing an issue? And what it is I am trying
to accomplish?



--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/

RE: activestate perl on cygwin

[Kevin T Cella]

> I simply asked a question. You provided an answer.
> Whose undies are in a bunch here?

As did I. Sorry I misinterpreted your tone.

> Wouldn't it be much more
> "stylistic" and clear to simply point directly at the Perl you insist
> on
> using?  Or did you really mean you are putting /usr/bin/perl in there
> to appear to be portable? That sort of answer I'd understand... except you
> have already stated that you don't care about portability.

It is my opinion that it looks better. I'm sorry you disagree.

> > Seriously, are you trying to attack me or understand the problem? I
> am
> > trying to be nice, I already apologized for my behavior earlier.
> My opinion on this situation does not require that I'm your friend.

I am not asking for friendship, just civility.

> And it's an answer of confusion. If I were to work on your script I
> would see /usr/bin/perl and think "Great. He's using a standard perl
> and
> I should be able to easily use this under Linux or Cygwin's perl, etc.
> Wait... Err... No... He's symlinked this to ActiveState!" and would be
> scratching my head wondering why you attempted to appear "Unix-like"
> with the shebang line yet are using a proprietary perl

My scripts will not leave this computer. I have absolutely no
intention of sharing any of my code. The only person who has
to understand it is me. I'm sorry it confused you.

> I know you said you want to use Win32 stuff but there's Win32 stuff
> that
> you could use in Cygwin too. If you really like Linux style paths, use
> Windows and Cygwin, seem to exert full control of the environment I
> would think using Cygwin's Perl, where you can more easily use Linux
> style paths not only for shebang but more conveniently throughout your
> script, would be something you'd want to do...

Agreed. In the long term it may happen, but not at this moment.
 
> BTW you never answered the question of what happens in ActiveState when
> you call setsid. I'll answer it for you. It returns "Not implemented on
> this platform" or something like that. IOW ActiveState does not
> implement nor support calling setsid. Why would you want setsid? It's
> useful in writing daemons, something I do on occasion. Along with that
> ActiveState doesn't seem to handle signals well. Forgive me here my
> memory is hazy as I had worked on this problem several years ago. I was
> attempting to write a daemon that would be essentially a Windows
> service
> and wanted it to be a multi threaded server meaning I wanted to fork
> and
> exec copies of myself to handle incoming requests. This requires proper
> signal handling. I was having problems with this so I queried in
> ActiveState forums and the guy responsible for signals in ActiveState
> responded that Windows doesn't support signals very well!
> 
> Back to Cygwin's Perl I could call setsid as well as wrote a little
> test
> program that set, sent and trapped all 30 or so supported signals
> without a problem. So much for ActiveState!

I will deal with it if an when I need to write a daemon script. Thanks
for the information.

> You've come in here and asked a question to which you have been given
> an
> answer. You insist on mixing together to separate distinct technologies
> that were not designed to work together where experienced people here
> advise that you stop fighting the two use the technologies more in the
> way they were intended than in ways they weren't intended. Ah but you
> insist on doing it the hard way. "Fine then, have fun with your
> problem"
> is not an unreasonable nor should it be an unexpected response for you.

I have already solved my problem, I will be using Mr. Peshansky's idea.
You have been asking me questions ever since, I am simply trying to provide
you with answers thereby extending to you the same courtesy others have on
this thread.
 


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/