10-02-2012
Quote:
Originally Posted by
Beginner123
Because our departments get the space for Free .
You are free to decide whatever you want, but be warned: this is a very, very, bad reason to base a decision on in all things technical.
Quote:
Could any one please suggest, how to make the (/xshare) file system an write once ,while owner group users of this share can read the contents. If I could solve that I can close this request.
There is definitely, positively no such thing: either one is allowed to write or not. If one is allowed to write he is permanently entitled to do so, if one is forbidden the non-entitlement is also permanent.
You could write a script which checks the directory in question and, if files are in it, mounts it read-only, otherwise it mounts read-write. Then put a cron job in place so that the directory gets unmounted/remounted once a day (or more often, whatever you deem feasible).
This will be as close as possible to "write once", but you will have to understand that your original requirement is not possible as such, any solution will be a better or worse compromise between what you want and what is possible.
I hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Hi...
Is it possible to re-export a exported NFS file system? If no, Why?
Let me know, if any further details are required about the question.
Thanks in advance
Adams:) (5 Replies)
Discussion started by: Adams Nave
5 Replies
2. AIX
I create a NFS file system. I can read this system from client, however, I cannot write anything in this folder. Why? (1 Reply)
Discussion started by: rainbow_bean
1 Replies
3. Solaris
:confused:Hi all
When i see in the /var/adm/messages, i saw the following error
unix: NFS write error on host : Stale NFS file handle.
unix: (file handle: 45ca415 3e7 a0000 2c7f6 3ebfc25f a0000 2 3e49)
It is using sunOS 5.7. Is anybody know what is this error?
Is is related to any network... (2 Replies)
Discussion started by: AirWalker83
2 Replies
4. AIX
Hello,
Can someone please point to an easy document or steps how to export AIX file system /whatever to Windows O/S
Basically Windows should see this filesystem / directory and should be able to write in this filesystem / directory
Thanks (2 Replies)
Discussion started by: filosophizer
2 Replies
5. UNIX for Dummies Questions & Answers
Hi, suppose I have file system path say /foo/bar/baz then how would I find out whether it is local file system or NFS? If it is NFS then I want to find out the host where file system is located.
Thanks,
Paresh (5 Replies)
Discussion started by: masaniparesh
5 Replies
6. SCO
After System power get failed
File system is not getting mounted in read- write mode (1 Reply)
Discussion started by: gtkpmbpl
1 Replies
7. AIX
hello,
i am trying to export a file system so that i can mount it on NIM server and make mksysb backup of the server on that fs.
i get this message:
mount: 1831-011 access denied for s_semdev:/dr_s_zeus/mksysb/dr_s_zeus
mount: 1831-008 giving up on:
s_semdev:/dr_s_zeus/mksysb/dr_s_zeus ... (5 Replies)
Discussion started by: omonoiatis9
5 Replies
8. AIX
Hello,
I have a script on my NIM Master that runs with crons and performs mksysb backups of all NIM Clients once a week.
There is a problem with one of the clients as it stucks and never finishes the mksysb backups.
I tried to unmount the NFS file system created by the NIM in order to perform... (5 Replies)
Discussion started by: omonoiatis9
5 Replies
9. Solaris
Hi all,
Sorry if I sound like a novice , I have always thought that for network file system which can be shared, there will be some access restriction in which
when user A is writing/editing fileA, user B is able to view the same fileA but cannot write/edit it until user A has... (6 Replies)
Discussion started by: javanoob
6 Replies
10. Solaris
Oct 13 12:19:15 xyz nfs: NFS write error on host xyz: Stale NFS file handle.
Oct 13 12:19:15 xyz nfs: (file handle: 68000000 1bc5492e 20000000 377c5e 1ce9395c 720a6203 40000000 bdfb0400)
Oct 13 12:19:15 xyz nfs: NFS write error on host zyz: Stale NFS file handle.
Oct 13 12:19:15 xyz nfs: ... (5 Replies)
Discussion started by: psychocandy
5 Replies
OPEN(2) System Calls Manual OPEN(2)
NAME
open, create, close - open a file for reading or writing, create file
SYNOPSIS
#include <u.h>
#include <libc.h>
int open(char *file, int omode)
int create(char *file, int omode, ulong perm)
int close(int fd)
DESCRIPTION
Open opens the file for I/O and returns an associated file descriptor. Omode is one of OREAD, OWRITE, ORDWR, or OEXEC, asking for permis-
sion to read, write, read and write, or execute, respectively. In addition, there are three values that can be ORed with the omode: OTRUNC
says to truncate the file to zero length before opening it; OCEXEC says to close the file when an exec(2) or execl system call is made; and
ORCLOSE says to remove the file when it is closed (by everyone who has a copy of the file descriptor). Open fails if the file does not
exist or the user does not have permission to open it for the requested purpose (see stat(2) for a description of permissions). The user
must have write permission on the file if the OTRUNC bit is set. For the open system call (unlike the implicit open in exec(2)), OEXEC is
actually identical to OREAD.
Create creates a new file or prepares to rewrite an existing file, opens it according to omode (as described for open), and returns an
associated file descriptor. If the file is new, the owner is set to the userid of the creating process group; the group to that of the
containing directory; the permissions to perm ANDed with the permissions of the containing directory. If the file already exists, it is
truncated to 0 length, and the permissions, owner, and group remain unchanged. The created file is a directory if the CHDIR bit is set in
omode. It is an exclusive-use file if the CHEXCL bit is set. Such files may be open for I/O by only one client at a time, but the file
descriptor may become invalid if no I/O is done for an extended period; see open(5).
Create fails if the path up to the last element of file cannot be evaluated, if the user doesn't have write permission in the final direc-
tory, or if the file already exists and does not permit the access defined by omode. If the file is new and the directory in which it is
created is a union directory (see intro(2)) then the constituent directory where the file is created depends on the structure of the union:
see bind(2).
Close closes the file associated with a file descriptor. Provided the file descriptor is a valid open descriptor, close is guaranteed to
close it; there will be no error. Files are closed automatically upon termination of a process; close allows the file descriptor to be
reused.
SOURCE
/sys/src/libc/9syscall
SEE ALSO
intro(2), bind(2), stat(2)
DIAGNOSTICS
These functions set errstr.
OPEN(2)