10 More Discussions You Might Find Interesting
1. UNIX for Beginners Questions & Answers
We are using Solaris 11 Logical Domains. We NFS share a disk backup area from one LDom to other servers. The share is on a single 1.5 Tb LUN presented to the Control Domain, and as a virtual disk on the NFS server LDom. A 1.5 Tb zpool has been created on the LDom. We now need to provide more disk... (2 Replies)
Discussion started by: SallyB
2 Replies
2. Ubuntu
I have 1 Server which was installed With centos 6.2 and there was a Samba Share the Directory /public was shared in the centos Server, its IP address is 192.168.1.15 , And I Have accessed the Share in Ubuntu 12.04 client machines by connect to server just giving IP address and share folder name ,... (1 Reply)
Discussion started by: babinlonston
1 Replies
3. UNIX for Dummies Questions & Answers
Hello,
I would like to share a 9p (Plan 9) passthrough/share to a VM via NFS (using a guest as an NFS server to share a directory from the host)
At the moment I am getting the error message: 'exportfs: /share does not support NFS export'... (2 Replies)
Discussion started by: Scratch
2 Replies
4. UNIX for Dummies Questions & Answers
I am not sure is this plausible...
I have just built a NFS master server on a solaris box (secured by NIS)
And I have a dozen of virtual machines running 32 and 64 bits linux and windows, running different types of servers.
I am not sure is it possible to move most of the programs to the... (6 Replies)
Discussion started by: xstaci
6 Replies
5. Shell Programming and Scripting
Hi Forums,
I got a little problem, I made a few modifications to the code of the launch script of a testing server(minecraft) and now updating is broken aswell as the automatic directory creation.
These Lines somehow create an endless symlink that refers to itself and I don't know how to fix... (0 Replies)
Discussion started by: Xaymar
0 Replies
6. Solaris
Hi,
Not sure where to post this, I'm sorry and need suggestion if this is wrong section.
we are running NFS Server on Solaris 10 and client box is HP-UX 11.11 (Can't apply latest patches/upgrades as in-house appln. doesn't allow)
I am able to mount NFS shares from this Solaris box onto all... (4 Replies)
Discussion started by: prvnrk
4 Replies
7. Solaris
Hi
I have a problem with NFS sharing on solaris 10, the problem simply with write permission, after do the following command, the folder still not writable from machine 2 :
on machine 1 (10.10.10.32) :
share -F nfs -o rw /u01/portalrepository/
on machine 2 (10.10.10.31) :
mount -F nfs... (35 Replies)
Discussion started by: Al-Mothafar
35 Replies
8. High Performance Computing
I'm planning to load balance 2 web servers. I'm considering mounting an NFS share between the 2 servers so they can share the data. My question is: does this setup offset some of the benefits of load balancing? although there are 2 web servers, they both still access a single NFS server. Wouldn't... (2 Replies)
Discussion started by: gaspol
2 Replies
9. Web Development
I'm exploring the possibility of load balancing 2 web servers and have both access an NFS share on an NFS server. I'm wondering which types of data would need to reside on the webservers and the NFS server. Would the entire web directory (HTML, CSS, images, documents) all reside in the NFS server... (1 Reply)
Discussion started by: gaspol
1 Replies
10. Filesystems, Disks and Memory
I've got a bunch of application CDs that I use here at home under Wine. They are Windows applications and as such, some of them want to see the volume label in order for the application to run. So... just copying the CD-ROM contents to a directory doesn't work. With that in mind, what I've done... (1 Reply)
Discussion started by: deckard
1 Replies
symlink(2) System Calls Manual symlink(2)
Name
symlink - make symbolic link to a file
Syntax
symlink(name1, name2)
char *name1, *name2;
Description
A symbolic link name2 is created to name1 (name2 is the name of the file created, name1 is the string used in creating the symbolic link).
Either name can be an arbitrary path name. The files need not be on the same file system.
Return Values
Upon successful completion, a zero (0) value is returned. If an error occurs, the error code is stored in errno, and a -1 value is
returned.
Diagnostics
The symbolic link is made, unless one or more of the following are true:
[ENOTDIR] A component of the name2 prefix is not a directory.
[EEXIST] The name2 already exists.
[EACCES] A component of the name2 path prefix denies search permission.
[EROFS] The file name2 would reside on a read-only file system.
[EFAULT] The name1 or name2 points outside the process's allocated address space.
[ELOOP] Too many symbolic links were encountered in translating the pathname.
[ENAMETOOLONG] A component of either pathname exceeded MAXNAMELEN characters, or the entire length of either pathname exceeded MAXPATHNAME
characters.
[ENOENT] The named file does not exist.
[EIO] An I/O error occurred while making the directory entry for name2, or allocating the inode for name2, or writing out the link
contents of name2.
[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 is no space left on the file system that will contain the symbolic
link.
[ENOSPC] There are no free inodes on the file system on which the symbolic link is being created.
[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 user's symbolic link is being created has been exhausted.
[EIO] An I/O error occurred while making the directory entry or allocating the inode.
[ETIMEDOUT] A connect request or remote file operation failed, because the connected party did not properly respond after a period of
time that is dependent on the communications protocol.
See Also
ln(1), link(2), readlink(2), stat(2), unlink(2)
symlink(2)
