Sponsored Content
Full Discussion: Error using scpg3
Top Forums UNIX for Dummies Questions & Answers Error using scpg3 Post 302754817 by drew_1980 on Friday 11th of January 2013 06:58:15 AM
Old 01-11-2013
Error using scpg3

Hello,

I installed Tectia client version 6.2.4.212 on our unix boxes. sftpg3 works for the users and what not, however when they try to use the scpg3 command to pull or place folders/directories from one box to another, they receive this error:

Code:
# scpg3 –rp user@unixboxname:/directory/directory/directory/ /directory/directory

error: File `/directory/directory/' is a directory, and directory creation (recursion) has not been enabled.

Does anyone know how to enable this so that users will be able too?

Moderator's Comments:
Mod Comment Please use code tags next time for your code and data.

Last edited by vbe; 01-11-2013 at 10:08 AM.. Reason: rm fancy fonts... + added code tags
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Error: Internal system error: Unable to initialize standard output file

Hey guys, need some help. Running AIX Version 5.2 and one of our cron jobs is writing errors to a log file. Any ideas on the following error message. Error: Internal system error: Unable to initialize standard output file I'm guessing more info might be needed, so let me know. Thanks (2 Replies)
Discussion started by: firkus
2 Replies

2. UNIX for Dummies Questions & Answers

awk Shell Script error : "Syntax Error : `Split' unexpected

hi there i write one awk script file in shell programing the code is related to dd/mm/yy to month, day year format but i get an error please can anybody help me out in this problem ?????? i give my code here including error awk ` # date-month -- convert mm/dd/yy to month day,... (2 Replies)
Discussion started by: Herry
2 Replies

3. UNIX for Advanced & Expert Users

VSI-FAX error - Cannot login to server and Connecto error to host

I encounters a VSIFAX related error: vfxstat: Cannot login to server on rsac3: Connect error to host 172.16.1.45: Invalid argument It started happening last night with a core dump. Then we can't start VSIFAX again. I am runing VSI-FAX 4.2 on AIX box (0 Replies)
Discussion started by: b_jin
0 Replies

4. 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

5. UNIX for Advanced & Expert Users

ssh error: Error reading response length from authentication socket

Hi - I am getting the error `Error reading response length from authentication socket' when I ssh from my cluster to another cluster, and then back to my cluster. It doesn't seem to affect anything, but it's just annoying that it always pops up and tends to confuse new users of the cluster. I... (1 Reply)
Discussion started by: cpp6f
1 Replies

6. UNIX for Dummies Questions & Answers

> 5 ")syntax error: operand expected (error token is " error

im kinda new to shell scripting so i need some help i try to run this script and get the error code > 5 ")syntax error: operand expected (error token is " the code for the script is #!/bin/sh # # script to see if the given value is correct # # Define errors ER_AF=86 # Var is... (4 Replies)
Discussion started by: metal005
4 Replies

7. Solaris

Rpcinfo: can't contact portmapper: RPC: Authentication error; why = Failed (unspecified error)

I have two servers with a fresh install of Solaris 11, and having problems when doing rpcinfo between them. There is no firewall involved, so everything should theoretically be getting through. Does anyone have any ideas? I did a lot of Google searches, and haven't found a working solution yet. ... (2 Replies)
Discussion started by: christr
2 Replies

8. Shell Programming and Scripting

IF section problem. syntax error: unexpected end of file error

Hello, I have another problem with my script. Please accept my apologies, but I am really nooby in sh scripts. I am writing it for first time. My script: returned=`tail -50 SapLogs.log | grep -i "Error"` echo $returned if ; then echo "There is no errors in the logs" fi And after... (10 Replies)
Discussion started by: jedzio
10 Replies

9. UNIX for Beginners Questions & Answers

Print Error in Console and both Error & Output in Log file - UNIX

I am writing a shell script with 2 run time arguments. During the execution if i got any error, then it needs to redirected to a error file and in console. Also both error and output to be redirected to a log file. But i am facing the below error. #! /bin/sh errExit () { errMsg=`cat... (1 Reply)
Discussion started by: sarathy_a35
1 Replies
TMAIL(1)						      General Commands Manual							  TMAIL(1)

