Sponsored Content
Full Discussion: Rsync an rcp error
Operating Systems HP-UX Rsync an rcp error Post 303013097 by Peasant on Wednesday 14th of February 2018 11:52:31 PM
Old 02-15-2018
Addition of the following switch (with existing of course) should solve your problem :
Code:
--rsync-path=/usr/local/bin/rsync

Without linkage on HPUX systems.

Regards
Peasant.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

rcp error

I'm trying to perform a rcp to a remote machine, but it keeps throwing up "LOGNAME: undefined variable" error. When I echo $LOGNAME, it comes up with my username. I have tried setting both the .rhosts and the .hosts.equiv file but to no avail (on both machines as well out of desperation!). Anyone... (8 Replies)
Discussion started by: divid_gil
8 Replies

2. Shell Programming and Scripting

rcp error trapping in rsh

I am writing a program which is something like below: rsh host1 "rcp file dest:directory" I am running this script from a machine host2. host1 has rlogin configuration for host2. but, dest machine has no rlogin configuration for host1 and fails on remote calls. Could anyone tell me how... (2 Replies)
Discussion started by: vvejendla
2 Replies

3. Shell Programming and Scripting

Need error code: rcp - reset by peer

I'm modifying a script that usese rcp. Currently the script may fail because of the "reset by peer" error message. I want to trap this in the script using a check with the $? Can anyone tell me what the error code is for the "Reset by Peer" error message when encountered by the rcp command. ... (1 Reply)
Discussion started by: jimcampanella
1 Replies

4. UNIX for Dummies Questions & Answers

Error while doing rcp to localhost

Hi, Rcping a file to localhost fails due to echo statement in .login file on a machine with RH 5.5 However, the same rcp is successful on another machine with Suse 9.2 (with the same .login). I cannot change .login file and was wondering at what could be causing this ? Command that I am... (2 Replies)
Discussion started by: coolket
2 Replies

5. UNIX for Advanced & Expert Users

SSH/RCP connectivity error

Hi Team, Hope you will be able to help me out with this problem. Our sun solaris 9 system receives Idoc files from another xxx system through RCP. But before RCP they establish an SSH connection. Since today morning they are not able to establish connection and is getting an error as pasted below... (0 Replies)
Discussion started by: anitha111
0 Replies

6. UNIX for Dummies Questions & Answers

Rsync Error

hi I have set up a rsync between to linux servers. One running Red Hat the other suse. The data is coping over but the sync using the delete option is not working. Output from command rsync -aWv --stats progress --delete /prod/CREATIVE2/WORK_IN_PROGRESS_PEARTREE 5.0.3.30:/raid1/PRODUCTION/... (0 Replies)
Discussion started by: treds
0 Replies

7. UNIX for Dummies Questions & Answers

rsync Error

hi I am running a rsync from one of our remote sites to the main building. i am using this command to run betwwen 2 linux servers rsync -aWv -e ssh --stats progress --delete --ignore-errors /raid1/PRODUCTION/WORK_IN_PROGRESS_PEARTREE/ 5.0.2.245:/prod2/RSYNCS/CREATIVE2/ >>... (2 Replies)
Discussion started by: treds
2 Replies

8. AIX

Rcp error while transferring files

i am trying to use a rsh script that uses the rcp command to copy files from server to server but it always produce the following error: HOSTNAME: protocol failure due to unexpected closure from server end Error: failed to copy /test to HOST2 system Error: failed to execute command on remote... (5 Replies)
Discussion started by: Portabello
5 Replies

9. UNIX for Advanced & Expert Users

Rsync error

this rsync from one day to the other simply no longer works, the key is ok, permissions and other ... with the same key can not connect via SSH which shows that there are no errors, but rsync it just does not work. :confused: root@san # rsync -avz -e "ssh -p 22 -i /root/.ssh/rsync"... (4 Replies)
Discussion started by: c0i0t3
4 Replies

10. Shell Programming and Scripting

Rsync Error: rsync: link_stat failed: No such file or directory (2)

I wish to copy all the files & folder under /web/Transfer_Files/data/ on mymac1 (Linux) to remote server mybank.intra.com (Solaris 10) /tmp/ location I am using Ansible tool synchronize module which triggers the unix rsync command as below:rsync --delay-updates -F --compress --archive --rsh=ssh... (2 Replies)
Discussion started by: mohtashims
2 Replies
TIMELIMIT(1)						    BSD General Commands Manual 					      TIMELIMIT(1)

