can anyone explain me the difference between pkginfo and pkgchk command in solaris. Both are used to display the package details, then what is the difference between both. (5 Replies)
I received a new error that I have not seen before on my Solaris 10 server last night:
From /var/adm/messages
Jan 8 04:59:26 nediaccomp005j scsi: /pci@780/pci@0/pci@9/scsi@0 (mpt0):
Jan 8 04:59:26 nediaccomp005j Log info 31010000c received for target 1.
Jan 8 04:59:26 nediaccomp005j ... (4 Replies)
I have compiled my application on Solaris 10 with following description
SunOS ldg1 5.10 Generic_138888-03 sun4v sparc SUNW,Sun-Blade-T6320
The compiler is Sun C++ 5.9 SunOS_sparc Patch 124863-01 2007/07/25
But when installing the application on Solaris 9
SunOS odcarch02 5.9... (2 Replies)
Hi folks,
I had a sparc machine with Solaris9 and built in java1.4.2
I installed Java1.5 on top of it by running the file jre-1_5_0_22-solaris-sparcv9.sh
Now when I run the java application, I get the following error:
Error occurred during initialization of VM... (2 Replies)
Hi,
I am getting following error on my sparc box running solaris 10 -
maintenance Feb_12 svc:/network/cswvncserver:default
In log file, following logs are found -
Following logs are found -
/sbin/sh: /var/opt/csw/svc/method/svc-cswvncserver: cannot execute vncserver: couldn't find... (2 Replies)
Hi Guys,
I ran :
pkgchk
without any options
then ran
pkgchk -v SUNWluu
I get this message:
NOTE: Waiting for exclusive access to the package database.
What does this mean? And how can I fix it?
Thanks a lot for your help. (0 Replies)
Hi,
I am using solris 8 and i am unable to start my tomcat. I am getting the below error.
Error occurred during initialization of VM
Unable to load native library: ld.so.1: java: fatal: libscf.so.1: open failed: No such file or directory
Please let me know. (1 Reply)
I cannot solve the following error bellow.
Can someone help me on this please?
Mar 31 07:08:45 serverx sudo: fork
Mar 31 07:18:50 serverx sudo: fork
Mar 31 07:28:45 serverx sudo: fork
Mar 31 07:38:47 serverx sudo: fork
Mar 31 07:48:45 serverx sudo: fork
Mar 31 07:58:45 serverx... (1 Reply)
Discussion started by: pangarano
1 Replies
LEARN ABOUT OPENSOLARIS
contents
contents(4) File Formats contents(4)NAME
contents - list of files and associated packages
SYNOPSIS
/var/sadm/install/contents
DESCRIPTION
The file /var/sadm/install/contents is a source of information about the packages installed on the system. This file must never be edited
directly. Always use the package and patch commands (see SEE ALSO) to make changes to the contents file.
Each entry in the contents file is a single line. Fields in each entry are separated by a single space character.
Two major styles of entries exist, old style and new style. The following is the format of an old-style entry:
ftype class path package(s)
The following is the general format of a new-style entry:
path[=rpath] ftype class [ftype-optional-fields] package(s)
New-style entries differ for each ftype. The ftype designates the entry type, as specified in pkgmap(4). The format for new-style entries,
for each ftype, is as follows:
ftype s: path=rpath s class package
ftype l: path l class package
ftype d: path d class mode owner group package(s)
ftype b: path b class major minor mode owner group package
ftype c: path c class major minor mode owner group package
ftype f: path f class mode owner group size cksum modtime package
ftype x: path x class mode owner group package
ftype v: path v class mode owner group size cksum modtime package
ftype e: path e class mode owner group size cksum modtime package
A significant distinction between old- and new-style entries is that the former do not begin with a slash (/) character, while the latter
(new-style) always do. For example, the following are old-style entries:
d none /dev SUNWcsd
e passwd /etc/passwd SUNWcsr
The following are new-style entries:
/dev d none 0755 root sys SUNWcsr SUNWcsd
/etc/passwd e passwd 0644 root sys 580 48299 1077177419 SUNWcsr
The following are the descriptions of the fields in both old- and new-style entries.
path The absolute path of the node being described. For ftype s (indicating a symbolic link) this is the indirect pointer (link)
name.
rpath The relative path to the real file or linked-to directory name.
ftype A one-character field that indicates the entry type (see pkgmap(4)).
class The installation class to which the file belongs (see pkgmap(4)).
package The package associated with this entry. For ftype d (directory) more than one package can be present.
mode The octal mode of the file (see pkgmap(4)).
owner The owner of the file (see pkgmap(4)).
group The group to which the file belongs (see pkgmap(4)).
major The major device number (see pkgmap(4)).
minor The minor device number (see pkgmap(4)).
size The actual size of the file in bytes as reported by sum (see pkgmap(4)).
cksum The checksum of the file contents (see pkgmap(4)).
modtime The time of last modification (see pkgmap(4)).
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsr |
+-----------------------------+-----------------------------+
|Interface Stability |Unstable |
+-----------------------------+-----------------------------+
SEE ALSO patchadd(1M), pkgadd(1M), pkgadm(1M), pkgchk(1M), pkgmap(4), attributes(5)NOTES
As shown above, the interface stability of /var/sadm/install/contents is Unstable (see attributes(5)). It is common practice to use this
file in a read-only manner to determine which files belong to which packages installed on a system. While this file has been present for
many releases of the Solaris operating system, it might not be present in future releases. The fully supported way to obtain information
from the installed package database is through pkgchk(1M). It is highly recommended that you use pkgchk rather than relying on the contents
file.
SunOS 5.11 20 Dec 2007 contents(4)