Sponsored Content
Top Forums UNIX for Advanced & Expert Users Permission inherited by users Post 302682197 by raggmopp on Sunday 5th of August 2012 06:51:46 PM
Old 08-05-2012
Seeing that both jane and jules are in the same group;

Code:
chmod g+s <dir name>

setting the sticky bit, aka, groupid, for the directory.
This forces the subdirectories and files to inherit the group perms of the parent directory, which you set accordingly.

Adding another layer, you could implement ACL's (Access Control Lists)

http://www.udel.edu/topics/os/unix/g...upsharing.html

The above link has good info in it.

My google search was "chmod g+s directory". Lots of hits.
 

10 More Discussions You Might Find Interesting

1. SCO

Inherited server - need help

I have inherited admin duties on an old server running SCO Open Server 5. No changes have been made to this thing for a very long time. The server has started randomly disconnecting itself from the network. I have to reboot the server to get it to find the network again. It happens about once a... (3 Replies)
Discussion started by: jmickens
3 Replies

2. Shell Programming and Scripting

Trying to manage an inherited Ksh script

Hi I am trying to get to know a script I have inherited. The original author is no longer available. Does anyone know if there is a utility to parse a ksh script and generate a report/output which details all the defined functions and their arguments? Maybe even provide a 'call trace' of how the... (1 Reply)
Discussion started by: ajcannon
1 Replies

3. Cybersecurity

file permission/acl: 2 users with write access on 1 file...

Hello, i need some help/advice on how to solve a particular problem. these are the users: |name | group | ---------- --------------- |boss | department1 | |assistant | department1 | |employee | department1 | |spy | department2 | this is the... (0 Replies)
Discussion started by: elzalem
0 Replies

4. HP-UX

Telnet permission for other then root users in HP-UNIX

Hi please tell me any one how to give telnet permission for other then root users in HP-UNIX :confused: (4 Replies)
Discussion started by: sreedhargouda
4 Replies

5. UNIX for Advanced & Expert Users

about the access permission of users home directory

RHEL5.0 As we know, when root create a new user, a new home directory will be created : /home/user I want to know what determine the access permission of /home/user . Thanks! (1 Reply)
Discussion started by: cqlouis
1 Replies

6. Solaris

To restrict the users not to change the passwords for NIS users

Hi All, How to restrict the NIS users not to change their passwords in for NIS users?? and my NIS user is unable to login to at client location what could be the problem for this ? Any body can help me. Thanks in advance. (1 Reply)
Discussion started by: Sharath Kumar
1 Replies

7. AIX

Inherited VIO server an LPARs

Lucky me, someone has installed a server and got it running with the best intentions, but leaving me a headache. :wall: We have a simple p520 with 4 disks. 2x145Gb & 2x300Gb. The smaller disk pair have been built into a VIO mirrored rootvg, and quite right too. The other two disks form a... (3 Replies)
Discussion started by: rbatte1
3 Replies

8. Red Hat

Showing all users in 'users' and 'top' commands

Hi All, I work in a multi user environment where my school uses Red Hat Linux server. When I issue commands such as "top" or "users", I get to see what others are doing and what kinds of applications they are running (even ps -aux will give such information). "users" will let me know who else is... (1 Reply)
Discussion started by: shoaibjameel123
1 Replies

9. Shell Programming and Scripting

Create multiple users with individual passwords to users

hi, i am new to shell scripts i write a shell script to create multiple users but i need to give passwords to that users while creating users, command to write this script (1 Reply)
Discussion started by: DONFOX
1 Replies

10. Shell Programming and Scripting

Trying to Parse An Inherited Command/Routine

I am am one of these people that it isn't good enough just to say, "Here, try this...". it is important for me to understand how and why something works (or doesn't work.) All that being said, I am trying to parse out a command that we use that was handed down to me by someone I can no longer... (3 Replies)
Discussion started by: he204035
3 Replies
DOVEADM-IMPORT(1)						      Dovecot							 DOVEADM-IMPORT(1)

NAME
doveadm-import - Import messages matching given search query SYNOPSIS
doveadm [-Dv] import [-S socket_path] [-s] source_location dest_parent search_query doveadm [-Dv] import [-S socket_path] [-s] -A source_location dest_parent search_query doveadm [-Dv] import [-S socket_path] [-s] -u user source_location dest_parent search_query DESCRIPTION
This command can be used to import mails from another mail storage specified by source_location to one or more user's mailboxes. All the mailboxes are imported under the given dest_parent mailbox, or to root level if dest_parent is empty (""). The search_query can be used to restrict which mailboxes or messages are imported. In the first form, doveadm(1) will executed the import action with the environment of the logged in system user. In the second form, the mails will be imported for all users. In the third form, the mails will be imported only for given user(s). OPTIONS
Global doveadm(1) options: -D Enables verbosity and debug messages. -v Enables verbosity, including progress counter. Command specific options: -A If the -A option is present, the command will be performed for all users. Using this option in combination with system users from userdb { driver = passwd } is not recommended, because it contains also users with a lower UID than the one configured with the first_valid_uid setting. When the SQL userdb module is used make sure that the iterate_query setting in /etc/dovecot/dovecot-sql.conf.ext matches your data- base layout. When using the LDAP userdb module, make sure that the iterate_attrs and iterate_filter settings in /etc/dovecot/dove- cot-ldap.conf.ext match your LDAP schema. Otherwise doveadm(1) will be unable to iterate over all users. -S socket_path The option's argument is either an absolute path to a local UNIX domain socket, or a hostname and port (hostname:port), in order to connect a remote host via a TCP socket. This allows an administrator to execute doveadm(1) mail commands through the given socket. -s When the -s option is present, dest_parent and all new mailboxes under it will be listed in the subscriptions file. -u user/mask Run the command only for the given user. It's also possible to use '*' and '?' wildcards (e.g. -u *@example.org). When neither the -A option nor -u user was specified, the command will be executed with the environment of the currently logged in user. ARGUMENTS
dest_parent The name of the destination mailbox, under which the mails should be imported. doveadm(1) will create the dest_parent mailbox if it doesn't exist. search_query Copy messages matching this search query. See doveadm-search-query(7) for details. source_location This argument specifies the mailbox format and location of the source location. The syntax is the same as for the mail_location set- ting. For example: maildir:/backup/20101126/jane.doe/Maildir or mdbox:/srv/mail/john.doe/mdbox:ALT=/nfsmount/john.doe/mdbox EXAMPLE
This example imports all mails from a backup under a backup-20101026 mailbox: doveadm import -u jane.doe@example.org mdbox:/backup/20101026/jane.doe/mdbox backup-20101026 all Another example that imports only messages from foo@example.org in the backup mdbox's INBOX to jane's INBOX: doveadm import -u jane.doe@example.org mdbox:~/mdbox-backup "" mailbox INBOX from foo@example.org REPORTING BUGS
Report bugs, including doveconf -n output, to the Dovecot Mailing List <dovecot@dovecot.org>. Information about reporting bugs is avail- able at: http://dovecot.org/bugreport.html SEE ALSO
doveadm(1), doveadm-fetch(1), doveadm-search(1), doveadm-search-query(7) Dovecot v2.2 2013-11-24 DOVEADM-IMPORT(1)
All times are GMT -4. The time now is 03:09 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy