Sponsored Content
Full Discussion: /usr/bin/scp error
Top Forums Shell Programming and Scripting /usr/bin/scp error Post 302918072 by junior-helper on Saturday 20th of September 2014 04:47:58 PM
Old 09-20-2014
Quote:
Originally Posted by Daniel Gate
I am wondering if the syntax is incorrect...
Yes, it is incorrect. I think you are confusing scp with rsync. scp does not support the exclude-from feature.

Code:
       Some of the additional features of rsync are:

       o      support  for copying links, devices, owners, groups, and permis‐
              sions

       o      exclude and exclude-from options similar to GNU tar

1. Regarding scp, I think your assumption is right, but for the first time of scp-ing only. When you scp the second time, then you need to remove the uppermost target directory, because it already exists. You should check out the following trick with rsync and the trailing slash:

Code:
       A trailing slash on the source changes this behavior to avoid  creating
       an  additional  directory level at the destination.  You can think of a
       trailing / on a source as meaning "copy the contents of this directory"
       as  opposed  to  "copy  the  directory  by name", but in both cases the
       attributes of the containing directory are transferred to the  contain‐
       ing  directory on the destination.  In other words, each of the follow‐
       ing commands copies the files in the same way, including their  setting
       of the attributes of /dest/foo:

              rsync -av /src/foo /dest
              rsync -av /src/foo/ /dest/foo

2. Not with scp, but I think it's the default behaviour of rsync.

I hope this helps.
This User Gave Thanks to junior-helper For This Post:
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

/bin/sh: /usr/bin/vi: No such file or directory when doing crontab

I just set up an ftp server with Red Hat 5.2. I am doing the work, I'm baby stepping, but it seems like every step I get stuck. Currently, I'm trying to set up a crontab job, but I'm getting the following message: /bin/sh: /usr/bin/vi: No such file or directory. I see that vi exists in /bin/vi,... (3 Replies)
Discussion started by: kwalter
3 Replies

2. AIX

nim mksysb error :/usr/bin/savevg[33]: 1016,07: syntax error

-------------------------------------------------------------------------------- Hello, help me please. I am trying to create a mksysb bakup using nim. I am geting this error, how to correct it ? : Command : failed stdout: yes stderr: no... (9 Replies)
Discussion started by: astjen
9 Replies

3. Solaris

How do I link ld in /usr/ucb/ to /usr/ccs/bin?

Hi all, below is the problem details: ora10g@CNORACLE1>which ld /usr/ucb/ld ora10g@CNORACLE1>cd /usr/ccs/bin ora10g@CNORACLE1>ln -s /usr/ucb/ld ld ln: cannot create ld: File exists ora10g@CNORACLE1> how to link it to /usr/ccs/bin? (6 Replies)
Discussion started by: SmartAntz
6 Replies

4. Shell Programming and Scripting

!/usr/bin/ksh error

Usually we use !/usr/bin/ksh at the start of the script.But if I am having this stuff in the scripts and calling one script from other its not working.What may be the reason behind it ? xyz.ksh #!/usr/bin/ksh echo "Hi" abc.ksh #!/usr/bin/ksh echo "I am fine" ksh xyz.ksh Its... (4 Replies)
Discussion started by: dr46014
4 Replies

5. OS X (Apple)

When to use /Users/m/bin instead of /usr/local/bin (& whats the diff?)?

Q1. I understand that /usr/local/bin means I can install/uninstall stuff in here and have any chance of messing up my original system files or effecting any other users. I created this directory myself. But what about the directory I didn't create, namely /Users/m/bin? How is that directory... (1 Reply)
Discussion started by: michellepace
1 Replies

6. Red Hat

/usr/bin/rhgb-client -- error while loading shared libraries: libpopt.so.0

Hi All, I have RHEL 5 installed in my system. Something must has happened because when i reboot the server, it came with many error.. /usr/bin/rhgb-client -- error while loading shared libraries: libpopt.so.0. Can't open shared object files. No such file/directory It finnaly ends with the... (6 Replies)
Discussion started by: IgnitedMind
6 Replies

7. UNIX and Linux Applications

/usr/bin/ld: cannot find -lz error

I am installing lxml module for python on redhat I have installed libxml2 already. When I run for libxslt: ./configure --prefix=libxslt_folder --with-libxml-prefix=libxml2_folder It is ok the I run : make I have error: /usr/bin/ld: cannot find -lz collect2: ld returned 1 exit status I... (4 Replies)
Discussion started by: AIX_30
4 Replies

8. BSD

FreeBSD: /usr/bin/ld not looking in /usr/local/lib

I'm not sure if this is the default behavior for the ld command, but it does not seem to be looking in /usr/local/lib for shared libraries. I was trying to compile the latest version of Kanatest from svn. The autorgen.sh script seems to exit without too much trouble: $ ./autogen.sh checking... (2 Replies)
Discussion started by: AntumDeluge
2 Replies

9. Shell Programming and Scripting

