Sponsored Content
Operating Systems Solaris Contents deleted from /var/sadm Post 303004265 by drysdalk on Thursday 28th of September 2017 04:03:17 PM
Old 09-28-2017
Hi,

Oh dear, that is...unfortunate. The primary purpose of the directory tree underneath /var/sadm on Solaris is to store information about all installed packages and patches. So basically, it's entirely system-dependent. No two servers will have the same contents in there, unless they've had exactly (and I really do mean exactly) the same life in terms of the OS install options, subsequently-added packages and applied patches all being 100% identical at every step of the way.

So in other words, unless this server happens to have a sibling system that has identical hardware, an identical patch level of the OS, and absolutely identical sets of installed software and patches, with literally no differences between the two systems in any way whatsoever, then the contents of /var/sadm are going to be different. It's not really a transplantable directory, sadly.

If it were me, and I had a system with a hosed /var/sadm and genuinely no backups, I'd most likely be looking at migrating services off of it on to another server, and re-installing the broken box. Unless you are happy never being able to install any packages or apply any patches (an unwise situation to be in, generally speaking), then that is probably your only way out of this without backups, I'm sorry to say.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

/var/sadm/install

Hi, can I delete the file install in /var/sadm directory because I do not need. Regard TDS (1 Reply)
Discussion started by: tinfoul
1 Replies

2. UNIX for Dummies Questions & Answers

Deleted /var/adm/sw/patch

I am on a HP-UX 11.0 machine and I deleted '/var/adm/sw/patch'. I realize now what a mistake this was. Since doing this I can no longer export display to remotely view netscape. At this point, what are my options for recovering the 'patch' directory? I don't have a backup. Any help would... (0 Replies)
Discussion started by: lucesean
0 Replies

3. UNIX for Dummies Questions & Answers

accidentally remove the contents of /var/sadm/pkg

Hi all, I carelessly remove the contents of /var/sadm/pkg. I do not have any backup of the folder. What can I do ? Thanks a lot. :eek: (11 Replies)
Discussion started by: stancwong
11 Replies

4. Solaris

Directory should not be deleted, But the contents can be

Hi Guys, I have an user's home directory set to /home/A And A contains the following directories B & C Is there some way in solaris by which i can prevent the directories B and C from getting deleted by the user but the contents of the directories B & C can be deleted ? Also i have... (2 Replies)
Discussion started by: localhost
2 Replies

5. Shell Programming and Scripting

Resolving Var to its contents

Hello everyone.... I am trying to dinamically create variable names and do resolution of this vars contents. After that is done I want to use (via a function call) the var and its contents by referring to it via the variable name. I am having a hard time achieving this .... can you help ? ... (5 Replies)
Discussion started by: gio001
5 Replies

6. Solaris

Content of /var/sadm/pkc/<pkg>/save directory

Hi, What are the contents of /var/sadm/pkg/<pkg>/save directory. - It contains various patches with their id's. What does the "pspool" directory inside it contain? (6 Replies)
Discussion started by: vibhor_agarwali
6 Replies

7. Solaris

Lost /var/sadm/install/contents file and /var/sadm/pkg

Hello, I recently found that my /var/sadm/install/contents, ~/admin/default, /var/spool/patch and /var/spool/pkg files were empty. This broke the pkginfo, pkgchk and other package related tools. The pkgmap no longer points to where the applications have been installed. I have replaced the... (0 Replies)
Discussion started by: ronin42
0 Replies

8. Solaris

Cleaning out /var/sadm/patch after Live Upgrade

I recently upgraded my OS to Solaris 10 10/09 from Solaris 10 06/06 using Live Upgrade. I wanted to clean up space in /var/sadm/patch. I'm assuming the server is now clean with a fresh version of Solaris 10 10/09. Can I safely remove everything in /var/sadm/patch? Thanks, jeremy (0 Replies)
Discussion started by: griff11
0 Replies

9. Solaris

/var/adm & /var/sadm

what is the difference between tha /var/adm and /var/sadm files in solaris 10 Os please can any one respond quickly thanking you (2 Replies)
Discussion started by: wkbn86
2 Replies

10. Shell Programming and Scripting

Accidently deleted /usr contents.

Hi I have the following code which was supposed to clean up a directory when the number of files in that directory exeeded 2.The code is given below. #!/usr/bin/ksh dir_num=`/usr/bin/find /var/.audit -type d | /usr/bin/wc -l` if then oldest_file=`/usr/bin/ls -1t | /usr/bin/tail... (19 Replies)
Discussion started by: chacko193
19 Replies
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 new-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.10 29 Jun 2004 contents(4)
All times are GMT -4. The time now is 06:45 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy