Recent content by CyBorg1958

OK - I solved it just by blabbing... :-) I simply turned the conditional around: If we're NOT in /tmp (my test directory), use STDIN/OUT, else use files. The log now shows this: ############################################################ Script source...

Kevin, in production this script is using STDIN and STDOUT - it accepts a stream from another application which calls it. In test, it's more convenient to execute it from the command line using 'regular' files as in and out. The idea is to have the script itself realize that it's being...

... as a matter of fact, if I run the script from the command line in the production folder ('customscripts'), the file names are correctly displayed as '-', as per the logfile. Still, the calling program exits with an error since it can't find INDATA.GMF... It's weird...

Hi & thanx for the tips! However... now the script dies on me at my $workdir = $ARGV[0] || die "Usage: scriptname.pl <workingdir>"; I ran the script with -W, got no warnings, it just died... Rgd's Cy

Hi! My script is triggered by the formatting process in our billing system, and when that happens it wants to use STDIN and -OUT as the in- and outdata. When I test the script I run it in another folder, from the command line : perl scriptname.pl. What I want to do is have the script know...