- 論壇徽章:
- 0
|
到下午5點(diǎn)50
一、qmail出現(xiàn)警告，請(qǐng)問這是這么回事
Oct 8 09:05:54 SUN250A qmail: [ID 748625 mail.alert] 1034039154.980585 alert: unable to append to bounce message; HELP! sleeping...
解決了
用了cat >; wtmpx
二、root用戶和 sudo 成 root 的用戶有什么區(qū)別
sudo指令
功能： 以root的身分執(zhí)行命令
語法： sudo 其他指令
用戶： 被root加入『/etc/sudoers』文件中的用戶
1．root的密碼除了root本人知道外，不需被其他需要用到root權(quán)限用戶知道，因?yàn)槭褂胹udo時(shí)，要求輸入的密碼是『該位用戶自己的密碼』。
2．把所有可執(zhí)行sudo指令的用戶都規(guī)范在『/etc/sudoers』這個(gè)文件中，root可以很容易地掌控整個(gè)系統(tǒng)。
執(zhí)行sudo su -成root的用戶，我覺得應(yīng)該和root用戶沒什么區(qū)別吧？
而普通用戶使用sudo 來執(zhí)行只有root才能執(zhí)行權(quán)限的命令，當(dāng)然跟用root用戶執(zhí)行是不一樣的，因?yàn)檫@時(shí)候他用的還是普通用戶的環(huán)境變量啊
補(bǔ)充一下，用su -成root的用戶還是有些環(huán)境變量是和root登陸是不一樣的。另外，它們的uid也是不一樣，只有euid是相同的。
三、apache可不可以禁止http的list?
有一行"Options Indexes FollowSymLinks MultiViews"
把其中的Indexes去掉了就行了，改掉這，所有的目錄都不能瀏覽了
如果想禁止某一個(gè)或幾個(gè)目錄，可以繼續(xù)往下看
四、sendmail下的pop3該怎么開啟？？？
如果有solaris7的server版，它的easy access盤里有pop3軟件
五、solaris8 安裝完后，在字符界面中，輸入錯(cuò)誤時(shí)，卻無法退回。怎么才能解決呢？
命令行，可以用del鍵
六、怎么讓solaris7認(rèn)識(shí)40gb的IDE硬盤
用solaris 8的光盤啟動(dòng) format 然后 label一下那快盤 然后solaris 7就可以認(rèn)出40g的大小了。
七、打完補(bǔ)丁后系統(tǒng)啟不來了
由于裝應(yīng)用軟件的時(shí)候要去solaris7要打補(bǔ)丁106980－18，106541－20，107544－02，106327－14，106950－18，107081－45，107656－09，108376－37，112300－01。我安裝完之后用init 6命令重啟系統(tǒng)，console出現(xiàn)信息：
INIT: can't creat /var/adm/utmp or /var/adm/utmpx
INIT:failed write of utmpx entry:" "
INIT:failed write of utmpx entry:" "
INIT:SINGLE USER MODE
ENTER RUN LEVEL(0-6,s,S)
可是無論輸入什么，系統(tǒng)都無法重啟或者關(guān)機(jī)，仍舊出ENTER RUN LEVEL(0-6,s,S)提示，哪位大俠知道是怎么回事？多謝了
在安裝patch106950－18的時(shí)候有提示：
expr: Cannot execute /usr/lib/ld.so.1
Patch number 106950-18 has been successfully installed.
See /var/sadm/patch/106950-18/log for details
當(dāng)時(shí)沒有去看log里的詳細(xì)信息，以各位高手看來這個(gè)問題會(huì)導(dǎo)致系統(tǒng)無法重啟么？
為了感謝大家的幫助，我把問題的原因和最后的解決方法在這里簡單的總結(jié)一下：（主體是直接從Sun公司的工程師給我們的solution文檔中拷貝過來，應(yīng)該不算侵權(quán)吧，呵呵）
SRDB ID: 20987
SYNOPSIS: After installing Solaris 7 kernel patch 106541, system fails to boot with the message "INIT: Cannot create /var/adm/utmp or /var/adm/utmpx"
DETAIL DESCRIPTION:
After installing Solaris 7 kernel patch 106541 system fails to boot.
The message "INIT: Cannot create /var/adm/utmp or /var/adm/utmpx"
has more than one possible cause. However, if the Solaris 7 kernel patch
106541 was loaded just prior to the boot failure, the following
solution may apply.
SOLUTION SUMMARY:
With a Solaris software CD in the cdrom drive.
#1. boot cdrom -s
#2. mount /dev/dsk/c0t0d0s0 /a
#3. ls -l /a/devices/pseudo/sys*
If there is NO MATCH - this is the key that the kernel patch
install is the culprit. Proceed to step 4.
If there IS a match - then it is likely that something else
is responsible for the NO BOOT issue. For example,
/etc/vfstab was recently edited and the mount of /var is incorrect.
#4. Get the "postpatch" script from the 106541-05 directory. It might
still be on the hard drive, or it can be moved on to the system via
ftp. 106541-07 uses the identical postpatch script and it
can be used as an alternative to the -05 postpatch script.
#5. #ROOTDIR=/a
#export ROOTDIR
#chmod 755 postpatch
#./postpatch
#6. ls -l /a/devices/pseudo/sys*
should now see the devices:
sysmsg@0:msglog and sysmsg@0:sysmsg
#7. #cd /
#umount /a
reboot
Note: To ftp the postpatch script from a server on the network, just
use the ip address of that server. #ftp ip_address
If additional network configuration is needed to accomplish the ftp,
reference InfoDoc 19086 How to access the network from a "boot cdrom -s"
environment.
The postpatch script is shown here for reference:
#! /bin/sh
#
# This is for the remote console. It checks for existence
# of the new device nodes, and creates them if necessary. This
# code emulates what would otherwise occur in SUNWcsd/postinstall,
# it is a requirement that this code run before the reconfiguration
# reboot.
#
# ensures an entry is in /etc/name_to_major
if [ -f $ROOTDIR/kernel/drv/sysmsg ]; then
/usr/sbin/add_drv -n -b $ROOTDIR sysmsg
else
exit 0
fi
devnode=$ROOTDIR/devices/pseudo/sysmsg@0:sysmsg
grep sysmsg $ROOTDIR/etc/name_to_major >;/dev/null 2>;&1
if [ "$?" = "0" ]; then
major_sysmsg=`grep sysmsg \
$ROOTDIR/etc/name_to_major | nawk '{ print $2 }'`
else
exit -1
fi
rm -f $devnode
mknod $devnode c $major_sysmsg 0
chmod 0600 $devnode
chown root:sys $devnode
devnode=../devices/pseudo/sysmsg@0:sysmsg
devlink=sysmsg
( cd $ROOTDIR/dev ; \
rm -f $devlink ; ln -s $devnode $devlink )
devnode=$ROOTDIR/devices/pseudo/sysmsg@0:msglog
grep sysmsg $ROOTDIR/etc/name_to_major >;/dev/null 2>;&1
if [ "$?" = "0" ]; then
major_sysmsg=`grep sysmsg \
$ROOTDIR/etc/name_to_major | nawk '{ print $2 }'`
else
exit -1
fi
rm -f $devnode
mknod $devnode c $major_sysmsg 1
chmod 0600 $devnode
chown root:sys $devnode
devnode=../devices/pseudo/sysmsg@0:msglog
devlink=msglog
( cd $ROOTDIR/dev ; \
rm -f $devlink ; ln -s $devnode $devlink )
exit 0
APPLIES TO: Operating Systems, Operating Systems/Solaris, Operating Systems/Solaris/Solaris 7, OS Install/Boot, OS Install/Boot/System Boot, AFO Vertical Team Docs, AFO Vertical Team Docs/Install/Boot, AFO Vertical Team Docs/Kernel
ATTACHMENTS:
其中第四步要取postpatch腳本，由于無法從硬盤上找到，又無法與別的機(jī)器建立ftp連接，我就手工地把postpatch腳本中的命令一行行地敲進(jìn)去了，雖然麻煩了一點(diǎn)，但最終還是一切ok了，好開心��！
八、編譯時(shí)尋找的連接庫路經(jīng)如何指定？
LD_LIBRARY_PATH似乎只是補(bǔ)充指定共享庫路經(jīng)的，我的LD_LIBRARY_PATH設(shè)的是/usr/openwin/lib，但是我用gcc -o foo foo.c -lsocket的時(shí)候編譯器其實(shí)是到/usr/lib里去找libsocket.so文件，但是我的PATH等變量中并沒有制定這個(gè)目錄，難道是編譯器的默認(rèn)指定么？那么在哪里修改這個(gè)缺省值呢？
It's the system's default behavior, but you can override it using "crle"
You can take this as reference:
http://supportforum.sun.com/freesolaris/techfaqs.html?techfaqs_3057
and turn to "man crle" for more info.
|
|
免費(fèi)注冊
發(fā)表于 2002-10-09 17:54
發(fā)表于 2002-10-09 18:16
