I'm trying to use Perl on Windows (Doh!) to connect to a folder on a Domain Controller via UNC.
Right now, I have
perl -e "`runas /user:DOMAIN\\Username dir \\\\SERVER\\d\$\\Path`"
This does not seem to connect nor does it prompt for password. Should I try throwing it into a script and... (0 Replies)
Is there a way for a server to determine client's DNS ip? I have an application that logs client's IP but in certain cases its desirable to know their DNS too (1 Reply)
Hi ,
I want to connect srver to pertuculat mode(i.e.srvrmanger)and after that I want to verify status of perticular component(i.e.CommOutboundMgr)
For that I have created following script bout after 3rd line it is not executing 4th linei.e. list comp CommOutboundMgr.
cd... (2 Replies)
Hello,
I searched the forums and didn't see a situation like this:
I cannot figure out how to parse out just the file name from the full path. The path looks like this:
\\foo\bar\filename.ext
I don't think something like 'cut' will work so I tried to whip up a regex but couldn't get it... (12 Replies)
Hi Folks,
Trying to build up a script that will lookup a username invoked as:
./buildscript.sh <username>
This should take <username> and look it up in <username_file> and prepare for further processing. Here is the snippet that isn't working just right:
user=$1
if ]; then
echo... (1 Reply)
Hello All :)
I want to write a shell script to find the file system usage on multiple UNIX servers.
Commands: df -g fsJCAPS
Below script works fine and it displays results on terminal/console. I want to store /redirect output on to local server from where I'm running the script.
... (3 Replies)
Need help with the script, I am trying to include this script as part of kickstart profile.
based of the host's IP address, in this case if the host is IP starting with 10.10.3.* or 10.10.6.*, I will be pushing appropriate routing file from my web server.
I validate host IP from nslookup.
... (3 Replies)
Discussion started by: bobby320
3 Replies
LEARN ABOUT OSX
symlink
SYMLINK(2) BSD System Calls Manual SYMLINK(2)NAME
symlink -- make symbolic link to a file
SYNOPSIS
#include <unistd.h>
int
symlink(const char *path1, const char *path2);
DESCRIPTION
A symbolic link path2 is created to path1 (path2 is the name of the file created, path1 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.
RETURN VALUES
Upon successful completion, a zero value is returned. If an error occurs, the error code is stored in errno and a -1 value is returned.
ERRORS
The symbolic link succeeds unless:
[EACCES] Write permission is denied in the directory where the symbolic link is being created.
[EACCES] A component of the path2 path prefix denies search permission.
[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.
[EEXIST] Path2 already exists.
[EFAULT] Path1 or path2 points outside the process's allocated address space.
[EIO] An I/O error occurs while making the directory entry or allocating the inode.
[EIO] An I/O error occurs while making the directory entry for path2, or allocating the inode for path2, or writing out the link
contents of path2.
[ELOOP] Too many symbolic links are encountered in translating the pathname. This is taken to be indicative of a looping symbolic
link.
[ENAMETOOLONG] A component of a pathname exceeds {NAME_MAX} characters, or an entire path name exceeds {PATH_MAX} characters.
[ENOENT] A component of path2 does not name an existing file or path2 is an empty string.
[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 there is no space left on the file system that will contain the sym-
bolic link.
[ENOSPC] There are no free inodes on the file system on which the symbolic link is being created.
[ENOTDIR] A component of the path2 prefix is not a directory.
[EROFS] The file path2 would reside on a read-only file system.
SEE ALSO ln(1), link(2), unlink(2), symlink(7)HISTORY
The symlink() function call appeared in 4.2BSD.
4.2 Berkeley Distribution June 4, 1993 4.2 Berkeley Distribution