-
Notifications
You must be signed in to change notification settings - Fork 225
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Older versions of wget do not support --trust-server-names #57
Comments
Thanks for making an issue for this, I know of the problem and others have done the same as you suggest in the past. Maybe that should be the fall back plan. |
I found this too when I set up msm a couple weeks ago and did the same as @jvz. I checked and this issue will affect all released versons of Red Hat Enterprise Linux and CentOS up to the current 6.3. I'll submit a patch suggestion for it, though it might be a week or two since work is a little crazy this month. I'll review for other things that could improve Red Hat compatibility too, since some commands generate error messages on RHEL5. |
Actually, I suppose I should ask first whether you're interested in making things more RH/Fedora friendly: I'm biased since I've lived in Red Hat adminland for so many years. To do so would touch a number of functions, especially init tree maintenance as discussed in issue #51 |
I only have experience with Debian distributions, however if, as it seems, MSM can be made to run quite easily on RPM based linux then it just definitely be discussed, and I'm open to suggestions on the point. |
See #86 for a patch. |
Issue is fixed. |
I'll keep this open until I merge it in. |
Actually, this problem has been fixed. Ignore me 😄 |
If I use the version of wget I have on my computer (1.13.4), it supports the
--trust-server-names
option, but if I use the version of wget (1.12) that comes with Amazon AMI 2012.03 (their latest version, based on RedHat), it does not support the option and instead errs out. To fix on my end, I just had to remove the option, but a better fix may be to do a version check for support of the option.The text was updated successfully, but these errors were encountered: