10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Redirecting log files to null writing junk into log files.
i have log files which created from below command
exec <processname> >$logfile
but when it reaches some size i am redirecting to null while process is running like
>$logfile
manually but after that it writes some junk into... (7 Replies)
Discussion started by: greenworld123
7 Replies
2. Shell Programming and Scripting
I want to move all files from one directory to another directory excluding today (sysdate files) on daily basis.
file name is in pattern file_2013031801, file_2013031802 etc (2 Replies)
Discussion started by: khattak
2 Replies
3. Solaris
Hi,
I am using solaris 10 OS.Please help me out with the commands needed in below two scenarios.
1)How to delete the existing files in the tar file.
suppose i have a main tarfile named application.tar and it contains a file called ingres.tar.
what is the command to remove ingres.tar... (2 Replies)
Discussion started by: muraliinfy04
2 Replies
4. Solaris
Dear All,
I have one of my Servers, running Solaris 9. I wanna enable the Audit log enabling, the way I did in Solaris 10 Servers.
After running, the bsmconv script, giving the reboots, modifying all the audit files in /etc/security, the audit is enabled, but the audit file which shall be... (3 Replies)
Discussion started by: sumeet1806
3 Replies
5. Shell Programming and Scripting
is there a way to efficiently monitor logfiles that do not have a date or time format? i have several logs on several different servers that need to be monitored. but i realized writing a script for this would be very complex and time consuming giving the variety of things i need to check for i.e.... (2 Replies)
Discussion started by: SkySmart
2 Replies
6. Shell Programming and Scripting
we r to develope a project which involves automatic encryption of all the text files user was working upon during logg off
and to decrypt them during log on
this is to be done by writing a shell script
can anyone help (2 Replies)
Discussion started by: vyom
2 Replies
7. Shell Programming and Scripting
How can view log messages between two time frame from /var/log/message or any type of log files.
when logfiles are very big and especially many messages with in few minutes, I would like to display log messages between 5 minute interval.
Could you pls give me the command? (1 Reply)
Discussion started by: johnveslin
1 Replies
8. Solaris
Hi,
i am workiing on HP servers with solaris 10
SunOS vmsvApp01 5.10 Generic_142910-17 i86pc i386 i86pc
i am facing a dealyed log in problem,
As soon i log in ... server is taking around 40-50 seconds to prompt password.
please suggest
Anand, (1 Reply)
Discussion started by: anand87
1 Replies
9. UNIX for Dummies Questions & Answers
Hey guys,
Should all logs as far as people logging in, group or user changes be in /var/log I'm using Solaris 9. Trying to actually start looking at logs here and there and I'm not really sure if they are all in that directory or if they are all enabled for logging.
Any starter tips would be... (2 Replies)
Discussion started by: kingdbag
2 Replies
10. Solaris
I have a simple backup script that I am running to back up drives across the network. However I need to have detailed log files for this script such as time backup started, what was backed up, if there were any errors and the time that the backup was complete. I would also like the script to... (3 Replies)
Discussion started by: valicon
3 Replies
LEARN ABOUT CENTOS
auth_attr
auth_attr(4) File Formats auth_attr(4)
NAME
auth_attr - authorization description database
SYNOPSIS
/etc/security/auth_attr
DESCRIPTION
/etc/security/auth_attr is a local source for authorization names and descriptions. The auth_attr file can be used with other authorization
sources, including the auth_attr NIS map and NIS+ table. Programs use the getauthattr(3SECDB) routines to access this information.
The search order for multiple authorization sources is specified in the /etc/nsswitch.conf file, as described in the nsswitch.conf(4) man
page.
An authorization is a right assigned to users that is checked by certain privileged programs to determine whether users can execute
restricted functionality. Each entry in the auth_attr database consists of one line of text containing six fields separated by colons (:).
Line continuations using the backslash () character are permitted. The format of each entry is:
name:res1:res2:short_desc:long_desc:attr
name The name of the authorization. Authorization names are unique strings. Construct authorization names using the following
convention:
prefix. or prefix.suffix
prefix Everything in the name field up to the final dot (.). Authorizations from Sun Microsystems, Inc. use solaris as a
prefix. To avoid name conflicts, all other authorizations should use a prefix that begins with the reverse-order
Internet domain name of the organization that creates the authorization (for example, com.xyzcompany). Prefixes
can have additional arbitrary components chosen by the authorization's developer, with components separated by
dots.
suffix The final component in the name field. Specifies what is being authorized.
When there is no suffix, the name is defined as a heading. Headings are not assigned to users but are constructed
for use by applications in their GUIs.
When a name ends with the word grant, the entry defines a grant authorization. Grant authorizations are used to support
fine-grained delegation. Users with appropriate grant authorizations can delegate some of their authorizations to others.
To assign an authorization, the user needs to have both the authorization itself and the appropriate grant authorization.
res1 Reserved for future use.
res2 Reserved for future use.
short_desc A short description or terse name for the authorization. This name should be suitable for displaying in user interfaces,
such as in a scrolling list in a GUI.
long_desc A long description. This field can explain the precise purpose of the authorization, the applications in which it is used,
and the type of user that would be interested in using it. The long description can be displayed in the help text of an
application.
attr An optional list of semicolon-separated (;) key-value pairs that describe the attributes of an authorization. Zero or more
keys may be specified. The keyword help identifies a help file in HTML.
EXAMPLES
Example 1: Constructing a Name
In the following example, the name has a prefix (solaris.admin.usermgr) followed by a suffix (read):
solaris.admin.usermgr.read
Example 2: Defining a Heading
Because the name field ends with a dot, the following entry defines a heading:
solaris.admin.usermgr.:::User Accounts::help=AuthUsermgrHeader.html
Example 3: Assigning Separate Authorizations to Set User Attributes
In this example, a heading entry is followed by other associated authorization entries. The entries below the heading provide separate
authorizations for setting user attributes. The attr field for each entry, including the heading entry, assigns a help file. The applica-
tion that uses the help key requires the value to equal the name of a file ending in .htm or .html:
solaris.admin.usermgr.:::User Accounts::help=AuthUsermgrHeader.html
solaris.admin.usermgr.pswd:::Change Password::help=AuthUserMgrPswd.html
solaris.admin.usermgr.write:::Manage Users::help=AuthUsermgrWrite.html
Example 4: Assigning a Grant Authorization
This example assigns to an administrator the following authorizations:
solaris.admin.printer.grant
solaris.admin.printer.delete
solaris.admin.printer.modify
solaris.admin.printer.read
solaris.login.enable
With the above authorizations, the administrator can assign to others the solaris.admin.printer.delete, solaris.admin.printer.modify, and
solaris.admin.printer.read authorizations, but not the solaris.login.enable authorization. If the administrator has both the grant autho-
rization, solaris.admin.printmgr.grant, and the wildcard authorization, solaris.admin.printmgr.*, the administrator can grant to others any
of the printer authorizations. See user_attr(4) for more information about how wildcards can be used to assign multiple authorizations
whose names begin with the same components.
Example 5: Authorizing the Ability to Assign Other Authorizations
The following entry defines an authorization that grants the ability to assign any authorization created with a solaris prefix, when the
administrator also has either the specific authorization being granted or a matching wildcard entry:
solaris.grant:::Grant All Solaris Authorizations::help=PriAdmin.html
Example 6: Consulting the Local Authorization File Ahead of the NIS Table
With the following entry from /etc/nsswitch.conf, the local auth_attr file is consulted before the NIS table:
auth_attr:files nisplus
FILES
/etc/nsswitch.conf
/etc/user_attr
/etc/security/auth_attr
SEE ALSO
getauthattr(3SECDB), getexecattr(3SECDB), getprofattr(3SECDB), getuserattr(3SECDB), exec_attr(4), nsswitch.conf(4), user_attr(4)
NOTES
When deciding which authorization source to use, keep in mind that NIS+ provides stronger authentication than NIS.
Because the list of legal keys is likely to expand, any code that parses this database must be written to ignore unknown key-value pairs
without error. When any new keywords are created, the names should be prefixed with a unique string, such as the company's stock symbol, to
avoid potential naming conflicts.
Each application has its own requirements for whether the help value must be a relative pathname ending with a filename or the name of a
file. The only known requirement is for the name of a file.
The following characters are used in describing the database format and must be escaped with a backslash if used as data: colon (:), semi-
colon (;), equals (=), and backslash ().
SunOS 5.10 9 Jan 2002 auth_attr(4)