|Pathologically Eclectic Rubbish Lister|
Re^4: making NET:SSH quietby DeadPoet (Scribe)
|on Jan 12, 2011 at 18:36 UTC||Need Help??|
I am more than willing to explore...
The topic that I see as most interesting is wrong handling of hung sessions. Thus far, in our 2300+ server environment I have NOT come across a set of SSH options that can account for when a process becomes hung on the remote server, such as rpm, df, bdf, getconf, ioscan, flaky sshd, etc... That is why one may need to kill the process and prevent script lock.
Oh please, provide an example and I will run tests.
Next, I am not knocking the various authors of CPAN Secure Shell modules. These folks have done wonderful work, such as your work. But I did say:
However, many of these modules can be difficult to compile on various platforms...
And, one may not be able to meet the requirements needed to compile. If I remember correctly, each module that I have used ships with ActiveState Perl.
Passwords and Pass Phrases could easily be addressed as the IPC::Open3 call provides STDIN, STDOUT, and STDERR. Synchronization between workers, what are they working on together? Are they working on the same server or different. Once again the %RESULTS shared hash is an example of bringing data back to the parent. However, could server(X) see server(y)'s data and act upon it, yes--the structure is shared. Could one just report on the collective information, as illustrated, yes. It is a concept and I stated adjust as needed.
So now I will add to my original statement and say: Check your local listing and your mileage may vary.--Poet