I am running a RHEL 3.0 on one machine and RHEL 4.0 on the the other -
both intel machines.
I have a cron that transfers a very large(2.8Gig AFTER gzip) file. I scp
the file from one machine (RHEL 3.0 - on a T1) to the other (RHEL
4.0-also on a T1), and find that their md5sums are different. However,
when I transfer the file over the local network(sames two machines -
just in the same building this time), the files match. It seems to have
something to do with an internet transfer only.
Questions:
1. How to I troubleshoot what is happeneing and when? Logs? Run scp in
debugging mode? The file is clearly coming over corrupted...
2. Can I use scp or rsync with md5 during the transfer (as opposed to
after the transfer) to ensure that it gets over clean? If not, what then?
Also - station wagon transfers are not an option, thanks. :)
RE: Revisiting an old topic: licensing/titlement and "redistribution" ... What you pay for is the patches and support you get over RHN. ... The media alone... just _not_ take advantage of support or updates for those machines?... trial of RHEL and continue using it legally even after the trial is ... (RedHat)
Revisiting an old topic: licensing/titlement and "redistribution" ... just _not_ take advantage of support or updates for those machines?... trial of RHEL and continue using it legally even after the trial is ... you can continue to use a paid-for installation of RHEL ... after the entitlement has run out. ... (RedHat)
Re: Fedora Makes a Terrible Server? ... add-ons on the enterprise OSes, if you are in a fast moving enterprise environment RHEL won't work. ...enterprise environments, but most would argue there you should probably lock everything down so tight that few kernel updates/userspace are even required for anything, the problem is in an environment were you are constantly having to bring in new hardware that does not work on the older release, where you cannot wait 6 months for RHEL to catch up. ... You typically bring in around a large enough set of new machines at a time any only update the pieces required to support that new machine, and then you run some test to validate that it gives the correct answers for various jobs. ... (Fedora)
Re: [PATCH] x86[-64] PCI domain support ... The x86PCI domain effort needs to be restarted, ...machines out in the field that need this in order for some devices to ... I assume IBM would have complained if it was broken in RHEL.... (Linux-Kernel)
Re: [PATCH] x86[-64] PCI domain support ...Greg KH wrote: ...machines out in the field that need this in order for some devices to ...RHEL is shipping it now, ... (Linux-Kernel)
