10 More Discussions You Might Find Interesting
1. Red Hat
Hi,
Please suggest steps to change grub from /dev/sda to /dev/sdb, (1 Reply)
Discussion started by: manoj.solaris
1 Replies
2. Shell Programming and Scripting
Objective: To recreate the partitioning setup of /dev/sda on /dev/sdc
How would I parse the below information and initialize variables
(an array?) that can be used to build sgdisk commands in a script, regardless of the number of partitions?
Something along the lines of:
sgdisk -n... (12 Replies)
Discussion started by: RogerBaran
12 Replies
3. What is on Your Mind?
Any Unix Admins out there who were tasked with upgrading and maintaining java/jboss installs and possibly related apps?
How did it work out?
Any tools to allow developers to tweak their java settings, like a console? I just started looking into this, if anyone has experience I'd appreciate... (0 Replies)
Discussion started by: allenhibbert
0 Replies
4. Solaris
So, we removed a LUN from the SAN and the system is refusing to remove the references to it in the /dev folder. I've done the following:
devfsadm -Cv
powermt -q
luxadm -e offline <drive path>
luxadm probe
All those commands failed to remove the path. The drive stills shows up as <drive... (13 Replies)
Discussion started by: DustinT
13 Replies
5. Programming
These days i am learning more about Java language and feel it is an interesting language than others.
Is there some books on it to make this language easy to me? (2 Replies)
Discussion started by: ggiwebsinfo
2 Replies
6. Programming
Hi guys,
I'm going to start studding about J2EE in a couple of weeks. I have no idea about its technologies. what prerequisites do i need. I only know java and have basic knowledge about HTML. I have a solid knowledge on database.
1. Do i need java script or CSS knowledge for JSP and JSF?
2.... (1 Reply)
Discussion started by: majid.merkava
1 Replies
7. UNIX for Advanced & Expert Users
Would like to confirm the ff. I got confused actually with the version I needed to download that will work on glassfish 3.0.1
a. Debian Squeeze (HP DL360). Need to use java version6
On Debian, I did apt-get install sun-java6-jdk. So when I check it's
java version "1.6.0_22"
Java(TM) SE... (1 Reply)
Discussion started by: lhareigh890
1 Replies
8. Solaris
Hi, Anyone can help
My solaris 8 system has the following
/dev/null , /dev/tty and /dev/console
All permission are lrwxrwxrwx
Can this be change to a non-world write ??
any impact ?? (12 Replies)
Discussion started by: civic2005
12 Replies
9. UNIX for Dummies Questions & Answers
hello everyone,
i wish to know anyone have any recommended good book about unix from for beginner until advanced?
i wish to buy just 1 book, that include most of the useful part.
i just review a book name "UNIX - in the nutshell 4th edition", is it suitable for me as a newbie?
If not, any else... (4 Replies)
Discussion started by: chuwfan
4 Replies
10. Solaris
Hi, I'm tryng to install the J2EE 1.4 on Solaris 8, but I'm getting an error message, saying I don't have enough space on the device....but I DO have...heres a df -k:
I'm trying to install in /export/home.......
Help?? (12 Replies)
Discussion started by: Zarnick
12 Replies
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)
11-27-2011
