rusty@GARNET.BERKELEY.EDU (08/04/89)
Does anybody know if the rcp bug in Ultrix 3.0 on the DS3100 where when you do an rcp between two remote machines it comes back with "Segmentation fault" (but doesn't core dump)? Here's an example of what I mean: machine1% rcp machine2:file machine3:file
grr@cbmvax.UUCP (George Robbins) (08/05/89)
In article <8908031904.AA24094@garnet.berkeley.edu> rusty@GARNET.BERKELEY.EDU writes: > Does anybody know if the rcp bug in Ultrix 3.0 on the DS3100 where > when you do an rcp between two remote machines it comes back with > "Segmentation fault" (but doesn't core dump)? Here's an example of > what I mean: > > machine1% rcp machine2:file machine3:file Anybody try this? It works fine on VAX architecture... -- George Robbins - now working for, uucp: {uunet|pyramid|rutgers}!cbmvax!grr but no way officially representing arpa: cbmvax!grr@uunet.uu.net Commodore, Engineering Department fone: 215-431-9255 (only by moonlite)
hill@faline.bellcore.com (Chris Hill) (08/08/89)
In article <> grr@cbmvax.UUCP (George Robbins) writes: >In article <8908031904.AA24094@garnet.berkeley.edu> rusty@GARNET.BERKELEY.EDU writes: >> Does anybody know if the rcp bug in Ultrix 3.0 on the DS3100 where >> when you do an rcp between two remote machines it comes back with >> "Segmentation fault" (but doesn't core dump)? Here's an example of >> what I mean: >> >> machine1% rcp machine2:file machine3:file > >Anybody try this? It works fine on VAX architecture... > Where a=uVAX II b=3100 c=3100 On system a rcp b:file c:file works OK On system b rcp a:file c:file rcp c:file a:file rcp c:file b:file rcp b:file c:file all fail with Segmentation fault but rcp c:file . rcp file b: both work OK Thank goodness we never use that command!