NAME
tmail - Mail Delivery Module SYNOPSIS
tmail [-b format] [-D] [-f from_name] [-I inbox_specifier] user[+folder] ... DESCRIPTION
tmail delivers mail to a user's INBOX or a designated folder. tmail may be configured as a drop-in replacement for binmail(1), mail.local(1) or any program intended for use for mail delivery by a mail delivery program such as sendmail(8). tmail is intended to be used for direct delivery by the mailer daemon; dmail(1) is the preferred tool for user applications, e.g. a mail delivery filter such as procmail(1). If tmail is used for a user application, then the calling program must be aware of the restrictions noted below. When tmail exits, it returns exit status values to enable the mail delivery program to determine whether a message was delivered successfully or had a temporary (requeue for later delivery) or permanent (return to sender) failure. If the +folder extension is included in the user argument, tmail will attempt to deliver to the designated folder. If the folder does not exist or the extension is not included, the message is delivered to the user's INBOX. If delivery is to INBOX and no INBOX currently exists, tmail will create a new INBOX, using the -I or -b flag if specified. tmail recognizes the format of an existing INBOX or folder, and appends the new message in that format. The -b flag specifies a format to create INBOX if INBOX does not already exist. This flag requires privileges, and can not be used with -I. The argument is a format name such as mix, mbx, etc. The -D flag specifies debugging; this enables additional message telemetry. The -f or -r flag is used by the mail delivery program to specify a Return-Path. The header Return-Path: <from_name> is prepended to the message before delivery. The -I flag is used by the mail delivery program to specify an alternative INBOX name. This flag requires privileges, and can not be used with -b. This affects the location and format of INBOX. If specified, it should be in one of three forms: The first form of argument to -I is the string "INBOX", which means to write to the system default inbox using the system default mailbox format. These system defaults are defined when the c-client library is built. The second form of argument to -I is a delivery specification, consisting of "#driver.", a c-client mailbox format driver name, "/", and a file name. This will write to the specified file in the specified format. For example, #driver.mbx/INBOX will write to file "INBOX" in the home directory in mbx format; and #driver.unix/mail/incoming will write to file "incoming" in the user's "mail" subdirectory in unix (default UNIX) format. The third form of argument to -I is any other name. Normally, this will write to the specified file on the user's home directory in the specified format. However, certain names are special. These are: value equivalant to ----- ------------- INBOX.MTX #driver.mtx/INBOX.MTX mbox #driver.unix/mbox mail.txt #driver.tenex/mail.txt If -I is not specified, the default action is -I INBOX. If multiple recipients are specified on the command line, tmail spawns one child process per recipient to perform actual delivery. This way of calling tmail is not recommended; see below under RESTRICTIONS. INSTALLATION
If tmail is to be used for mail delivery from the mail delivery program, it must be installed setuid root. If sendmail is the mail delivery program, tmail is invoked from sendmail.cf. Look for the "Mlocal" line, and substitute the path name for the tmail binary in place of /bin/mail, /usr/lib/mail.local, etc. You should also add the flag to invoke tmail with CRLF style newlines; this is usually done with E= in the Mlocal line. Here is an example of an Mlocal line in sendmail version 8: Mlocal, P=/usr/local/etc/tmail, F=lsDFMAw5:/|@qPrn+, S=10/30, R=20/40, E= , T=DNS/RFC822/X-Unix, A=tmail $u If tmail is to be called with the -I flag, it must be invoked with both real and effective UID root. Many sendmail configurations invoke the local mailer as the sending user when that user is local, which will prevent -b or -I from working. SECURITY CONSIDERATIONS
If tmail is invoked by an ordinary user, the Received: header line will indicate the name or UID of the user that invoked it. Ordinary users are not permitted to use the -b or -I flag since otherwise a user could create any file on another user's directory. tmail can deliver mail to home directories. In addition, tmail can be used to deliver mail to other mail folders in a home directory or an inferior directory of a home directory. RESTRICTIONS
The calling program should invoke tmail with CRLF newlines, otherwise tmail will complain in syslog. Absolute pathnames and ~user specifications are not permitted in +folder extensions. Ordinary users are not permitted to use the -I flag. IMAP4 namespace names are not yet supported in +folder extensions. It is not possible to use tmail to deliver to mh(1) format mailboxes. If delivery to multiple users is specified and delivery to any single user fails, the entire delivery will be reported as having failed, even though delivery to other users may have succeeded. If tmail is used for mail delivery from sendmail(8), a separate tmail invocation should be done for each user. Otherwise a delivery failure for a single user in a message going to multiple users will cause multiple deliveries to all the other users every time sendmail(8), retries. AUTHOR
Mark Crispin, MRC@CAC.Washington.EDU SEE ALSO
binmail(1) sendmail(8) September 27, 2007 TMAIL(1)
All times are GMT -4. The time now is 04:24 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy