path1 is defined and it is a directory path
path1 is defined and it is a directory path
var1 is defined and it holds string value
Basically i did not understand the importance of /*,*
Moderator's Comments:
Please use code tags next time for your code and data. Thanks
It is nice that you told us (twice) that $path1 expands to a directory path. It would be nice if you told us how path2 is defined. I don't understand why you're saying that you do not understand the importance of /*,* since that string does not appear anywhere in the assignment statement you showed us???
Presumably after you go to the effort to define the variable result you use it somewhere later in your code. How is it used?
The echo RudiC suggested might not help much since the string is quoted in the definition and unquoted in the echo.
Couple of questions as I try to decipher someones code who left...
What would something coded like this do?
IFS=:
grep FIELD1 /Path/Path2/Param.fle | read LBL1 LBL2 USRID EADR SUBJ SERVERNAME CFGTBL DIR
ERR=0
Param.fle contents..
FIELD1:FEI::FIELD2:dATAFIELD BATCH:MAIN SERVER......etc.. (2 Replies)
Can any body explains the under given lines of code i have difficulties in understanding it,
my $errorlog = "/var/log/controler.log";
&initLanguage($language);
&launchCbox();
sub launchCbox { ... (1 Reply)
I am really new to UNIX and programming in general and so apologies if this thread is a bit simple.
I have searched and found a piece of sample code for a training program I am currently undertaking, but seeing as I am relatively new, I dont completely understand how it works.
Here is the... (1 Reply)
hello all,
May i know what is this "DEBUG_ME $DEBUG_CMD main" doing in the below code. I am confused with alias also "alias DEBUG_ME='#'". Thanks for your help.
set -x
alias DEBUG_ME='#'
if ; then
. /product/apps/informatica/v7/pc/ExtProc/debug.ksh "$1"
fi
# Declaring the... (1 Reply)
This is the command. Assume file1 exists but file2 does not:
ls file1 file2 >newfile 2>&1
This simply makes a text file with two lines: file1 \n file2 could not be found. What I don't understand is that when you run this command: ls file1 file2 >newfile, it prints "file2 could not be found" to... (1 Reply)
Well, I found myself trying to fix some Perl code (Ive never done any Perl in my life) and I pinpointed the place where the bug could be. But to be sure I have to know what does a few line of code mean:
$files_lim =~ (/^\d*$/)
$files_lim =~ (/^\d*h$/)$files_age =~ s/h//The code where this was... (0 Replies)
What is the difference between the two statements below?
A:
$a->{"$fruit"}->{"$color"}->{size} = $size
B:
$size = $a->{"$fruit"}->{"$color"}->{size}
Please assist. Thanks! (0 Replies)
Hi,
I need to understand below perl code, can some one advise me.
perl -MDate::Parse -e'BEGIN{$main::now=time;$main::old=(time-60*30)}' -nE'if(/^(\w+\s+\d+\s+\d+:\d+:\d+)/) {$t=str2time $1; $t > $old && $t < $now && print}' (1 Reply)
As the title suggests, I want to better understand the following assembly code:
section .text
global main ; must be declared for linker (gcc)
main: ; tell linker entry point
mov edx, len ; message length
mov ecx, msg ; message to write... (2 Replies)
Hello... and thanks in advance for reading this or offering me any assistance
I'm trying to understand specific differences between the various login scripts... I understand the differences between interactive vs non-interactive and login vs non-login shells... and that's not where my question... (4 Replies)
Discussion started by: bodisha
4 Replies
LEARN ABOUT OSF1
link
link(2) System Calls Manual link(2)NAME
link - Creates a hard link to an existing file on the local file system
SYNOPSIS
#include <unistd.h>
int link ( const char *path1, const char *path2 );
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
link(): XSH5.0
Refer to the standards(5) reference page for more information about industry standards and associated tags.
PARAMETERS
Points to the pathname of an existing file. Points to the pathname for the directory entry to be created. If the path2 parameter names a
symbolic link, an error is returned.
DESCRIPTION
The link() function creates an additional hard link (directory entry) for an existing file. The old and the new link share equal access
rights to the underlying object. The link() function atomically creates a new link for the existing file and increments the link count of
the file by one.
Both the path1 and path2 parameters must reside on the same file system. A hard link to a directory cannot be created.
Upon successful completion, the link() function marks the st_ctime field of the file for update, and marks the st_ctime and st_mtime fields
of the directory containing the new entry for update.
A process must have write permission in the target directory with respect to all access control policies configured on the system.
See symlink(2) for information about making symbolic links, including Context Dependent Symbolic Links (CDSLs).
RETURN VALUES
Upon successful completion, the link() function returns a value of 0 (zero). If the link() function fails, a value of -1 is returned, no
link is created, and errno is set to indicate the error.
ERRORS
If the link() function fails, errno may be set to one of the following values: The requested link requires writing in a directory with a
mode that denies write permission, or a component of either the path1 or path2 parameter denies search permission. The requested link
requires writing in a directory to which the process does not have write access with respect to one or more of the system's configured
access policies. The directory in which the entry for the new 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. The link named by the path2 parameter already exists. The path1 or
path2 parameter is an invalid address. [Tru64 UNIX] An I/O error occurred when updating the directory. Too many links were encountered in
translating path1 or path2. The number of links to the file named by path1 would exceed LINK_MAX. The length of the path1 or path2 string
exceeds PATH_MAX or a pathname component is longer than NAME_MAX. The file named by the path1 parameter does not exist or the path1 or
path2 parameter is an empty string. The directory in which the entry for the new link is being placed cannot be extended because there is
no space left on the file system containing the directory. A component of either path prefix is not a directory. The file named by the
path1 parameter is a directory. The requested link requires writing in a directory on a read-only file system. The link named by the
path2 parameter and the file named by the path1 parameter are on different file systems.
[Tru64 UNIX] For NFS file access, if the link() function fails, errno may also be set to one of the following values: Indicates that the
system file table is full or there are too many files currently open in the system. Indicates a stale NFS file handle. An opened file was
deleted by the server or another client; a client cannot open a file because the server has unmounted or unexported the remote directory;
or the directory that contains an opened file was unmounted or unexported by the server.
RELATED INFORMATION
Commands: link(1), unlink(1)
Functions: unlink(2), symlink(2)
Standards: standards(5) delim off
link(2)
11-17-2014
