9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am using SFTP to transmit files from the Mainframe to an UNIX server. I am looking for some kind of script that runs with SFTP to delete tranmitted files older than 3 days.
Can this be done in a SFTP transmission batch job? (5 Replies)
Discussion started by: Steve Carlson
5 Replies
2. AIX
how do i remove sub directories of a directory and all files which are older than 7 days by a single command in AIX. pls help me.
I am using command as
#find /gpfs1/home/vinod/hpc/ -depth -type d -mtime +7 -exec rm -rf {} \;
so i want to delete all sub directories and all files from the... (1 Reply)
Discussion started by: vinodkmpal
1 Replies
3. Shell Programming and Scripting
Hi All
I want to remove the files with name like data*.csv from the directory older than 10 days.
If there is no files exists to remove older than 10 days, It should not do anything.
Thanks
Jo (9 Replies)
Discussion started by: rajeshjohney
9 Replies
4. Shell Programming and Scripting
Hi All,
I am using below code to delete files older than 2 days. In case if there are no files, I should log an error saying no files to delete.
Please let me know, How I can achive this.
find /path/*.xml -mtime +2
Thanks and Regards
Nagaraja. (3 Replies)
Discussion started by: Nagaraja Akkiva
3 Replies
5. Shell Programming and Scripting
I want to write a shell script that deletes all log files in a directory that are older than 30 days except for 3 files:
I am using the following command:
find /tmp/logs -name "*.log" -mtime +30 -exec rm -f {} \;But this command deletes all the log files.
How can i modify this script that... (5 Replies)
Discussion started by: mmunir
5 Replies
6. Solaris
Hi all,
I want to delete log files with extension .log which are older than 30
days. How to delete those files?
Operating system -- Sun solaris 10
Your input is highly appreciated.
Thanks in advance.
Regards,
Williams (2 Replies)
Discussion started by: William1482
2 Replies
7. UNIX for Dummies Questions & Answers
This is driving me crazy. How can I delete files in a specifc directory that are over 30 days old? Thanks in advance. (3 Replies)
Discussion started by: tlphillips
3 Replies
8. Shell Programming and Scripting
Hi, All,
I'd like to delete files older than 1 day.
I thought the following command
find /your_directory -mtime +1-exec rm -f {} \;
will do the work, but not so, it seems like it won't delete files unless it is 2 days old or older. the files between 1 day and 2 days old does not... (7 Replies)
Discussion started by: ericaworld
7 Replies
9. UNIX for Dummies Questions & Answers
can anyone tell me how I would write a script in ksh on AIX that will delete files in a directory older than 7 days? (1 Reply)
Discussion started by: lesstjm
1 Replies
KADM5.ACL(5) MIT Kerberos KADM5.ACL(5)
NAME
kadm5.acl - Kerberos ACL file
DESCRIPTION
The Kerberos kadmind(8) daemon uses an Access Control List (ACL) file to manage access rights to the Kerberos database. For operations
that affect principals, the ACL file also controls which principals can operate on which other principals.
The default location of the Kerberos ACL file is /var/kerberos/krb5kdc/kadm5.acl unless this is overridden by the acl_file variable in
kdc.conf(5).
SYNTAX
Empty lines and lines starting with the sharp sign (#) are ignored. Lines containing ACL entries have the format:
principal permissions [target_principal [restrictions] ]
NOTE:
Line order in the ACL file is important. The first matching entry will control access for an actor principal on a target principal.
principal
(Partially or fully qualified Kerberos principal name.) Specifies the principal whose permissions are to be set.
Each component of the name may be wildcarded using the * character.
permissions
Specifies what operations may or may not be performed by a principal matching a particular entry. This is a string of one or more
of the following list of characters or their upper-case counterparts. If the character is upper-case, then the operation is disal-
lowed. If the character is lower-case, then the operation is permitted.
+--+---------------------------------------------------+
|a | [Dis]allows the addition of principals or poli- |
| | cies |
+--+---------------------------------------------------+
|c | [Dis]allows the changing of passwords for princi- |
| | pals |
+--+---------------------------------------------------+
|d | [Dis]allows the deletion of principals or poli- |
| | cies |
+--+---------------------------------------------------+
|i | [Dis]allows inquiries about principals or poli- |
| | cies |
+--+---------------------------------------------------+
|l | [Dis]allows the listing of principals or policies |
+--+---------------------------------------------------+
|m | [Dis]allows the modification of principals or |
| | policies |
+--+---------------------------------------------------+
|p | [Dis]allows the propagation of the principal |
| | database (used in incr_db_prop) |
+--+---------------------------------------------------+
|s | [Dis]allows the explicit setting of the key for a |
| | principal |
+--+---------------------------------------------------+
|x | Short for admcil. All privileges |
+--+---------------------------------------------------+
|* | Same as x. |
+--+---------------------------------------------------+
target_principal
(Optional. Partially or fully qualified Kerberos principal name.) Specifies the principal on which permissions may be applied.
Each component of the name may be wildcarded using the * character.
target_principal can also include back-references to principal, in which *number matches the component number in principal.
restrictions
(Optional) A string of flags. Allowed restrictions are:
{+|-}flagname
flag is forced to the indicated value. The permissible flags are the same as the + and - flags for the kadmin add_princi-
pal and modify_principal commands.
-clearpolicy
policy is forced to be empty.
-policy pol
policy is forced to be pol.
-{expire, pwexpire, maxlife, maxrenewlife} time
(getdate string) associated value will be forced to MIN(time, requested value).
The above flags act as restrictions on any add or modify operation which is allowed due to that ACL line.
WARNING:
If the kadmind ACL file is modified, the kadmind daemon needs to be restarted for changes to take effect.
EXAMPLE
Here is an example of a kadm5.acl file.
*/admin@ATHENA.MIT.EDU * # line 1
joeadmin@ATHENA.MIT.EDU ADMCIL # line 2
joeadmin/*@ATHENA.MIT.EDU il */root@ATHENA.MIT.EDU # line 3
*/root@ATHENA.MIT.EDU cil *1@ATHENA.MIT.EDU # line 4
*/*@ATHENA.MIT.EDU i # line 5
*/admin@EXAMPLE.COM x * -maxlife 9h -postdateable # line 6
(line 1) Any principal in the ATHENA.MIT.EDU realm with an admin instance has all administrative privileges.
(lines 1-3) The user joeadmin has all permissions with his admin instance, joeadmin/admin@ATHENA.MIT.EDU (matches line 1). He has no per-
missions at all with his null instance, joeadmin@ATHENA.MIT.EDU (matches line 2). His root and other non-admin, non-null instances (e.g.,
extra or dbadmin) have inquire and list permissions with any principal that has the instance root (matches line 3).
(line 4) Any root principal in ATHENA.MIT.EDU can inquire, list, or change the password of their null instance, but not any other null
instance. (Here, "*1" denotes a back-reference to the first component of the actor principal.)
(line 5) Any principal in the realm ATHENA.MIT.EDU (except for joeadmin@ATHENA.MIT.EDU, as mentioned above) has inquire privileges.
(line 6) Finally, any principal with an admin instance in EXAMPLE.COM has all permissions, but any principal that they create or modify
will not be able to get postdateable tickets or tickets with a life of longer than 9 hours.
SEE ALSO
kdc.conf(5), kadmind(8)
AUTHOR
MIT
COPYRIGHT
1985-2013, MIT
1.11.3 KADM5.ACL(5)