Getting error: /usr/bin/env: ruby: No such file or directory

Hi, I installed ruby using rvm with root user on Linux. Now i m trying the below command as a non root user with sudo privileges. sudo /usr/local/rvm/rubies/ruby-2.2.5/bin/gem install passenger I get the below error: I had even reset the path for both gem as well as ruby as you... (8 Replies)
Discussion started by: mohtashims
8 Replies
dput.cf(5)							File Formats Manual							dput.cf(5)

NAME
dput.cf - Debian package upload tool configuration file DESCRIPTION
This manpage gives a brief overview of dput's configuration file and the available options in it. dput is a tool to upload Debian packages to the archive. FORMAT
dput.cf consists of different groups of configuration options, one for each host where you want to be able to upload packages. Hosts are defined using an identifier header with a short name for the host, enclosed in square brackets. Note that only if multiple such headers are encountered in the configuration, only the group following the last header is considered. This is done to avoid confusion when overrid- ing a global configuration file with a user-specific one. There's a special identifier, [DEFAULT], which holds default parameters for all the hosts. The defaults can be overridden by redefining them again in each host section. The available parameters are listed below: fqdn This is the fully qualified domain name that will be used (can be specified as host:port for HTTP, HTTPS and FTP). login Your login on the machine named before. A single asterisk * will cause the scp and rsync uploaders to not use supply a login name when calling to ssh, scp, and rsync. incoming The directory that you should upload the files to. method The method that you want to use for uploading the files. Currently, dput accepts the following values for method: ftp the package will be uploaded via ftp, either anonymously or using a login/password. Note that ftp is unencrypted so you should not use password authentication with this. http and https the package will be uploaded via http or https using the PUT method as specified in WebDAV. The upload method will prompt for a password if necessary. scp the package will be uploaded using ssh's scp. This transfers files using a secure ssh tunnel, and needs an account on the upload machine. rsync the package will be uploaded using rsync over ssh. This is similar to scp, but can save some bandwidth if the destination file already exists on the upload server. It also needs a login on the remote machine as it uses ssh. local the package will be "uploaded" locally using /usr/bin/install. This transfers files to a local incoming directory, and needs appropriate permissions set on that directory. hash The hash algorithm that should be used in calculating the checksum of the files before uploading them. Currently, dput accepts the following values for hash: md5 use the md5 algorithm for calculation sha use the sha algorithm for calculation allow_unsigned_uploads This defines if you are allowed to upload files without a GnuPG signature to this host or not. allow_dcut This defines if you are allowed to upload a dcut changes file to the queue to remove or move files. distributions This defines a comma-separated list of distributions that this host accepts, used to guess the host to use when none is given on the command line. allowed_distributions A regular expression (of Python re module syntax) that the distribution field must match or dput will refuse the upload. delayed Set a numeric default parameter for delayed uploads (i.e. uploads to this queue will be delayed the specified number of days. Defaults to the empty string, meaning no delay. This only works with upload queues that support delayed uploads. run_lintian This option defines if lintian should be run before the package will be uploaded or not. If the package is not lintian clean, the upload will not happen. run_dinstall This options defines if dinstall -n should be run after the package has been uploaded or not. This is an easy way to test if your package would be installed into the archive or not. check_version This option defines if dput should check if the user has installed the package in his system for testing it before putting it into the archive. If the user has not installed and tested it, dput will reject the upload. passive_ftp This option defines if dput should use passive ftp or active ftp for uploading a package to one of the upload queues. By default, dput uses passive ftp connections. If you need to use active ftp connections, set passive_ftp to 0. progress_indicator This integer option defines if dput should display a progress indicator for the upload. (Currently implemented in ftp only.) Supported values: 0 (default) - no progress, 1 - rotating progress indicator, and 2 - kilobyte counter. scp_compress This option defines if the scp upload to the host will be compressed, or not. This option is only used for the 'scp' upload method, and has been found to decrease upload time for slow links, and increase upload times for faster links. ssh_config_options The arguments of this config options should be ssh config file options in the style documented in ssh_config(5). They will be passed to all automatic invocations of ssh and scp by dput. Note that you can define multiline (dput) configuration options by indenting the second line with whitespace (i.e. similar to RFC822 header continuations). post_upload_command This option defines a command to be run by dput after a successful upload. pre_upload_command This option defines a command to be run by dput before a upload happens. default_host_main This defines the default host for packages that are allowed to be uploaded to the main archive. This variable is used when guessing the host to upload to. BUGS
Please send bug reports to the author. FILES
/etc/dput.cf global dput configuration file ~/.dput.cf peruser dput configuration file AUTHOR
Christian Kurz. Updated by Thomas Viehmann <tv@beamnet.de>. Many other people have contributed to this code. See the Thanks file. SEE ALSO
dput(1) /usr/share/doc/dput COMMENTS
The author appreciates comments and suggestions from you, if any. April 8, 2001 dput.cf(5)
All times are GMT -4. The time now is 07:38 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy