Reputation: 59
We have recently migrated from HPUX 11 to RHEL 6 and in the process our sysadmin group informed us that lynx was no longer available and we'd have to use elinks instead. We make servlet calls from nightly batch processing scripts and never had a problem with lynx. With elinks about half the time it double fires and calls the servlet twice (as much as two minutes between firings with no other activity on the system).
Being servlets each is independent and unaware of other instances and so we're having to do a lot of cleanup the following day and at times this results in very large financial transactions going screwy.
The sysadmins know nothing about elinks and have left it up to us, none of whom is a linux expert, to figure out why elinks sometimes double fires when called from a shell script and other times doesn't. Anyone else experience something like this or have some sort of starting point? I've of course been through the documentation and the elinks website.
Upvotes: 0
Views: 367
Reputation: 59
So there is actually a config option in elinks where it will retry three times if it doesn't get a response, and given that the servlet was a fire-and-forget it obviously didn't get a response. I'm still a bit curious as to why it would only retry sometimes and not others, but curl is a better solution anyway so I'm moving on. Thanks for the insights, all.
Upvotes: 0