I ran into the following and still do not understand entirely the rationale behind this. If someone could explain why things are as they are I'd be thankful.
The following was tested on AIX 7.1 with ksh88, but i suspect that to be ubiquitous. In an installation routine i had to create a set of symbolic links. Because they might already exist i used test -e filename to test it:
This didn't work as expected because test returned 0 only if the link AND its target existed. If only the link exists but not the file referenced by it test will return 1.
A "file that exists" is IMHO covered by a link, even if this link points to a file which doesn't. I can stat() this file and do many other operations on it which can be done with a file.
I do understand that i can use "-L", which tests for a link but i would like to understand the rationale behind the behavior. Or is the POSIX documentation inconsistent here?
Hi all,
I am getting "test:argument expected" error in the following script
LOGDIR=$XXAR_TOP/log
PROGRAM_NAME=XXAR_GPS_LBFDMSGEN
..
..
..
Check_Errors()
{
sqllogfile=$1
cd ${LOGDIR}
countfile=${LOGDIR}/${PROGRAM_NAME}.tmp
echo "countfile is " $countfile >> $LOGFILE
echo... (4 Replies)
Can someone help me with a very simple query
I have the following script:
#!/bin/sh
VAR1=""
if
then
VAR1="Message"
fi
echo $VAR1
put when i run it i get the following error
test_job.sh: test: argument expected (5 Replies)
I'm newbie to coding script so i found test: argument expected when i run it. please help me
a=`df -k |awk '{print $5 }'|egrep "(100%|%)"|cut -d"%" -f1|tail -1`
if
then
df -k|egrep "(100%|%)"|awk '{print $1,$5,$6}'
else
echo "No disk capacity more than 80%"
fi
thk in advance (7 Replies)
+
test.sh: test: argument expected
#!/bin/bash
if
then
echo thennnn
else
echo elseeee
fi
why does it show this error? Clearly from debug mode, the argument is passed. I also tried if
Run on Solaris 9.
Thanks (10 Replies)
Hello folks,
I've got this script which runs perfectly when i run it manually. But when i am running it from a crontab i am getting an error saying
test argument expected.
The line from where it is coming is something like this:
if
then
do something
fi
Any idea why? (2 Replies)
Hi,
Since i am new to Unix and on suggestion on some smart guys on unix... i have decide to learn more deeply on Unix...so i was kind of playing with if statements and found this error... though i tried to correct is for hours now i couldnt find whats wrong in my loop.
if
then
... (4 Replies)
# to search a file if it exists and whether its readable or not
# if yes print its first 5 lines
echo enter the filename to be searched
read fname
if #-d $fname
then
echo file doesn exists
elif
then
echo its a directory
elif
then
cat $fname
else
echo its not readable
fi
# end of... (9 Replies)
Hello all,
I am trying to figure out why i am getting an error while executing the script...altought it seems like its work...but still get the test arguement error...any help would be appericiate...this script basically connects to any oracle db ( just have to pass db name to it)... (4 Replies)
check_build_info_table()
{
if
then
export build_info_table=`sqlplus -s sna/dbmanager <<!
set pagesize 0 heading off feedback off
SELECT DISTINCT TABLE_NAME FROM ALL_TABLES WHERE OWNER = 'XYZ' AND TABLE_NAME = 'MY_TABLE';
exit
!`
... (3 Replies)
The following example prompts are passed into the shell script.
$1 = /tmp/dir/
$2 = varies (test.txt, test1.txt, test2.txt...)
$3 = test_YYYYMMDD.txt
---------------------------------------------------------------------------
#!/bin/sh
cd $1
if ; then
if ; then
... (3 Replies)
Discussion started by: smkremer
3 Replies
LEARN ABOUT NETBSD
ln
LN(1) BSD General Commands Manual LN(1)NAME
ln -- make links
SYNOPSIS
ln [-fhinsv] source_file [target_file]
ln [-fhinsv] source_file ... target_dir
DESCRIPTION
The ln utility creates a new directory entry (linked file) which has the same modes as the original file. It is useful for maintaining mul-
tiple copies of a file in many places at once without using up storage for the ``copies''; instead, a link ``points'' to the original copy.
There are two types of links: hard links and symbolic links. How a link ``points'' to a file is one of the differences between a hard or
symbolic link.
The options are as follows:
-f Unlink any already existing file, permitting the link to occur.
-h If the target_file or target_dir is a symbolic link, do not follow it. This is most useful with the -f option, to replace a symlink
which may point to a directory.
-i Cause ln to write a prompt to standard error if the target file exists. If the response from the standard input begins with the char-
acter 'y' or 'Y', then unlink the target file so that the link may occur. Otherwise, do not attempt the link. (The -i option over-
rides any previous -f options.)
-n Same as -h, for compatibility with other ln implementations, namely GNU coreutils.
-s Create a symbolic link.
-v Cause ln to be verbose, showing files as they are processed.
By default ln makes hard links. A hard link to a file is indistinguishable from the original directory entry; any changes to a file are
effective independent of the name used to reference the file. Hard links may not normally refer to directories and may not span file sys-
tems.
A symbolic link contains the name of the file to which it is linked. The referenced file is used when an open(2) operation is performed on
the link. A stat(2) on a symbolic link will return the linked-to file; an lstat(2) must be done to obtain information about the link. The
readlink(2) call may be used to read the contents of a symbolic link. Symbolic links may span file systems and may refer to directories.
Given one or two arguments, ln creates a link to an existing file source_file. If target_file is given, the link has that name; target_file
may also be a directory in which to place the link; otherwise it is placed in the current directory. If only the directory is specified, the
link will be made to the last component of source_file.
Given more than two arguments, ln makes links in target_dir to all the named source files. The links made will have the same name as the
files being linked to.
SEE ALSO link(2), lstat(2), readlink(2), stat(2), symlink(2), symlink(7)STANDARDS
The ln utility conforms to IEEE Std 1003.2-1992 (``POSIX.2'').
The -v option is an extension to IEEE Std 1003.2-1992 (``POSIX.2'').
HISTORY
A ln utility appeared in Version 6 AT&T UNIX.
BSD October 29, 2007 BSD