in reply to Background proc requires ENTER keystroke on Windows 2012
Sorry, I got stuck trying to get cpanm to run in my system; without success. (What a steaming pile!)
Have you tried substituting some other command for cpanm? If the substitute doesn't hang it would indicate that it is cpanm; probably a difference in configuration between the systems.
Guesswork here, but from my previous experiences with cpan & cpanp; they tend to make extensive use of Term::* for keyboard handling; providing (crap) history and supposedly "pretty" coloring that makes the output look like a '90s leet hAxoR website -- ie. totally unreadable... {rant grossly abbreviated}
My point is that those modules only seem to "work" on windows if the cmd window sessions are configured with the default settings -- eg. 80x25 screen white on black; no quickedit or tab completion etc. etc. Settings that no one who actually use windows would ever stick with.
My best guess from reading the symptoms is that AWS cmd sessions are not configured with those useless defaults and so Term::* et.al. conflict.
The easy way to test is to replace cpanm with a simple perl script by the same name that just reads the arguments and echos them to both stdout and stderr.
If that works without hanging, you know where to look and what to look for.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: Background proc requires ENTER keystroke on Windows 2012
by Anonymous Monk on Aug 01, 2016 at 19:34 UTC | |
|
Re^2: Background proc requires ENTER keystroke on Windows 2012
by stevieb (Canon) on Aug 01, 2016 at 19:55 UTC | |
by BrowserUk (Patriarch) on Aug 01, 2016 at 20:13 UTC | |
by stevieb (Canon) on Aug 01, 2016 at 23:22 UTC | |
by BrowserUk (Patriarch) on Aug 02, 2016 at 01:03 UTC |