Bug 139866
Summary: | rsh -d doesn't do anything | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Bastien Nocera <bnocera> |
Component: | rsh | Assignee: | Karel Zak <kzak> |
Status: | CLOSED NOTABUG | QA Contact: | Ben Levenson <benl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | rvokal, tao |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-11-25 10:25:09 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Bastien Nocera
2004-11-18 15:39:27 UTC
And what is your expected result for this? I have absolutely no idea... -d means socket debugging. You have to use it with something other, for example: rsh -d <host> <command> It works for me. If you haven't idea I have one nice idea -- I'm going to close this report as Not A Bug :-) What's the difference between: rsh -d <host> <command> and rsh -d 172.31.0.52 uname -a ? If you do get some debugging, how come no debugging output is coming on my tests? By the way, although I don't know what the output will look like, I do expect some difference in the output if I use the "-d" switch... -d option set secket to debug mode by setsockopt(). It's all. It hasn't other effect to rsh. It means rsh doesn't output any extra messages for "-d", so it's wrong if you expect any difference in the output. The socket debug messages are out of rsh control. All control of this stuff has linux kernel. The output of kernel messages maintain klogd and syslogd and depend on your system setting what and where (on console or in the /var/log/messages) you will see. Ha, understood. Thanks for the clarification. |