8月20,21日 :: mmmmn
mmmmn · 2004-09-24
资料收集
|
首页
|
8月22,23日>>>
8月20,21日
时间:2004-09-24
1、一个BUG:XVR-100使用100%的CPU,在fbpm 功能被允许的时候。
这个BUG被114537-22 solais8
114537-22 solaris9所修复
2、关于进程调度
There's some confusion here, partially due to some odd bits of Solaris
parlance. The "scheduler", known as PID 0, process "sched", only
handles swapping whole processes to and from disk. The subsystem
which handles picking which processes to run, preempting running
threads, etc. is known as the "dispatcher". Note that there is no
seperate "dispatcher" thread -- all the dispatcher work happens on an
"as needed" basis by all the threads in the system.
Threads which are in the dispatcher code cannot be preempted -- it all
runs at high PIL (DISP_LEVEL, or 11), which is above LOCK_LEVEL (10),
which means that the thread block or be preempted. It *can* be
interrupted by high-level interrupts (for example, by the timer
interrupt, which runs at PIL 14), but those don't change the
progression.
Jim Mauro's "Inside Solaris" articles (later pulled together and
expanded into the "Solaris Kernel Internals" book, which is
recommended reading) on the dispatcher are still reasonably accurate,
even though it only talks about releases up to Solaris 7:
http://sunsite.uakom.sk/sunworldonline/swol-01-1999/swol-01-insidesolaris.html
http://sunsite.uakom.sk/sunworldonline/swol-02-1999/swol-02-insidesolaris.html
(The details have gotten a bit more complicated in later releases, but
the broad sweep is the same)
http://sunsite.uakom.sk/sunworldonline/swol-12-1998/swol-12-insidesolaris.html
- jonathan
3、在solaris8及以前的版本,如果在patchadd后面跟的格式不会,则会有不正常的信息显示
在solaris9以后,可以跟不同的扩展名。例如:
[root@m2 /tmp]# patchadd 117171-08.jar
Verifying signed patch <117171-08>...
Verifying digital signature for signer <es-signature>
Digital signature for signer <es-signature> verified.
Verifying contents of signed patch </tmp/117171-08.jar>
Contents of signed patch </tmp/117171-08.jar> verified.
Signature on signed patch <117171-08> has been verified.
Extracting patch contents...
Checking installed patches...
Verifying sufficient filesystem capacity (dry run method)...
Installing patch packages...
Patch number 117171-08 has been successfully installed.
See /var/sadm/patch/117171-08/log for details
Patch packages installed:
FJSVhea
SUNWcar
SUNWcarx
SUNWcpc
SUNWcpcx
SUNWcsr
SUNWcsu
SUNWcsxu
SUNWhea
或:
[root@m2 /tmp]# patchadd
http://patches.sun.com/all_signed/117175-01.jar
Downloading patch from <
http://patches.sun.com/all_signed/117175-01.jar
>...
..............25%..............50%..............75%..............100%
## Downloading...
## Download Complete
Verifying signed patch <117175-01>...
Verifying digital signature for signer <es-signature>
Digital signature for signer <es-signature> verified.
Verifying contents of signed patch </tmp/patchadd-dwnld/117175-01.jar>
Contents of signed patch </tmp/patchadd-dwnld/117175-01.jar> verified.
Signature on signed patch <117175-01> has been verified.
Extracting patch contents...
Checking installed patches...
Patch 117175-01 has already been applied.
See patchadd(1M) for instructions.
Patchadd is terminating.
4、在X86系统和SPARC系统的打印配置设置几乎一样,可以参照下面的文章进行配置:
http://www.sun.drydog.com/faq/6.html#6.4
最主要的区别是把FAQ中的/dev/lp1 替换成在U60系统下的/dev/ecpp0
注意在FAQ中的laserjet.fd文件中Command行最后有一个“-”,很多人都忽略了它。并且注意gs命令也会根据Ghostscript的安装不同而路径不同。
5、在solaris10上使用一个包的库的方式保存关于安装的包的信息,大大增强了对信息的保护功能
问题:在solaris8中已经安装了SUNWcsu包,但是pkginfo不显示那个包存在。而且在/var/sadm/pkg下也有一个SUNWcsu的目录。系统运行正常,但是很多软件安装的时候都报没有找到SUNWcsu而无法安装。
解决:在/var/sadm/pkg/SUNWcsu目录下还有一个隐藏的目录:.save.SUNWcsu,在该目录下有一个空的文件pkginfo。pkginfo命令就是扫描这个文件来返回信息。把这个文件删除后就可恢复
mmmmn
引用Trackback(0)
|
编辑
评论
发表评论
最后更新
原始快照:web.archive.org