Re: Interactive Input without Expect.pm

Erm, so they want added functionality implemented by your new code, but they don't want to add any other code such as Expect? It sounds more like someone's living in a land of make-believe full of elves, faries, and eskimo</Homer>.

If there were an existing copy of Expect and it's prereqs installed that would need upgrading then yes I could see an issue; but if it's adding new code you just need to weild the cluebat and explain: "You want X; the quickest way to get X is me using module Y. Otherwise you're going to pay me BIGNUM reproducing what X does off the shelf."

Comment on Re: Interactive Input without Expect.pm

Replies are listed 'Best First'.
Re: Re: Interactive Input without Expect.pm by sagat (Novice) on May 24, 2004 at 18:13 UTC
Yeah, that would be good, except this is a fixed price project, and there are about 100-150 servers that need this script run on them. Im not about to do this. Having to compile/install Tty/Pty/Expect on all of em gives the sysadmins grey hairs. They dont want to install, and thats the excuse they are giving management. In any case, Im about to cheat by writing a script from my workstation that uses Expect to ssh to each of the servers, mounts an NFS share which has my original script, executes my script minus the parts that needs Expect, and then runs the Expect parts via ssh. An ugly hack, but it should work ;-) -chris	[reply]

Replies are listed 'Best First'.

Re: Re: Interactive Input without Expect.pm
by sagat (Novice) on May 24, 2004 at 18:13 UTC

In any case, Im about to cheat by writing a script from my workstation that uses Expect to ssh to each of the servers, mounts an NFS share which has my original script, executes my script minus the parts that needs Expect, and then runs the Expect parts via ssh. An ugly hack, but it should work ;-)

-chris

[reply]