不知道怎么回事,无法ftp, 输入正确用户和密码,总是说"login incorrect". 看了
/etc/inetd.conf, 甚至重装了ftp 得包,还是不行。

解决

打开一窗口,实时监测inetd

truss -fa -t open,fork,exec -p 198 --> 198 为inetd 的PID

打开另一窗口,

ftp 192.168.0.10

监测窗口出现

1276: open64("/etc/shells", O_RDONLY) = 3

去查,果然/etc/shells 有毛病,如是仅有一行

/etc/ftponly

改成

/bin/ksh
/bin/sh

再FTP, 成功也

WHY 出现这个现象?俺只记得前天上机时喝了一瓶啤酒 :emn2:

boyu 回复于:2003-01-04 07:29:16
谢谢laoxia


josephxd 回复于:2003-01-04 07:54:11
謝謝了.

iricyan 回复于:2003-01-04 09:57:57
faint!

laoxia喝酒也不告诉偶!您的签名又改了!

呵呵!偶也知道了!/bin/truss!

linz 回复于:2003-01-04 10:27:30
good
呵呵就这样偷学了不少东西

llc107 回复于:2003-01-04 10:38:24
下回登录时用用户名“BEER”,口令:“tasty”就好了 :-P

hbbeger 回复于:2003-01-04 19:21:49
good

procrus 回复于:2003-01-04 19:25:47
又多了一个工具:)
谢谢laoxia

bigbear0118 回复于:2003-01-04 20:01:45
高手

hutao 回复于:2003-01-04 23:49:16
感谢laoxia:)

race 回复于:2003-01-05 10:04:34
老下,多写点嘛

laoxia 回复于:2003-01-05 10:16:11
等俺下次喝完啤酒D

race 回复于:2003-01-05 10:21:02
我送您1箱百威

mmmmn 回复于:2003-01-05 12:08:13
Cool Commands
Peter Baer Galvin

There are so many commands in Solaris that it is difficult to separate the cool ones from the mundane. For example, there are commands to report how much time a program spends in each system call, and commands to dynamically show system activities, and most of these commands are included with Solaris 8 as well as Solaris 9. This month, I’m highlighting some of the commands that you might find particularly useful.

Systems administrators are tool users. Through experience, we have learned that the more tools we have, the better able we are to diagnose problems and implement solutions. The commands included in this column are gleaned from experience, friends, acquaintances, and from attendance at the SunNetwork 2002 conference in September. “The /procodile Hunter” talk by Solaris kernel developers Brian Cantrill and Mike Shapiro was especially enlightening and frightening because Cantrill wrote code to illustrate a point faster than Shapiro could explain the point they were trying to illustrate!

Useful Solaris Commands

truss -c (Solaris >= 8): This astounding option to truss provides a profile summary of the command being trussed:


$ truss -c grep asdf work.doc
syscall seconds calls errors
_exit .00 1
read .01 24
open .00 8 4
close .00 5
brk .00 15
stat .00 1
fstat .00 4
execve .00 1
mmap .00 10
munmap .01 3
memcntl .00 2
llseek .00 1
open64 .00 1
---- --- ---
sys totals: .02 76 4
usr time: .00
elapsed: .05
It can also show profile data on a running process. In this case, the data shows what the process did between when truss was started and when truss execution was terminated with a control-c. It’s ideal for determining why a process is hung without having to wade through the pages of truss output.


truss -d and truss -D (Solaris >= 8): These truss options show the time associated with each system call being shown by truss and is excellent for finding performance problems in custom or commercial code. For example:


$ truss -d who
Base time stamp: 1035385727.3460 [ Wed Oct 23 11:08:47 EDT 2002 ]
0.0000 execve(“/usr/bin/who”, 0xFFBEFD5C, 0xFFBEFD64) argc = 1
0.0032 stat(“/usr/bin/who”, 0xFFBEFA98) = 0
0.0037 open(“/var/ld/ld.config”, O_RDONLY) Err#2 ENOENT
0.0042 open(“/usr/local/lib/libc.so.1”, O_RDONLY) Err#2 ENOENT
0.0047 open(“/usr/lib/libc.so.1”, O_RDONLY) = 3
0.0051 fstat(3, 0xFFBEF42C) = 0
. . .
truss -D is even more useful, showing the time delta between system calls:

文章整理:西部数码--专业提供域名注册虚拟主机服务
http://www.west263.com
以上信息与文章正文是不可分割的一部分,如果您要转载本文章,请保留以上信息,谢谢!