ssh/scp at Redhat Enterprise 3 (2.4.21-32.ELsmp #1 SMP Fri Apr 15 21:17:59 EDT 2005 i686 i686 i386 GNU/Linux)

[Kautzsch, Dirk]

Dear People, 

I have following situation with "OpenSSH_3.6.1p2, SSH protocols 1.5/2.0,
OpenSSL 0x0090701f": 

a) I will send files via scp to: "OpenSSH_3.8p1, SSH protocols 1.5/2.0,
OpenSSL 0.9.7d 17 Mar 2004" 

b) used command: 

scp [-vvv] -p -B -C /home/gdg/generation/cr/test_lnx50/lnx50.test2.000001
gdg at lnx50:/home/gdg/EMPFANG/lnx50.test2 

Login without PW runs fine, DEBUG3 shows never any errors, but the target
file will not be created ! 

c) used command: 

scp [-vvv] -p -B -C /home/gdg/generation/cr/test_lnx50/lnx50.test2.000001
gdg at lnx50:/home/gdg/EMPFANG/    <--- without any filename 

Login without PW runs fine, DEBUG3 shows never any errors, but the target
file will be created :-) 

d) then, I will rename file at remote server via ssh 

ssh [-vvv] gdg at lnx50  mv -f /home/gdg/EMPFANG/lnx50.test2.000001
/home/gdg/EMPFANG/lnx50.test2  

After this action are not more files inside directory ! 
If I use "cp", then the first file (lnx50.test2.000001) exists - the second
(lnx50.test2) are not exists. 

My comments: 

All command will be run from a script-deamon that run with "nohup ... &".
The script-deamon start the "work-script" via "nohup ... &" and this will
execute the scp/ssh-command. 

The user.environment is correct and available in background. 

Note: All commands work fine, if I start from a console. 

May be, It's a special security rule active or the background had a other
environment ? 

Have you any idea ? 

Thanks in advance and cordial regards, 

Dirk Kautzsch