05-16-2008
On AIX and *BSD is possible, let's say :
Quote:
/tmp/test1 - allowing user1,(rw), insecure
/tmp/test1 - allowing user2,(r), secure --no-acl
These are just examples I have found in the net.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi everyone,
I was told, i my job, to do a script that creates the backup of all the files that are important to us.
So i created the script, put it in the crontab and it works great.
Now what i want is to write to a file what directories have being copied with date and time.
How can i... (3 Replies)
Discussion started by: jorge.ferreira
3 Replies
2. HP-UX
Hello,
If I have an export like:
/usr/temp -rw=ram:alligator
means that /usr/temp has "rw" permissions to ram and alligator machines and has "ro" to everyone else? (1 Reply)
Discussion started by: psimoes79
1 Replies
3. 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
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. SCO
After System power get failed
File system is not getting mounted in read- write mode (1 Reply)
Discussion started by: gtkpmbpl
1 Replies
6. UNIX for Dummies Questions & Answers
Hello All,
I am application admin. I need to clear all the temporary files cleared by the applications. I need help/suggestion that is there any way to create a file system such that every Dir created in by any user will have 775 permissions. So, that i can simply clear the temporary file which... (6 Replies)
Discussion started by: firestar
6 Replies
7. SCO
hi
Knows someone what kind of file system uses SCO Unix 5.0.6?
Which linux or unix LIVE CD can read and write into file system from SCO Unix?
I've tried to boot SCO using Knoppix 6.2.1 LIVE CD, but cannot mount.
# mount -t sysv /dev/sda1 /mnt
mount: wrong fs type, bad option, bad superblock... (2 Replies)
Discussion started by: ccc
2 Replies
8. AIX
Hello Guru's
We are trying to save some data for 10 -15 yrs. so we created a NFS share file system and mounted on AIX 5.3 servers, keeping in mind that we might need to replace the expired disk/bad disk every 2 yrs or 4 yrs.
Now we are trying to solve. How to protect it from getting deleted... (6 Replies)
Discussion started by: Beginner123
6 Replies
9. Red Hat
I am attempting to get a baseline of deployed RHEL 6.5 servers and need to produce a full filesystem permission settings list.....but I forgot the bloody command and am racking my brain and now have a migraine.
I just need a simple list starting at "/" right down the tree, listing the folder,... (3 Replies)
Discussion started by: strykergli250hp
3 Replies
10. UNIX for Beginners Questions & Answers
i want to give users the ability to create write and read files in other user directory , but not to have option to delete the file after created ( sticky bit not going to work here ... ) for example :
i have user : manager with directory repository
i have user : worker1 that need to write... (4 Replies)
Discussion started by: umen
4 Replies
WDMD(8) System Manager's Manual WDMD(8)
NAME
wdmd - watchdog multiplexing daemon
SYNOPSIS
wdmd [OPTIONS]
DESCRIPTION
This daemon opens /dev/watchdog and allows multiple independent sources to detmermine whether each KEEPALIVE is done. Every test interval
(10 seconds), the daemon tests each source. If any test fails, the KEEPALIVE is not done. In a standard configuration, the watchdog timer
will reset the system if no KEEPALIVE is done for 60 seconds ("fire timeout"). This means that if single test fails 5-6 times in row, the
watchdog will fire and reset the system. With multiple test sources, fewer separate failures back to back can also cause a reset, e.g.
T seconds, P pass, F fail
T00: test1 P, test2 P, test3 P: KEEPALIVE done
T10: test1 F, test2 F, test3 P: KEEPALIVE skipped
T20: test1 F, test2 P, test3 P: KEEPALIVE skipped
T30: test1 P, test2 F, test3 P: KEEPALIVE skipped
T40: test1 P, test2 P, test3 F: KEEPALIVE skipped
T50: test1 F, test2 F, test3 P: KEEPALIVE skipped
T60: test1 P, test2 F, test3 P: KEEPALIVE skipped
T60: watchdog fires, system resets
(Depending on timings, the system may be reset sometime shortly before T60, and the tests at T60 would not be run.)
A crucial aspect to the design and function of wdmd is that if any single source does not pass tests for the fire timeout, the watchdog is
guaranteed to fire, regardless of whether other sources on the system have passed or failed. A spurious reset due to the combined effects
of multiple failing tests as shown above, is an accepted side effect.
wdmd will exit if a watchdog driver is not loaded.
wdmd cannot be used on the system with any other program that needs to open /dev/watchdog, e.g. watchdog(8).
Test Source: clients
Using libwdmd, programs connect to wdmd via a unix socket, and send regular messages to wdmd to update an expiry time for their connection.
Every test interval, wdmd will check if the expiry time for a connection has been reached. If so, the test for that client fails.
(Other test sources such as scripts executed each test interval may be added in the future.)
OPTIONS
-D Enable debugging to stderr and don't fork.
-H num Enable (1) or disable (0) high priority features such as realtime scheduling priority and mlockall.
Default 1.
2011-08-01 WDMD(8)