02-17-2010
Nothing in UNIX directly supports it. You need to use the open-source Mono interpreter. I'm not sure if it's available for AIX or not, it originated on Linux. Even then, it's efficacy is hard to guarantee.
Realistically, if you want to write UNIX scripts, C# is the last language you'd ever want to use. It's about as portable as a depleted uranium garden gnome.
10 More Discussions You Might Find Interesting
1. AIX
wondering if there are any opportunities to learning AIX on regular hardware :)
thanks,
manny (11 Replies)
Discussion started by: mr_manny
11 Replies
2. Shell Programming and Scripting
I am having an issue while trying to run the Net::SFTP module. I have been able to install this on several machines before but have never had this problem. When I am running a simple script to test the sftp it dies but does not trigger the print statement for my error. The last line is in red.
... (0 Replies)
Discussion started by: kofs79
0 Replies
3. UNIX for Advanced & Expert Users
Hi Guys
Am new in UNIX environment I was asked by my boss to write a program that transfer files from the AIX server to the Wintel Server. I have written the program in C# windows which does almost the same thing. So how to run the C# program in UNIX? (1 Reply)
Discussion started by: michmsk
1 Replies
4. Windows & DOS: Issues & Discussions
I have a .NET application that remotely starts, stops, and gets status of Windows services and scheduled tasks. I would like to add the capability of starting, stopping, and getting status of remote AIX applications also. Based on some preliminary research, one option may be to use 3rd party .NET... (0 Replies)
Discussion started by: auser1
0 Replies
5. UNIX for Dummies Questions & Answers
I have an application I wrote that is designed to run on a windows system but now starting to think I would rather be using Unix. Would the application have to be 100% rewritten to work on unix, or is there something I could install that would allow me to run my .NET application inside unix? (2 Replies)
Discussion started by: redbrad0
2 Replies
6. UNIX for Dummies Questions & Answers
Hi All,
I've wrote a script to truncate newline characters in a text file. Could you please help me in figuring out the issue
:confused:
for file in $Filelist; do
echo $file;
FileName=`basename $file`;
sed 's/^M//g' $file> "${file}"2;
mv "${file}"2 "${file}";
sed '1d' "${file}"... (5 Replies)
Discussion started by: udayakumar
5 Replies
7. AIX
Hello, I am experiencing a problem trying to use the GNU gdb debugger on my AIX 6.1 system, as follows:
$ gdb
exec(): 0509-036 Cannot load program powerpc64-ibm-aix6.1.2.0-gdb because of the following errors:
0509-130 Symbol resolution failed for powerpc64-ibm-aix6.1.2.0-gdb... (1 Reply)
Discussion started by: Clovis_Sangrail
1 Replies
8. AIX
Requirement is to monitor cpu usage /process for a user given time and record the output. topas,topasout,topasrec,tprof not seems to be working for me. so what i am looking for is to run below command continously till the time limit given by the user who runs the script.since below command is a one... (6 Replies)
Discussion started by: NarayanaPrakash
6 Replies
9. AIX
hi guys
We have a AIX Server with TSM installed.
This server has en0 for administration purposes and we have en1 for backup stuff.
en0 subnet 10.10.10.x
en1 subnet 10.10.20.x
The issue we are having is all of a sudden the LPARs we are backing up lose connectivity to the AIX-TSM Server.... (23 Replies)
Discussion started by: karlochacon
23 Replies
10. AIX
1)We have 2 node cluster RAC on AIX:
->test1
->test3
2) After rebooting server both the node sequentailly, we are getting below error from errpt command :
# errpt |more
IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION
FE2DEE00 0901223914 P S SYSXAIXIF DUPLICATE IP ADDRESS... (2 Replies)
Discussion started by: manjusharma128
2 Replies
LN(1) BSD General Commands Manual LN(1)
NAME
link, ln -- make links
SYNOPSIS
ln [-Ffhinsv] source_file [target_file]
ln [-Ffhinsv] source_file ... target_dir
link source_file target_file
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 and
symbolic link.
The options are as follows:
-F If the target file already exists and is a directory, then remove it so that the link may occur. The -F option should be used with
either -f or -i options. If none is specified, -f is implied. The -F option is a no-op unless -s option is specified.
-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.
-f If the target file already exists, then unlink it so that the link may occur. (The -f option overrides any previous -i options.)
-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.
-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
effectively 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.
When the utility is called as link, exactly two arguments must be supplied, neither of which may specify a directory. No options may be sup-
plied in this simple mode of operation, which performs a link(2) operation using the two passed arguments.
COMPATIBILITY
The -h, -i, -n and -v options are non-standard and their use in scripts is not recommended. They are provided solely for compatibility with
other ln implementations.
The -F option is FreeBSD extention and should not be used in portable scripts.
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 simplified link command conforms to Version 2 of the Single UNIX Specification (``SUSv2'').
HISTORY
An ln command appeared in Version 1 AT&T UNIX.
BSD
February 14, 2006 BSD