03-14-2012
Have you done any work on the whole root zone, all my zones are sparse so I have no experience of whole root zones - but i have seen a very similar error generated during the live upgrade process.
What if anything was done while the zone was down or being rebooted?
Regards
Dave
5 More Discussions You Might Find Interesting
1. Red Hat
Is there not one of us who can help here?? I'm really letting down my
pants here - not sure what's going on but if you could foreward this
link to a group you may know I would greatly appreciate it. I'm getting this error:
May 30 22:18:35 MYSERVERNAME sendmail: j4V2HWka015549: ... (1 Reply)
Discussion started by: angelohl
1 Replies
2. Linux
I am using Linux box. i am able to send mails through sendmail to local and other domains.
i am not receving any incoming mails.
dovecot service is running. (4 Replies)
Discussion started by: harishindn
4 Replies
3. Shell Programming and Scripting
Hi,
We are using a shell script which is called from COBOL program. Here the program works fine till we are using MicroFocus(MF) COBOL 4 and UNIX AIX 5.3.
Recently we have upgraded to MicroFocus(MF) COBOL 5.1 but same AIX version. now the shell script not working as expected.
The shell... (5 Replies)
Discussion started by: vensk27
5 Replies
4. UNIX for Dummies Questions & Answers
Hi Folks,
I have opened a log file through Vi editor in putty itself and I was searching for a pattern in logs , let say 'ABCD'
/abcd
then I want to come out from vi editor, Please advise what is the command to come out from unix editor..! (1 Reply)
Discussion started by: KAREENA18
1 Replies
5. Infrastructure Monitoring
Issue: I'm not receiving notifications
I can succesfully receive an e-mail if I do this on the command line:
/usr/bin/mail -s "NAGIOS HOST ALERT on $HOSTNAME$" rgouette@butlerbros.com
but, my command.cfg configuration below, refuses to send an e-mail when I set a service to a critical... (3 Replies)
Discussion started by: rgouette
3 Replies
LEARN ABOUT OPENDARWIN
rem_drv
rem_drv(1M) rem_drv(1M)
NAME
rem_drv - remove a device driver from the system
SYNOPSIS
rem_drv [-b basedir] device_driver
The rem_drv command informs the system that the device driver device_driver is no longer valid. If possible, rem_drv unloads device_driver
from memory. rem_drv also updates the system driver configuration files.
If rem_drv has been executed, the next time the system is rebooted it automatically performs a reconfiguration boot (see kernel(1M)).
The following options are supported:
-b basedir Sets the path to the root directory of the diskless client. Used on the server to execute rem_drv for a client. The client
machine must be rebooted to unload the driver.
Note - The root file system of any non-global zones must not be referenced with the -b option. Doing so might damage the
global zone's file system, might compromise the security of the global zone, and might damage the non-global zone's
file system. See zones(5).
Example 1: Removing the sd Driver
The following example removes the sd driver from use:
example% rem_drv sd
Example 2: Removing a Diskless Client
The following example removes the driver from the sun1 diskless client. The driver is not uninstalled or unloaded until the client machine
is rebooted.
example% rem_drv -b /export/root/sun1 sd
Note the caveat on the use of the -b option in the description of that option, above.
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
add_drv(1M), kernel(1M), update_drv(1M), attributes(5), devfs(7FS)
6 Apr 2005 rem_drv(1M)