Skip to content, navigation.
Just a quick note:
I have released SLX 03 - Server Impact. This is a work in progress and I will be adding a new PDF to it with full statistics showing real server impact from DirTracer. I have the test servers and slamd setup and will get the tests run soon.
Cheers!
Lee
Alo all,
I received good news from the Big Admin admins today, the new DirTracer and Pkgapp versions are online!
The following versions are now available here on Big Admin. For information on the latest changes in this update, please see my previous blog - DT 6.0.7 Coming soon!
DirTracer 6.0.7 
Pkgapp 3.2
I have also released the SLX 02 DirTracer Quickstart on SLX (Sun Learning Exchange) - "This video is a Quickstart guide to getting DirTracer6 running in a short amount of time using Configurator 6. I also step through a real example of how DirTracer runs using the config file created by Configurator."
Finally, I am in production of the latest DirTracer SLX video "Server Impact". Using Slamd, Cacti and DirTracer I plan on showing exactly what impact a Directory Server will see from DirTracer runs based on different run/problem types. More on this later.
Cheers!
Lee
Hey all,
Quick tech tip here.
We recently came
across a situation where a Customer ran DirTracer 3 separate times in
the same second; one for each of the three instances on a single
system. Each config file had the correct configuration for each
instance but all three were used at the same time.
Example: Using a wrapper script to launch all 3 in the same second.
#!/bin/sh
nohup ./dirtracer -f ./dirtracer.config.1 &
nohup ./dirtracer -f ./dirtracer.config.2 &
nohup ./dirtracer -f ./dirtracer.config.3 &
As
a result, DirTracer is launched 3 times in the same second and each
see's that there is no existing sub-databin inside /var and only 1
sub-databin is created; i.e. /var/072309-01.
<snip>
* Using config file [./dirtracer.config.1]
* Using config file [./dirtracer.config.2]
* Using config file [./dirtracer.config.3]
* Dirtracer mainloop will run for * Dirtracer mainloop will run for * Dirtracer mainloop will run for[100 sec. Between 1 & 2 min.]
[100 sec. Between 1 & 2 min.]
[100 sec. Between 1 & 2 min.]
* Databin parameter check 1 * Databin parameter check 1 * Databin parameter check 1[success]
[success]
[success]
* Databin parameter check 2 * Databin parameter check 2 * Databin parameter check 2[success]
[success]
[success]
* Databin Found [/var]
* Databin Found [/var]
* Databin Found [/var]
* Databin used is * Databin used is * Databin used is[/var/072309-01]
[/var/072309-01][/var/072309-01]
<snip>
To ensure DirTracer runs properly and uses a separate sub databin (as intended) the following workaround can be used.
#!/bin/sh
nohup ./dirtracer -f ./dirtracer.config &
sleep 1
nohup ./dirtracer -f ./dirtracer.config &
sleep 1
nohup ./dirtracer -f ./dirtracer.config &
By giving DirTracer a 1 second delay between executions gives it enough time to notice there is an exiting sub-databin in the intended path and increment the sub-databin number.
Example:
myzone root[/var/tmp/data]# ls -l
drwxr-xr-x 11 root root 30 Jul 23 14:48 072309-01
drwxr-xr-x 11 root root 30 Jul 23 14:48 072309-02
drwxr-xr-x 11 root root 30 Jul 23 14:48 072309-03
Hope this helps...
Cheers,
Lee
Hi all,
Good news is always welcome :D
I have finalized testing of not only DirTracer (DT) 6.0.7 but have also finished coding and testing of Pkgapp 3.2 for both Redhat and SuSE Linux. 
See my previous blog DT 6.0.7 Coming soon! or the README.dirtracer for details on what has changed.
Available DirTracer and Pkgapp versions:
Remember: DirTracer comes with Pkgapp (see the dirtracertools path) but for non Sun Directory Server customers, Pkgapp 3.2 can be downloaded separately.
Currently these versions are only available internally until BigAdmin can update their copies. Until that happens, contact your Sun Customer Service Representative and have them send you the latest versions.
Enjoy!
Lee
Hi all,
Well, I hopped on the fix for the last updates bug so fast I decided to just release a new version of DirTracer (DT 6.0.7).
Here is a list of the current change's...
DirTracer:As the changes only affected a couple of bugs I will not be reworking the pdf doc giude to reflect the new version information. This also allowes me to quickly generae and release new fixes for current issues.
I have made the above changes to the Solaris Sparc, Solaris x86, Linux and HP-UX versions. I have not coded a new version of Pkgapp 3.2 yet for HP-UX so I will release this version a bit later. I will update soon when I have released DirTracer internally for download. Once I do and you wish to get a copy, please contact your Sun Frontline Engineer.
Regards,
Lee
Hi all,
Quick update on DirTracer. I knew about this issue for a couple of months but haven't had time to deal with it. I have created a bug (see below) and a fix. I will try to get this out soon as DirTracer 6.0.7. The fix is already in DT7 (DirTracer 7)
CR 6861010 DirTracer 6.0.6 incorrectly identifies the DS as 64bit if running in as 32bit on AMD64
Cheers all
Lee
Great news all,
I have released my first vidcast on Sun's Learning Exchange (SLX) site! 
SLX 01 - DirTracer Overview (runtime 7min 32sec)
This is the first in what I hope to be a long series discussing DirTracer, Configurator and Pkgapp. If you are unfamiliar with DirTracer, this Overview is an easy and fast way to get acquainted with Sun's #1 Directory support tool.
On July 24th I will be releasing the second vidcasts titled "DirTracer Quickstart". This will walk you through getting DirTracer up and running in the shortest amount of time using Configurator.
I am currently in production on the third vidcast titled "Server Impact". This is a hot topic when it comes to running DirTracer on production systems.
That's all for now folks,
Enjoy
Lee
Hello all,
I was approached today by a Partner about running DirTracer in the background. I believe I have been asked about this once before.
Currently I have not tested nor can DirTracer be run in the background. I just tried this in fact and saw nothing in the databin path, nor in the /tmp area for the runtime log. I have found a way however.
If I background or no hup it I get no output -> (nohup ./dirtracer -f ./dirtracer.config &).
But if I create a stub script that launches DirTracer with nohup and & and do the same with the stub...it works.
myzone root[/opt/dirtracer]#cat backgrounder
#!/bin/sh
nohup ./dirtracer -f ./dirtracer.config &
myzone root[/opt/dirtracer]#nohup ./backgrounder &
[1] 9159
myzone root[/opt/dirtracer]#Sending output to nohup.out
[1] Done ./backgrounder
In most circumstances, (99% of the time) you should be running DirTracer in the foreground because the runtime is generally short. I can only see backgrounding the process when you use the MEM_LEAK_TRACKING option or if you have such a long DirTracerrun that you will have to close down your terminals and leave.
Thanks to Brian for this great question.
Lee
Hey all,
Quick update to say Pkgapp 3.2 is now available externally on the Big Admin scripts site. You can download it here.
Currently I am working on Pkgapp 3.2 ports to Linux.
Big Admin Scripts: Sun Java System Category
Cheers!
Lee
Yes it's true! DirTracer now works with DS7!
I was fortunate to get access to DS7 during the Directory Masters event in New Jersey. While there I was able to quickly install DS7 and migrate an old dead DS6.2 instance. I ran DT 6.0.6 against this new instance and was ecstatic to see it ran with 0 errors. In reality DS Development had moved two commands but DT had used its defaults to guess things like install type (zip/native) and where the dsrk's ldapsearch and ldapmodify were located.
Today I decided to revisit these two items and found it was easy as pie to change; only took a few minutes. I had to copy/paste and change approximately seven lines of code (mostly path based) and that was it.
To mirror the DT version I used when DS6 was released, I will now re-version this as DirTracer 7.0.0 or DT7. While DT7 works perfectly with DS7, I'm not saying DT7 won't change. In fact I'm planning many new features for DT7 for its first
--------------------------------------------------------------------------------
Sun Microsystems dirtracer 7.0.0 Solaris Sparc 05/26/2009
--------------------------------------------------------------------------------
* Checking Config File [success 1211182548 != 3006111464]
* Using config file [./dirtracer.config]
* OS Type and Version [SunOS 10 sparc]
* Dirtracer mainloop will run for [1 sec.]
* Databin parameter check 1 [success]
* Databin parameter check 2 [success]
* Databin Found [/var/tmp/dtcapture]
* Databin used is [/var/tmp/dtcapture/052609-02]
* Relocating runtime log [success]
* Case Number [NOT AVAILABLE]
* User is root. Continuing...
* PID Check (18925) [success]
* Process State [not hung]
* High CPU tracking [off]
* Mem Leak tracking [off]
* Config Only Capture [on]
* Pstack Force (-F) [off]
* Instance Name is [/opt/dsee62/ldapinst3]
* Using host name [s-6000a-t6300i-zone8-sca11]
* Using host id [84aaaac8]
* Ldap Tools Path [/opt/dsee7/dsrk/bin]
* DS Version [7.0 - 64 bit - zip install]
* Backends Found [sun]
* Transaction log location [/opt/dsee62/ldapinst3/db]
* Solaris tar found [/usr/sbin/tar]
* gzip found [/bin/gzip]
* elfdump found [/usr/ccs/bin/elfdump]
* pstack found [/bin/pstack]
* prstat found [/bin/prstat]
* netstat found [/bin/netstat]
* iostat found [/bin/iostat]
* vmstat found [/bin/vmstat]
* mpstat found [/bin/mpstat]
* ldapmodify found [/opt/dsee7/dsrk/bin/ldapmodify]
* ldapsearch found [/opt/dsee7/dsrk/bin/ldapsearch]
* pms.sh found [/opt/dirtracer/dirtracertools/pms.sh]
* Access/Error Logging [left as is]
* Audit Logging [left as is]
* Iostat available. Executing... [success]
* Vmstat available. Executing... [success]
* Mpstat available. Executing... [success]
* pms.sh (pmonitor) executed [success]
* pms.sh interval(1) x checks(1) [pms.sh run time (1 sec.)]
*
* Entering Main Performance Gathering Loop
*
* Loop 0 - 090526-132724 [pstack/prstat override on]
togo[1sec]-timer[1]
*
*
* Exiting Main Performance Gathering Loop
*
* Done gathering stats [pms.sh iostats vmstats etc]
* Access/Error Logging [left as is]
* Audit Logging [left as is]
* Logging level [left as is]
*
* Gathering needed customer defined configuration
* ls -laR of slapd Instance [success]
* nsslapd-db-home-directory [success]
* nsslapd-db-logdirectory [success]
* nsslapd-directory db [success]
* nsslapd-directory sun [success]
*
* Gathering Other Environment Information
* ns-slapd version [success]
* nsds50ruv dc=sun,dc=com [success]
* cn=config search [success]
* rootdse search [success]
* idsktune [not found]
* dirtracer7.0.0 [success]
* /etc/release [success]
* /etc/system cp: cannot access /etc/system
[failed]
* /var/adm/messages [success]
* uname -a [success]
* uptime -a [success]
* date/time [success]
* ifconfig -a [success]
* mount -p [success]
* ps -aef [success]
* pflags [failed]
* pldd [failed]
* pmap [failed]
* pfiles [failed]
* prtconf -v prtconf: devinfo facility not available
[success]
* showrev -p [success]
* swap -s [success]
* pkginfo -l [success]
* df -k [success]
* logs - access: gathering 1 files
* access [success]
* access rotation [success]
* logs - error: gathering 1 files
* errors [success]
* error rotation [success]
* logs - audit: gathering 1 files
* audit [success]
* audit rotation [success]
* config dse.ldif's [success]
* schema [success]
* shared mem files [skipped]
*
* [ALERT 1] Shared Mem files were not included in the dirtracer tar file and were NOT copied/saved to the databin.
*
* ds lib files cksum [skipped]
* ds lib files elfdump [skipped]
* Writing used dirtracer.config.last [success]
* Copying dirtracer.config.last [success]
* Writing manifest-090526-132724.log [success]
*
* Packaging files
* Preparing files - pstack [0 files]
* Preparing files - prstat [0 files]
* Preparing files - netstat [success]
* Preparing files - ds-config-data [success]
* Preparing files - ds-logs [success]
* Preparing files - ds-mmap-files [success]
* Preparing files - ds-srch-monitor [success]
* Preparing files - ds-srch-cache [success]
* Preparing files - ds-txnlogs-data [success]
* Preparing files - os-info [success]
* Preparing files - gcore [0 files]
* Preparing files - crash [0 files]
* Preparing Main file [success]
* Leaving my temp files intact
Operations Complete
--------------------------------------------------------------------------------
1) Dirtracer capture data located in directory [ /var/tmp/dtcapture/052609-02 ]
Upload "only" this file to your supportfiles.sun.com cores directory at Sun
[ dirtracer-84aaaac8-s-6000a-t6300i-zone8-sca11-090526-132724.tar.gz ]
Thank you.
Sun Software Technology Service Center (STSC)
NOTES:
1) You can check for updates to this script here:
BigAdmin - http://www.sun.com/bigadmin/scripts/indexSjs.html
2) Release Notes and Guides located here:
Docs - http://docs.sun.com/app/docs/doc/820-0437
3) GDD information located here:
Docs - http://www.sun.com/service/gdd/index.xml
4) Please send all Bugs and RFE's to the following address:
Subject "dirtracer bug/rfe" - gdd-issue-tracker@sun.com
5) Please send all other questions etc to:
Subject "dirtracer feedback" - gdd-feedback@sun.com
--------------------------------------------------------------------------------
ALERTS ENCOUNTERED: See /var/tmp/dtcapture/052609-02/ALERTS-090526-132718.log
1) Shared Mem files were not included in the dirtracer tar file and were NOT copied/saved to the databin.
As I mentioned two blogs ago I was preparing to start releasing DT Video (pocasts?) on the Sun Learning Exchange (SLX). The first draft is complete for my first video titled "DirTracer Overview". I will start production of the video later today or tomorrow and hope to release it to SLX quite soon.
Cheers!
Lee
Hi all!
Pkgapp 3.2 is available internally...yeah!
I finally had time to update the Pkgapp documentation and retest it on various application cores/gcores and it is now ready for prime time. I have also submitted it to BigAdmin and it should be available in the next few days. If you need it now, please contact your favorite Sun Support representative and request he send it from the internal download site. I will also update "this" post once Big Admin has uploaded the new version.
Pkgapp 3.2 has 2 big new features...
If the core/gcore is good, the user is given the following message:
* Checking if corefile is truncated [CORE gcore.cshttpd.28734 GOOD Core contains 293 segments ]
If the core is truncated, the user is alerted and required to answer yes/no as to whether they understand the data may be totally unusable.
* Checking if corefile is truncated [WARNING! core gcore.cshttpd.28734.truncated is truncated (40396864d bytes instead of 40397397d bytes)]
*
* ALERT! The core was found to be truncated, it therefore may not be usable
* pkgapp will continue to gather data and you can still upload the result to Sun
*
* Do you understand the core may not be usable? [yes|no] yes
[Answer was -> yes]
* Continuing...
If you use/have an RSS Reader such as NetNewsWire or Google Reader you can see the latest updates to Big Admin using the following links.
Big Admin Scripts: Sun Java System Category
Next up...I plan to finalize and release DTR and begin production of my first SLX video for Dirtracer users!
Take care,
Lee
Hi all,
Thought I would drop in a quick blog and let you know what I've been up to.
As mentioned in my last blog I was asked to present Dirtracer at the DM event. The event, hosted by Michael Melore, Wajih Ahmed and Ludovic Poitou was great! I was able to meet people I've only talked to on the phone or emailed over the past 5 years. I was able to meet with Sun Partners and Sun Development and Support Engineers...
I presented an overview of Dirtracer and its components as well as my latest project, DTR (Dirtracer Reporter); more on this below. I have to admit I was very nervous. In past lives I was a pre-sales engineer and presentations like this were easy. Needless to say I haven't presented to a large group since joining Sun; just not something I do in my Support role.
In the end I forgot about being nervous and soon was on a roll.
It was great meting you all, I had a blast. See Ludo's Sketches blog for more info on this event.
Over the past couple of months I have been ratifying a few data reporting tools I and others have created into one nice package called DTR. Dirtracer Reporter is a bundle of existing Directory Server data reporting scripts rolled into a single usable interface. DTR shines when run against Dirtracer captured data, it however can run against basic Directory Server data such as dse.ldif and log files.
I am in the final test phase and making sure a slight glitch here and there are fixed and hope to release to Big Admin in the next coming weeks. More to come on DTR soon.
One of my other sub projects which will kick off soon is the creation of SLX videos for Dirtracer. These will be video podcast in nature and will show how Dirtracer is used for various problem types.
Here is a list of topics I hope to highlight.
These videos will supplement my blog content as well as giving you audio and visual queues of how Dirtracer looks when running for a specific problem type.
Until my next blog...ciao!
Lee
I've been so busy with new tools and support calls I almost forgot to mention...I'm presenting Dirtracer and my new DTR at the Directory Masters Event in New Jersey this coming Wednesday April 29th!
I have been wacky busy in the past coupe of months getting a new version of Pkgapp3, and my new DTR (Dirtracer Reporter) ready for prime time...
If you happen to make it to the event this week, stop by and say hi!
Hope to see you there,
Lee
Hello all,
I'm please to announce I have released Pkgapp 3.0 for Solaris!
So far Pkgapp 3.0 is only availabe for Solaris but I will begin porting this code to Linux and HPUX. I wanted to get Solaris first instead of waiting for all to be done...this way at least one unix flavor is available for use.
You can obtain Pkgapp 3 from Big Admin: Pkgapp 3.0 Solaris
Sun Employees can also find information on Sunspace.
Included files:
For information on what changed, what the usage looks like and a runtime example (using mysql) see my last post - Pkgapp 3.0 code has been finalized!
Enjoy all!
Lee
Pkgapp3 is the latest update to the Sun GDD tool set. These tools are designed to help customers gather the data needed for the best possible support on their issues.
Pkgapp is a shell tool built by Sun Support Engineering to help gather all OS and application libraries used by Sun Java Systems (and others) servers at runtime. Pkgapp can be used to gather these libs, etc, from cores produced by crashes or gcores captured manually by administrators.
Pkgapp is part of the GDD (Gathering Debug Data) suite of tools and has been used for years to help Sun Support debug tricky crashes, as well as performance and memory leak problems where cores or gcores are available.
New major features in Pkgapp 3.0:
1) Now handles Java Cores and grabs jstack and jinfo.
- See the -j and -J options
2) Includes all functionality that was available in both pkg_app 2.7 and pkgcore.
3) Can allow for the temporary files to be retained in /tmp
- See the -r option
4) Allows pkgapp3 to be placed in a $PATH location; can now be run from any location.
5) Can use relative paths for the following options:
-c <core file OR pid of a running process>
-p <full path to, but not including the process binary> (ns-slapd, imapd, httpd etc.)
-s <Storage; path to store the final tar file in>
6) Retains all lib/binary paths (pkgcore) as well as the pkg_app app/ location for older pkg_app aware applications.
7) Names the final storage path as pkgapp-<date>-<index> to help administrators locate the final tar file faster.
- Ex: pkgapp3-111708-01/
8) Gathers the following Solaris only proctool commands from the core.
- pldd
- pstack
- pmap
- pcred
- pflags
- pargs
9) Checks to see if the core file is truncated and checks the core files cksum to ensure the file size match.
10) Gathers the following core and pkgapp3 specific data
- core file cksum
- core file truncation (good/bad)
- core file size (ls -l)
- library list (from the pldd)
- manifest log (all files included int he final tar)
- pkgapp3 arguments used.
11) Gathers the following OS specific data
- coreadm info
- date/time
- messages (from /var/adm)
- pkginfo
- showrev -p
- /etc/release (Solaris)
- ulimit
- uname -a
12) Creates a coreinfo.sh script to allow Sun Engineers to quickly run "coreinfo" for ns-slapd processes (only).
13) Alerts administrators they must upload 2 files (pkgapp tar & core) separately when they do not use the -i (include core) switch.
14) Will exit with a fatal error if a pldd cannot be properly retrieved from the core and alerts the administrator to run pkgapp3 using a pid as the -c option.
15) Saves the pkgapp3 arguments and runtime log into /var/tmp/pkgapp-history/. Helps administrators and pkgapp see previous runs.
16) Updated usage and alert messages.
Here are a couple previews of how the new code works.
Example: Usage output
* ----------------------------------------------------------------------------------
* Sun Microsystems RSD pkgapp 3.0 Solaris [11/24/2008]
* ----------------------------------------------------------------------------------
pkgapp 3.0, a Sun Microsystems data gathering utility.
Usage:
pkgapp [options] -c <core file | pid> -p <full path (path only) to process binary> -s [path to write tar file]
Required parameters:
-c <core file OR pid of a running process>
-p <full path to, but not including the process binary> (ns-slapd, imapd, httpd etc.)
Optional parameters:
-i (Include a previously generated core file with the final tar.gz)
-j (Javacore; process a java core)
-r (Remove all temp files)
-q (Quiet)
-d (Debug)
-J <JstackPath; path to the jstack (jdk) commands>
defaults to /usr/jdk/instances/...
-s <Storage; path to store the final tar file in>
usage: pkgapp -c <name of the core file> -p <path to process binary>
usage: pkgapp -c <pid of the running app> -p <path to process binary>
Examples: these are examples mixing various parameters
Directory Server
pkgapp -i -r -c ./core.14740 -p /var/mps/ds52p4/bin/slapd/server/64
Messaging Server
pkgapp -c ./core.3496 -p /opt/SUNWmsgsr/lib
Web Server
pkgapp -c ./core.1092 -p /space/iws70/lib -s /var/crash
Calendar Server
pkgapp -r -c ./core -p /opt/SUNWics5/cal/lib
Sendmail
pkgapp -i -c 512 -p /usr/lib
Mysqld
pkgapp -i -r -c ./core -p /support/mysql-5.0.41/bin
Example: Runtime output
* ----------------------------------------------------------------------------------
* Sun Microsystems RSD pkgapp 3.0 Solaris [11/24/2008]
* ----------------------------------------------------------------------------------
* OS release [5.10]
* Platform [SUNW,Sun-Blade-2500]
* Checking [-c] is a core or pid [using pid 1409]
* Process Root [/support/mysql-5.0.41/data]
* Databin parameter [-s] checks [reset to /var/tmp/dev]
* Databin found [/var/tmp/dev/test/cores/storage]
* Databin writable check [success]
* Databin used/created is [/var/tmp/dev/test/cores/storage/pkgapp-112408-05]
* Creating temp area [/tmp/pkgapp.2928/]
* Pid used, no corefile to check
* Process binary [mysqld]
* Checking usage history [not recently run]
* mysqld binary bit version [32]
* Checking path [-p] to binary name [success, path != binary name]
* Checking path [-p] is a directory [success]
* Locating mysqld [success]
* Checking located mysqld is 32 bit [success]
* Binary located [/support/mysql-5.0.41/bin/mysqld]
* Adding binary to pkgapp.pldd [success]
* Grabbing pldd [success]
* Grabbing pstack [success]
* Grabbing pmap [success]
* Grabbing pcred [success]
* Grabbing pflags [success]
* Grabbing pargs [success]
* Provide the full path and name to the core file
* If you do not have a core, enter "none"
* Example - /data/cores/core.1445: /var/tmp/dev/cores/core.1409
[Answer was -> /var/tmp/dev/cores/core.1409]
* Grabbing [-i] core/gcore [success]
* Javatools [-j] not set [skipped]
* Grabbing /var/adm/messages [success]
* Grabbing uname -a [success]
* Grabbing date/time [success]
* Grabbing showrev -p [success]
* Grabbing pkginfo -l [success]
* Grabbing /etc/release [success]
* Grabbing coreadm [success]
* Grabbing ulimit [success]
* Grabbing libs [success]
* Making lib paths app/ [success]
* Making lib paths libs/ [success]
* Linking libraries [success]
* Libraries linked [62 ttl]
*
* Using hostid for naming .tar.gz [837872d0]
* Writing file [pkgapp-837872d0-s4u-2500a-brm04-081124-095809.tar.gz]
*
* Done gathering files
* Writing dbxrc & opencore.sh files [success]
* Writing manifest-081124-095809.log [success]
* Writing pkgapp-args-081124-095809 [success]
* Creating final tarfile [success]
* Compressing tarfile [success]
* End of runtime logging
* Saving history info [/var/tmp/pkgapp-history/history-081124-095809.log]
* Saving runtime log [/var/tmp/pkgapp-history/runtime-081124-095809.log]
* Removing [-r] temp area/files [removed]
*
* Operations Complete
----------------------------------------------------------------------------------
Upload the following file(s) to your supportfiles.sun.com Cores Directory at Sun
1) File(s) located in directory /var/tmp/dev/test/cores/storage/pkgapp-112408-05
[ pkgapp-837872d0-s4u-2500a-brm04-081124-095809.tar.gz ]
Thank you.
Sun Software Technology Service Center (STSC)
NOTES:
1) You can check for updates to this script here:
BigAdmin - http://www.sun.com/bigadmin/scripts/indexSjs.html
2) Release Notes and Guides located here:
Docs - http://docs.sun.com/app/docs/doc/820-0437
3) GDD information located here:
Docs - http://www.sun.com/service/gdd/index.xml
4) Please send all Bugs and RFE's to the following address:
Subject "pkgapp bug/rfe" - gdd-issue-tracker@sun.com
5) Please send all other questions etc to:
Subject "pkgapp feedback" - gdd-feedback@sun.com
I will announce Pkgapp 3.0 for Solaris's availability in the next few days...stay tuned!
Lee
This blog copyright 2009 by Lee Trujillo
