01-24-2006
User Administration
I have an application that runs on Unix and the user administration is managed at a Unix level. The application has an application ID which is linked to the user ids which are created at Unix level. Can you please help if I can be able to track which user used the Application ID and what action was performed?
Thanks
8 More Discussions You Might Find Interesting
1. Solaris
Hello, I inhearited several solaris machines (read that about 30 of them) and have a need to be able to manage the user accounts remotely.... Currently the machines all have the same users but not exactly the same spelling (each machine was locally managed before and thus every single passwd/shadow... (2 Replies)
Discussion started by: wgriffin
2 Replies
2. UNIX for Dummies Questions & Answers
Hey guys how do you check if an account is locked in tru64, and how do you unlock it? (1 Reply)
Discussion started by: sbn
1 Replies
3. Solaris
hi '
i am creating a primary group and a secondary group for a user.
#groupadd -g 101 test
#groupadd -g 102 test1
#useradd -d /export/home/user1 -m -s /bin/ksh -g test -G test user1
in /etc/passwd i can find the username as user1 and group name as test
and where can i find the... (4 Replies)
Discussion started by: madhudeepan
4 Replies
4. Solaris
Hi All.....
How many maximum no of users can be created in solaris 10.0
Waiting for the reply ..... (2 Replies)
Discussion started by: sendhils13
2 Replies
5. Solaris
unable to run smgroup / smadd command to create or modify the users and directories. (1 Reply)
Discussion started by: sendhils13
1 Replies
6. Solaris
hi frnds
I created sparse root zone, in that zone when i try to change the passwd it is giving permission denied.
what is the reason and how to chnage the root passwd in the zone. can u please explain the query. (4 Replies)
Discussion started by: sravan ega
4 Replies
7. Shell Programming and Scripting
Dear All,
I need to restrict the users in our server.
1.History & history -c command working all groups & others.So i need to restrict history -c option for groups & others .
2.Any option available to view user activity with all
Eg--->user1 Jul22 10:20:11 date
3.Any other Special... (7 Replies)
Discussion started by: kpoobathi
7 Replies
8. AIX
Dear All
Please how can I create a user which would be only able to manage queue printer like creating, release, hold etc a printer queue. He would for example be able to enter commands like :
- lpstat -pprintqueue where printqueue is an existing queue on the server
- enable printqueue... (0 Replies)
Discussion started by: sobnc
0 Replies
LEARN ABOUT SUNOS
verifier
verifier(1M) Application Server Utility verifier(1M)
NAME
verifier - validates the J2EE Deployment Descriptors against application server DTDs
SYNOPSIS
verifier [-v] [-d destination_directory] [-r [a|w|f]] jar_filename
Use the verifier utility to validate the J2EE deployment descriptors and the Sun ONE Application Server specific deployment descriptors. If
the application is not J2EE compliant, an error message is printed.
When you run the verifier utility, two results files are created in XML and TXT format. The location where the files are created can be
configured using the -d option. The directory specified as the destination directory for result files should exist. If no directory is
specified, the result files are created in the current directory. Result files are named as jar_filename_verified.xml and jar_filename_ver-
ified.txt
The XML file has various sections that are dynamically generated depending on what kind of application or module is being verified. The
root tag is static-verification which may contain the tags application, ejb, web, appclient, connector, other, error and failure-count. The
tags are self explanatory and are present depending on the type of module being verified. For example, an EAR file containing a web and EJB
module will contain the tags application, ejb, web, other, and failure-count.
If the verifier ran successfully, a result code of 0 is returned. A non-zero error code is returned if the verifier failed to run.
OPTIONS
-v verbose debugging is turned on.
-d identifies where the result files get placed.
-r identifies the reporting level defined as one of the following:
o a sets output reporting level to display all results (default)
o w sets output reporting level to display warning and failure results
o f sets output reporting level to display only failure results
jar_filename name of the ear/war/jar file to perform static verification on. The results of verification are placed in two files
jar_filename_verified.xml and jar_filename_verified.txt in the destination directory.
Example 1: Using verifier in the Verbose Mode
example% verifier -v -d /verifier-results -rf sample.ear
Where -v runs the verifier in verbose mode, -d specifies the destination directory, and -rf displays only the failures. The results are
stored in /verifier-results/sample.ear_verified.xml and /verifier-results/sample.ear_verified.txt.
asadmin(1M)
Sun Java System Application Server March 2004 verifier(1M)