Lose the trailing space character on the ftp line ! It's the space character after the EOF .
In fact you have quite a lot of lines with spurious trailing spaces.
To spot them I typed
Hi,
I need ur help is this matter, i have th ebelow script, and i keep getting this error: syntax error: unexpected end of file
affectedRow=`cat dbOutput.log | grep "1 row affected"`
echo "affectedRow : $affectedRow"
if ; then
echo "Look to the next OMCDB"
... (10 Replies)
Hi All,
I have written a korn script (code pasted below). It is giving the error while debugging "new.sh: syntax error at line 62: `end of file' unexpected".
I have re-written the whole code in VI and explored all help related to this error on this Unix forum and tried it. Somehow, I could... (7 Replies)
I have a script that's failing
./zzmaster.sh: line 2: syntax error: unexpected end of file
There are 4 scripts total involved. The first 'znocc0.sh' essentially curls a page then does some sed sequences...
#!/bin/sh
#GET SENTINAL INFO
curl -b z0cookie.txt -L -k -e... (2 Replies)
Hi,
I have problem in constructing "IF" condition.
The below code throws "tst.sh: line 10: syntax error: unexpected end of file"
#!/bin/ksh
test=9
echo $test
if ]
then
echo "in"
fi
echo "end"
exit 0
Actually, i want to check whether the variable $test is empty or null.
... (5 Replies)
Hi,
I am newbie to UNIX scripting. I am facing this error "syntax error: unexpected end of file" while executing the following script:
------
a=$1
if
then
sqlplus -s prospect_stg/prospect_stg@mdmpt <<END
insert into bckup_marc_parameter_lookup select * from... (6 Replies)
I will appreciate help is this matter. i am getting this error (./getwind.scr: line 41: syntax error: unexpected end of file) in the following script :
##############################
#QSUB -eo -q sb -lT 1200 -s /bin/csh
#Run on an HP-UX machine or norway to access ncks
# lat and lon are in... (0 Replies)
I am new to unix, so thank u for ur patience
I try to make it work (to duplicate two first columns in several files):
#!/bin/bash
for i in `seq 2 5`
do
awk `{ print $1,$1,$2,$2,$3,$4}` final_chr.${i} > input_${i}
done
and i get
./my_script3.sh: command substitution: line 5: syntax... (2 Replies)
first of all I thought the argument DONE is necessary for all scripts that have or begin with do statements which I have on my script, However, I still don't completely understand why I am receiving an error I tried adding another done argument statement but didn't do any good.
I appreciate... (3 Replies)
I checked the forum and internet, tried different workaorunds but it didnt fixed the error.
Please advise on the code.
#!/bin/sh
CWD=/home/test/Bench
cd $CWD
(grep "`date +%d-%b"`" File.txt) > /home/test/Bench/dateout
if
then
echo “data” > /home/test/ Bench /test
else
echo "File... (16 Replies)
Hi,
I am brand new to this so I apologize ahead of time for any formatting problems.
I know there is a previous (closed) thread on here about this problem but I wasn't able to fix the error following the posts there so I thought I could create a new one.
Here is the error I am getting:
... (3 Replies)
Discussion started by: SierraG
3 Replies
LEARN ABOUT FREEBSD
symlink
SYMLINK(2) BSD System Calls Manual SYMLINK(2)NAME
symlink, symlinkat -- make symbolic link to a file
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <unistd.h>
int
symlink(const char *name1, const char *name2);
int
symlinkat(const char *name1, int fd, const char *name2);
DESCRIPTION
A symbolic link name2 is created to name1 (name2 is the name of the file created, name1 is the string used in creating the symbolic link).
Either name may be an arbitrary path name; the files need not be on the same file system.
The symlinkat() system call is equivalent to symlink() except in the case where name2 specifies a relative path. In this case the symbolic
link is created relative to the directory associated with the file descriptor fd instead of the current working directory. If symlinkat() is
passed the special value AT_FDCWD in the fd parameter, the current working directory is used and the behavior is identical to a call to
symlink().
RETURN VALUES
The symlink() function returns the value 0 if successful; otherwise the value -1 is returned and the global variable errno is set to indicate
the error.
ERRORS
The symbolic link succeeds unless:
[ENOTDIR] A component of the name2 path prefix is not a directory.
[ENAMETOOLONG] A component of the name2 pathname exceeded 255 characters, or the entire length of either path name exceeded 1023 charac-
ters.
[ENOENT] A component of the name2 path prefix does not exist.
[EACCES] A component of the name2 path prefix denies search permission, or write permission is denied on the parent directory of
the file to be created.
[ELOOP] Too many symbolic links were encountered in translating the name2 path name.
[EEXIST] The path name pointed at by the name2 argument already exists.
[EPERM] The parent directory of the file named by name2 has its immutable flag set, see the chflags(2) manual page for more infor-
mation.
[EIO] An I/O error occurred while making the directory entry for name2, or allocating the inode for name2, or writing out the
link contents of name2.
[EROFS] The file name2 would reside on a read-only file system.
[ENOSPC] The directory in which the entry for the new symbolic link is being placed cannot be extended because there is no space
left on the file system containing the directory.
[ENOSPC] The new symbolic link cannot be created because there is no space left on the file system that will contain the symbolic
link.
[ENOSPC] There are no free inodes on the file system on which the symbolic link is being created.
[EDQUOT] The directory in which the entry for the new symbolic link is being placed cannot be extended because the user's quota of
disk blocks on the file system containing the directory has been exhausted.
[EDQUOT] The new symbolic link cannot be created because the user's quota of disk blocks on the file system that will contain the
symbolic link has been exhausted.
[EDQUOT] The user's quota of inodes on the file system on which the symbolic link is being created has been exhausted.
[EIO] An I/O error occurred while making the directory entry or allocating the inode.
[EFAULT] The name1 or name2 argument points outside the process's allocated address space.
In addition to the errors returned by the symlink(), the symlinkat() may fail if:
[EBADF] The name2 argument does not specify an absolute path and the fd argument is neither AT_FDCWD nor a valid file descriptor
open for searching.
[ENOTDIR] The name2 argument is not an absolute path and fd is neither AT_FDCWD nor a file descriptor associated with a directory.
SEE ALSO ln(1), chflags(2), link(2), lstat(2), readlink(2), unlink(2), symlink(7)STANDARDS
The symlinkat() system call follows The Open Group Extended API Set 2 specification.
HISTORY
The symlink() system call appeared in 4.2BSD. The symlinkat() system call appeared in FreeBSD 8.0.
BSD April 10, 2008 BSD