go ahead... be a heretic | |
PerlMonks |
Background proc requires ENTER keystroke on Windows 2012by stevieb (Canon) |
on Aug 01, 2016 at 16:42 UTC ( [id://1168938]=perlquestion: print w/replies, xml ) | Need Help?? |
stevieb has asked for the wisdom of the Perl Monks concerning the following question: Disclaimer: cross-posted at StackOverflow. This is a much simpler (pure Perl) version of Debug background Perl procs started with compiled C# code (breaks only on AWS), as its far less reading, and much simpler to test/reproduce. The issue is that on my Amazon Web Services (AWS) Windows 2012 systems, a Perl script that runs in the background listening for network requests requires an ENTER keystroke in the server script (background proc) cmd window before it processes. This does not happen on my Windows 2008 R2 systems (the proc runs properly with no interaction). I am not certain if this is an AWS thing, or a win2k12 thing, as I don't have any 2k12 servers to test on that aren't in AWS. I'd appreciate if anyone with 2k12 systems could test this to see if it works properly. This test does not require any non-core modules to be installed, and I've removed the requirement for Proc::Background as well. To repro:
On my local servers, the server returns to the client properly without any interaction. On my AWS systems, it hangs. Hitting ENTER in the server cmd window causes things to go through. Running the server script in foreground mode (perl server.pl run), the whole shebang works properly on 2012 with no interaction. NOTE: there's no method in this test code to stop the server.pl background proc. It has to be killed via Task Manager. client.pl
server.pl
Back to
Seekers of Perl Wisdom
|
|