Sponsored Content
Top Forums Shell Programming and Scripting Solaris 9 Home Directory, Two Machines Sharing a NAS Post 303025055 by MadeInGermany on Tuesday 23rd of October 2018 02:31:52 PM
Old 10-23-2018
While {} \; runs a chmod for each file, the {} + collects the filenames and, when long enough, runs a chmod with the collected argument list.
Fewer invocations of chmod => greater speed.
This User Gave Thanks to MadeInGermany For This Post:
 

7 More Discussions You Might Find Interesting

1. HP-UX

sharing a directory

Im trying to simply share a directory on one unix server and mount that share on a different unix server. There is no "share" command like on sun. What is the command to create a share on HP-UX? (2 Replies)
Discussion started by: bski
2 Replies

2. IP Networking

Printer Sharing on a Mixed(Windows/Linux) Home Network

Sometimes you get the tiger...but sometimes he get you and this latest home network “project” of mine has gnawed on me pretty badly. Perhaps you can offer some technical help. It will be heartily appreciated. I have a small home network initially comprising two computers running Windows... (1 Reply)
Discussion started by: Annatar
1 Replies

3. UNIX for Advanced & Expert Users

Mounting NAS Drive on solaris

Hi, Im running 32-bit solaris on sparc. We have a NAS(Network attached drive), with its IP address, username and password. I'd like to be able to mount it on the solaris machine, and unmount it. The best possibility would be able to mount it simulataneously on 2 or more systems. Please... (9 Replies)
Discussion started by: 0ktalmagik
9 Replies

4. Solaris

NISuser home directory movement in Solaris

How to move home directory of NIS user from one system to another system in Solaris. Thanks & Regards Durgaprasad (1 Reply)
Discussion started by: durgaprasadr13
1 Replies

5. UNIX for Dummies Questions & Answers

ssh autologin issue when both machines are having same ~home directory

Hi, I have two machines. M1 and M2 and having a generic id catadm, these two machines having common mount of /u/catadm directory. with this setup, ssh autologin is failing for me and asking me to enter password when i try autologin using this generc id from M1 to M2 catadm-M1$ ssh... (3 Replies)
Discussion started by: rbalaj16
3 Replies

6. Solaris

Sharing a local disk between to solaris machines

Hi, I recently added a disk on a solaris 9 and I wanted to make it accessible for another machine, using the same name here is what i did : On the machine holding the internal disk in vfstab i added the line /dev/dsk/c1t1d0s4 /dev/rdsk/c1t1d0s4 /SHARED2 ufs 2 yes ... (2 Replies)
Discussion started by: zionassedo
2 Replies

7. Solaris

NFS with a NAS: permanently inconsistent directory state across clients

Hi, I am having some NFS directory consistency problems with the below setup on a local (192.) network: 1. Different permissions (chmod) for the same NFS dir are reflected on different clients. 2. (more serious) an NFS dir created on client1 cannot be accessed on client2; this applies to some... (10 Replies)
Discussion started by: cosmojetz
10 Replies
sticky(5)                                               Standards, Environments, and Macros                                              sticky(5)

NAME
sticky - mark files for special treatment DESCRIPTION
The sticky bit (file mode bit 01000, see chmod(2)) is used to indicate special treatment of certain files and directories. A directory for which the sticky bit is set restricts deletion of files it contains. A file in a sticky directory can only be removed or renamed by a user who has write permission on the directory, and either owns the file, owns the directory, has write permission on the file, or is a privi- leged user. Setting the sticky bit is useful for directories such as /tmp, which must be publicly writable but should deny users permission to arbitrarily delete or rename the files of others. If the sticky bit is set on a regular file and no execute bits are set, the system's page cache will not be used to hold the file's data. This bit is normally set on swap files of diskless clients so that accesses to these files do not flush more valuable data from the sys- tem's cache. Moreover, by default such files are treated as swap files, whose inode modification times may not necessarily be correctly recorded on permanent storage. Any user may create a sticky directory. See chmod for details about modifying file modes. SEE ALSO
chmod(1), chmod(2), chown(2), mkdir(2), rename(2), unlink(2) BUGS
The mkdir(2) function will not create a directory with the sticky bit set. SunOS 5.10 1 Aug 2002 sticky(5)
All times are GMT -4. The time now is 06:16 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy