11-06-2015
Yes, a symbolic link on the nfs is the way to go.
A link tmp -> /tmp is quite common.
The same applies to a log directory; the destination directory with correct attributes must exist on each client.
Eventual log rotation/cleanup must run on each client - the best method is to let the application do it.
--
An alternative is to use automounter and a hierarchical mount. Probably more complicated and less preferrable.
Last edited by MadeInGermany; 11-06-2015 at 03:51 AM..
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I want to copy php.ini to all subdirectory. what command that should i run? (2 Replies)
Discussion started by: dzufauzan
2 Replies
2. AIX
Hi,
I want to change the values for shared file system in aix for that I have run the command smitty chnfsexp but I am not getting the all the values which I have seen while adding the file system while exporting
example
smitty chnfsexp
but after selecting shared file system using F4... (3 Replies)
Discussion started by: manoj.solaris
3 Replies
3. Filesystems, Disks and Memory
hello
i wanted to ask you
i try to setting:
pc server name: A
pc user name: B
pc user name: C
server A is opensuse 11.2 with kde 4.3.5 and last kernel
so i create NFS server, i think.. folder (/usr is all softwares and library) because
server A can share to PC A.
because all... (0 Replies)
Discussion started by: tunjin
0 Replies
4. Solaris
I shared from linux server a dir with nfs3,solaris mount
ok,and can tar files,but if i do ls or cp..
on mnt i have mount the nfs share
root@solaris: mnt $ touch 2
root@solaris: mnt $ ls -lh
ls: can't read ACL on .: Permission denied
root@solaris: mnt $ ls
1.tar
2
root@solaris: mnt $ cp... (4 Replies)
Discussion started by: Linusolaradm1
4 Replies
5. HP-UX
I ve a client : <clientname> and a server: <servername>
Both of them running: HPUX B.11.31
SERVER outputs:
I ve shared a folder in <servername> called /test and the O/P for
# exportfs
- /test root=<clientname>,rw=<clientname>,ro ""
# showmount -e
export list for... (6 Replies)
Discussion started by: Amit Kulkarni
6 Replies
6. UNIX for Dummies Questions & Answers
Hello, I have a question regarding ACLs and their availability across different Unix platforms via NFS share.
If I have an AIX/FreeBSD/Solaris/HP-UX client that has an nfs share from a different system mounted on it, will the ACLs on the nfs share be processed properly?
My guess is that as... (2 Replies)
Discussion started by: bstring
2 Replies
7. Solaris
I'm using nfs client machine.
One of my colleague said that he shared the directories using nfs server .........
How can i know the nfs shared directories available to mount at my machine....??
Thanks in Advance.:b: (3 Replies)
Discussion started by: vamshigvk475
3 Replies
8. Solaris
I'm having a strange issue that I'm unsure what to do with. I have a new Solaris home server that I want hard mount /home to all our servers. I've made each user's home directory a filesystem so that I can manage every user with a quota. In each one of my server vfstab files I have it set as:
... (4 Replies)
Discussion started by: mijohnst
4 Replies
9. UNIX for Beginners Questions & Answers
Hi everyone,
have a good day to you.
I am trying to use NFS to share a folder between 2 linux systems.
Let's say the server which is sharing the folder is server A and the client which need to access this shared folder is server B.
In server B, i am having a Joe user which UID and GID is 500.... (1 Reply)
Discussion started by: michael_hoang
1 Replies
LEARN ABOUT DEBIAN
mh_installjar
MAVEN(1) User Commands MAVEN(1)
NAME
Maven - Installs a jar into /usr/share/maven-repo.
SYNOPSIS
mh_installjar [option]... [pom] [jar] [link]...
DESCRIPTION
Installs the jar file in /usr/share/maven-repo, at the correct location for Maven. The jar is copied into the build directory. It can also
create additional links to the jar, usually located in /usr/share/java.
Where
[pom] is the location of the POM associated with the jar to install.
GroupId, artifactId and version will be extracted from this file.
[jar] is the path to the jar to install, usually located in the build
folder.
[link] is an additional link to the jar to install, usually there should
be a link to usr/share/java/$jar.jar and usr/share/java/$jar-$version.jar to comply with the Java packaging guidelines. Note that
there is no need to specify those particular links if the --java-lib option is used.
OPTIONS
-h --help: show this text
-V --version: show the version
-p<package> --package=<package>: name of the Debian package which
will contain this jar file
-e<version>, --set-version=<version>: set the version for the jar,
do not use the version declared in the POM file.
-r<rules> --rules=<rules>: path to the file containing the
rules to apply when cleaning the POM. Optional, the default location is debian/maven.rules Maven rules are used here to extract the
groupId, artifactId and version from the POM file.
-l --java-lib: Optional, if given it will install the jar into
/usr/share/java to comply with the Debian Java specification. The jar will be installed as /usr/share/java/$name-$version.jar and a
versionless link /usr/share/java/$name.jar will point to it, as well as the links installed in /usr/share/maven-repo
-n<name> --usj-name=<name>: Optional, the name to use when installing the
library in /usr/share/java when --java-lib is used. Defaults to the artifact id found in the POM.
-j<version> --usj-version=<version>: Optional, the version to use when
installing the library in /usr/share/java when --java-lib is used. Defaults to the version found in the POM.
-s --no-usj-versionless: Optional, don't install the versionless link
in /usr/share/java. This flag is used only when the -l or --java-lib option is given.
-d<path> --dest-jar=<path>: Optional, the destination for the real jar.
The other places where the jar appears, in the repository or in the list of links, will be symlinks to this jar. Defaults to
/usr/share/java/$name-$version.jar if --java-lib is used, otherwise the jar is installed in the versioned path in the Maven reposi-
tory.
-c<classifier> --classifier=<classifier>: Optional, the classifier for
the jar. Empty by default.
-v --verbose: show more information while running
-n --no-act: don't actually do anything, just print the results
--skip-clean-pom: don't clean the pom, assume that a previous action ran
mh_cleanpom with the correct options. mh_cleanpom is run only to extract the groupId, artifactId and version of the jar
See also: mh_installpom(1), mh_installsite(1)
Maven Repo Helper version 1.7.1 January 2012 MAVEN(1)