Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
-
Need code to print message if software doesn't install then continue to next software
You did not specify, how you install Gimp, so it is difficult to recommend a suitable solution. Usual install scripts return a non-zero exit code, which you might want to catch. Others might output something to stderr to indicate failure, so you can evaluate this.- rovf
- Post #2
- Forum: UNIX Scripting
-
Need some help with Perl Error!
> Not sure if this statement is supported on the ActivePerl I wouldn't call __END__ a "statement", but ... yes, it is Perl standard, and works well with ActiveState Perl too. -
pclose returns -1 in solaris 10
You posted this in the wrong forum. This forum is intended for Perl problems, so you probably won't get much help. As of your problem, I would do a perror to get more information. -
ssh via expect
Update: Also crossposted here: http://www.unix.com/shell-programming-scripting/160967-ssh-via-expect.html -
ssh via expect
(Crossposting note: I have already posted this article on comp.lang.tcl on the 3 days ago. This is posted here again, because I didn't get any response on my original article so far). I use the following script on Solaris to log into a remote host: spawn ssh other@[exec uname -n] expect {$}... -
Write all STDIN lines into a file
>> How do you signal EOF? > Ctrl-D on a blank line. For completeness, we should mention that this is true on Unix-like systems. For Windoze CMD shell, for instance, it would be Ctrl-Z. Though the #! line of the OP's program suggests that he is indeed using such a system, we can not conclusively... -
Write all STDIN lines into a file
> Strangely, the OPs code worked fine for me unmodified. Well, if the OP really used his code from the command line, maybe he simply forgot to signal EOF to STDIN.... -
Write all STDIN lines into a file
> How can you make such a generalisation? It depends entirely on how the script is normally invoked. Exactly that's the point. The OP does not reveal how s/he normally invokes the script, hence we can not assume that STDOUT connects to a terminal. That's what "In general..." means. BTW, it's... -
Write all STDIN lines into a file
Writing the prompt to STDOUT doesn't make much sense to me. In General, STDIN/STDOUT won't be connected to a terminal.
