Sponsored Content
Full Discussion: Patchadd error
Operating Systems Solaris Patchadd error Post 302103630 by reborg on Friday 19th of January 2007 04:44:10 PM
Old 01-19-2007
I'm not sure here, but it may be an issue with broken patching tools 119254-14 was a fix for that. Rev 21,22,23 of 118833 had problems with those driver modules, and I am guessing that the faulty patches weren't properly removed.
 

8 More Discussions You Might Find Interesting

1. Solaris

patchadd/patchrm

Ok, I attempted to apply a patch to a V440 and it bailed part way through. When I tried to patchrm the patch (after booting from CD), patchrm said that I had to fully install the failed patch before I could delete it. Since installing it killed the system forcing a boot from CD, it sounds like a... (4 Replies)
Discussion started by: BOFH
4 Replies

2. Solaris

patchadd fails to apply a patch

Hello, I'm trying to apply the patch on Solaris 9 : $/jac/update$ patchadd ./112945-46 Checking installed patches... One or more patch packages included in 112945-46 are not installed on this system. Patchadd is terminating. The error message is not really talkative so I had a... (7 Replies)
Discussion started by: Tex-Twil
7 Replies

3. Solaris

patchadd error

Greetings All- I ran into this problem today and was curious if anyone else had seen it. I am attempting to add patch 137402-02 on a v890 running Sol9. Here's the error I get: #> patchadd 137402-02 Checking installed patches... Verifying sufficient filesystem capacity (dry run... (7 Replies)
Discussion started by: bluescreen
7 Replies

4. Solaris

patchadd command

# patchadd /Desktop/117837-08.jar Validating patches... Loading patches installed on the system... Done! Loading patches requested to install. Done! The following requested patches have packages not installed on the system Package SPROcc from directory SPROcc in patch 117837-08 is... (19 Replies)
Discussion started by: seyiisq
19 Replies

5. Solaris

patchadd -p ,, basic question

greetings, I am new to solaris, have a basic question. I have to check for patch 137111-04 (as prerequisite) for installing Oracle. # patchadd -p | grep 137111-04 # patchadd -p | grep 137111 Patch: 137137-09 Obsoletes: 120741-01 120986-12 120992-02 121008-02 121274-01 121414-01... (2 Replies)
Discussion started by: mubeenmd
2 Replies

6. UNIX for Dummies Questions & Answers

> 5 ")syntax error: operand expected (error token is " error

im kinda new to shell scripting so i need some help i try to run this script and get the error code > 5 ")syntax error: operand expected (error token is " the code for the script is #!/bin/sh # # script to see if the given value is correct # # Define errors ER_AF=86 # Var is... (4 Replies)
Discussion started by: metal005
4 Replies

7. Cybersecurity

How to limit patchadd command to root user only?

How to limit patchadd command to root user only? I'm running a solaris 10 5/09 server, I have 2 users other than root. One being able to use the patchadd command and one is unable to do so. What I'm trying to do is to limit the patchadd command so that only root is able to run it. (7 Replies)
Discussion started by: ShouTenraku
7 Replies

8. Solaris

I am new & I have a question about patchadd in Solaris 11

Hi guys, I am really new to Solaris. My question is about the patching package management. Now I was provided some old packages within that there are hard-coded codes written with commands like "patchadd", so anyway I can make them work with Solaris 11? Cheers! (8 Replies)
Discussion started by: ethanzhou
8 Replies
WBWD(4) 						   BSD Kernel Interfaces Manual 						   WBWD(4)

NAME
wbwd -- device driver for watchdog timer found on Winbond Super I/O chips SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file: device wbwd Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): wbwd_load="YES" DESCRIPTION
The wbwd driver provides watchdog(4) support for the watchdog interrupt timer present on at least the following Winbond Super I/O chips: o 83627HF/F/HG/G Rev. G o 83627HF/F/HG/G Rev. J o 83627HF/F/HG/G Rev. UD-A o 83627DHG IC ver. 5 SYSCTL VARIABLES
The wbwd driver provides the following options as sysctl(8) variables. dev.wbwd.0.timeout_override This variable allows to program the timer to a value independent on the one provided by the watchdog(4) framework while still relying on the regular updates from e.g. watchdogd(8). This is particularly useful if your system provides multiple watchdogs and you want them to fire in a special sequence to trigger an NMI after a shorter period than the reset timeout for example. The value set must not be lower than the sleep time of watchdogd(8). A value of 0 disables this feature and the timeout value provided by watchdog(4) will be used. dev.wbwd.0.debug_verbose If set this sysctl will tell the driver to log its current state before and after the timer reset on each invocation from watchdog(9) to the kernel message buffer for debugging. dev.wbwd.0.debug This read-only value gives the state of some registers on last update. The wbwd driver also provides further sysctl options that are hidden by default. See the source code for more information. SEE ALSO
watchdog(4), device.hints(5), watchdog(8), watchdogd(8), watchdog(9) HISTORY
The wbwd driver first appeared in FreeBSD 10.0. AUTHORS
This manual page was written by Bjoern A. Zeeb <bz@FreeBSD.org>. BSD
December 28, 2012 BSD
All times are GMT -4. The time now is 10:57 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy