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?
Hi,
Somebody/somebody removed all contents /vat/sadm on Solaris 10 Sparc box.
As of now server is up and running. There is no backup for this server.
If we copy contents from another equivalent server, can it work ?
We don't know if it will be fixed by booting form DVD also.
Any suggestions? (4 Replies)
Hi Friends,
Actually in an linux server , there was printer jobs files occupying more space in /var/spool/cups so i want a script for deleting the files once in two week since i need the latest two weeks files.
Thanks in advance..Waiting for the script. (2 Replies)
I am new to using zfs. I have a new Solaris 10 server and I would like to start using live upgrade to help me have a route to "get back to good" if when patching the server things go badly. In my searching so far I have found the following pages and learned a lot...
How to make and mount a... (0 Replies)
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)
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)
ludelete(1M)ludelete(1M)NAME
ludelete - delete a boot environment
SYNOPSIS
/usr/sbin/ludelete [-l error_log] [-o outfile] BE_name [-X]
DESCRIPTION
The ludelete command is part of a suite of commands that make up the Live Upgrade feature of the Solaris operating environment. See
live_upgrade(5) for a description of the Live Upgrade feature.
The ludelete command deletes all records associated with a boot environment (BE) on all defined complete BEs. A complete BE is one that is
not participating in an lucreate(1M), luupgrade(1M), or lucompare(1M) operation. Use lustatus(1M) to determine a BE's status. You can
delete neither the current BE, nor the BE that will become current upon the next reboot. Also, you cannot delete a BE that has file systems
mounted with lumount(1M) or mount(1M).
ludelete does not alter any files on the BE being deleted.
The ludelete command requires root privileges.
OPTIONS
The ludelete command has the following options:
-l error_log
Error and status messages are sent to error_log, in addition to where they are sent in your current environment.
-o outfile
All command output is sent to outfile, in addition to where it is sent in your current environment.
-X
Enable XML output. Characteristics of XML are defined in DTD, in /usr/share/lib/xml/dtd/lu_cli.dtd.<num>, where <num> is the version
number of the DTD file.
OPERANDS
BE_name
Name of the BE to be deleted.
EXIT STATUS
The following exit values are returned:
0 Successful completion.
>0 An error occurred.
FILES
/etc/lutab
list of BEs on the system
/usr/share/lib/xml/dtd/lu_cli.dtd.<num>
Live Upgrade DTD (see -X option)
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWluu |
+-----------------------------+-----------------------------+
SEE ALSO lu(1M), luactivate(1M), lucancel(1M), lucompare(1M), lucreate(1M), lucurr(1M), ludesc(1M), lufslist(1M), lumake(1M), lumount(1M), lure-
name(1M), lustatus(1M), luupgrade(1M), lutab(4), attributes(5), live_upgrade(5)SunOS 5.10 24 Jan 2002 ludelete(1M)