NAME
timelimit -- effectively limit the absolute execution time of a process SYNOPSIS
timelimit [-pq] [-S killsig] [-s warnsig] [-T killtime] [-t warntime] command [arguments ...] DESCRIPTION
The timelimit utility executes a given command with the supplied arguments and terminates the spawned process after a given time with a given signal. If the process exits before the time limit has elapsed, timelimit will silently exit, too. Options: -p If the child process is terminated by a signal, timelimit propagates this condition, i.e. sends the same signal to itself. This allows the program executing timelimit to determine whether the child process was terminated by a signal or actually exited with an exit code larger than 128. -q Quiet operation - timelimit does not output diagnostic messages about signals sent to the child process. -S killsig Specify the number of the signal to be sent to the process killtime seconds after warntime has expired. Defaults to 9 (SIGKILL). -s warnsig Specify the number of the signal to be sent to the process warntime seconds after it has been started. Defaults to 15 (SIGTERM). -T killtime Specify the maximum execution time of the process before sending killsig after warnsig has been sent. Defaults to 120 seconds. -t warntime Specify the maximum execution time of the process in seconds before sending warnsig. Defaults to 3600 seconds. On systems that support the setitimer(2) system call, the warntime and killtime values may be specified in fractional seconds with microsec- ond precision. ENVIRONMENT
KILLSIG The killsig to use if the -S option was not specified. KILLTIME The killtime to use if the -T option was not specified. WARNSIG The warnsig to use if the -s option was not specified. WARNTIME The warntime to use if the -t option was not specified. EXIT STATUS
If the child process exits normally, the timelimit utility will pass its exit code on up. If the child process is terminated by a signal and the -p flag was not specified, the timelimit utility's exit status is 128 plus the signal number, similar to sh(1). If the -p flag was spec- ified, the timelimit utility will raise the signal itself so that its own parent process may in turn reliably distinguish between a signal and a larger than 128 exit code. In rare cases, the timelimit utility may encounter a system or user error; then, its exit status is one of the standard sysexits(3) values: EX_USAGE The command-line parameters and options were incorrectly specified. EX_SOFTWARE The timelimit utility itself received an unexpected signal while waiting for the child process to terminate. EX_OSERR The timelimit utility was unable to execute the child process, wait for it to terminate, or examine its exit status. EXAMPLES
The following examples are shown as given to the shell: timelimit -p /usr/local/bin/rsync rsync://some.host/dir /opt/mirror Run the rsync program to mirror a WWW or FTP site and kill it if it runs longer than 1 hour (that is 3600 seconds) with SIGTERM. If the rsync process does not exit after receiving the SIGTERM, timelimit issues a SIGKILL 120 seconds after the SIGTERM. If the rsync process is terminated by a signal, timelimit will itself raise this signal. tcpserver 0 8888 timelimit -t600 -T300 /opt/services/chat/stats Start a tcpserver(n) process listening on tcp port 8888; each client connection shall invoke an instance of an IRC statistics tool under /opt/services/chat and kill it after 600 seconds have elapsed. If the stats process is still running after the SIGTERM, it will be killed by a SIGKILL sent 300 seconds later. env WARNTIME=4.99 WARNSIG=1 KILLTIME=1.000001 timelimit sh stats.sh Start a shell script and kill it with a SIGHUP in a little under 5 seconds. If the shell gets stuck and does not respond to the SIGHUP, kill it with the default SIGKILL just a bit over a second afterwards. SEE ALSO
kill(1), rsync(1), signal(3), tcpserver(n) STANDARDS
No standards documentation was harmed in the process of creating timelimit. BUGS
Please report any bugs in timelimit to the author. AUTHOR
The timelimit utility was conceived and written by Peter Pentchev <roam@ringlet.net> with contributions and suggestions by Karsten W Rohrbach <karsten@rohrbach.de>, Teddy Hogeborn <teddy@fukt.bsnet.se>, and Tomasz Nowak <nowak2000@poczta.onet.pl>. BSD
September 29, 2010 BSD
All times are GMT -4. The time now is 08:56 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy