I am using command substitution into a find command in a script where I have built a menu to do a bunch of tasks within my unix account. When I choose the options for to find a file/files that have the same inode of the entered filename, ie hardlinks, nothing shows up. When I choose the appropiate... (2 Replies)
Q1: Let's say I create a hard-link bar.c in /tmp to a file foo.c which resides in /var/tmp. Is there a easy way to find out which file /tmp/bar.c hardlinks to (and vice-versa - i.e which files have got hard-linked from /var/tmp/foo.c) when one does not (and wants to) know the location of the other... (0 Replies)
Hello,
I got an IHS 6.1 installed and want to publish a directory with an index of files, directories and symlinks / symbolic links / soft links, last ones being created with the usual Unix command "ln -s .... ....".
In httpd.conf I've tried following for that directory:
Options Indexes... (1 Reply)
Hi :-)
i have a dump of a backupdisk (~540GB / ext3). The Backups have some 100 millions of hardlinks (backups are created with storeBackup). The OS is linux.
A restore of a directory ended after some days with the errormessage "no memory to extend symbol table"
The restore of the complete... (0 Replies)
Hi
I want to create softlinks, my source files and folders are placed in one server(hostname: info-1) and i want to access those files from different host(hostname :info-2).
file and folder names in info-1 host.
file1
folder1
Thanks,
Mallik. (1 Reply)
I have a pen drive1 with UFS file system and it has 43G used. It has a hell lot of soft links to other files which are located in a second pen drive2. We partitioned the file system on sun sparc machine, such that / has around 150G space.Now when we are copying the files from pen drive 1 to / on... (3 Replies)
Discussion started by: crackperl
3 Replies
LEARN ABOUT MINIX
test
TEST(1) General Commands Manual TEST(1)NAME
test, [ - test for a condition
SYNOPSIS
test expr
[ expr ]
OPTIONS
(none)
EXAMPLES
test -r file # See if file is readable
DESCRIPTION
Test checks to see if files exist, are readable, etc. and returns an exit status of zero if true and nonzero if false. The legal operators
are
-r file true if the file is readable
-w file true if the file is writable
-x file true if the file is executable
-f file true if the file is not a directory
-d file true if the file is a directory
-s file true if the file exists and has a size > 0
-t fd true if file descriptor fd (default 1) is a terminal
-z s true if the string s has zero length
-n s true if the string s has nonzero length
s1 = s2 true if the strings s1 and s2 are identical
s1 != s2 true if the strings s1 and s2 are different
m -eq m true if the integers m and n are numerically equal
The operators -gt, -ge, -ne, -le, and -lt may be used as well. These operands may be combined with -a (Boolean and), -o (Boolean or), !
(negation). The priority of -a is higher than that of -o. Parentheses are permitted, but must be escaped to keep the shell from trying to
interpret them.
SEE ALSO expr(1), sh(1).
TEST(1)