1753884 Members
7330 Online
108809 Solutions
New Discussion юеВ

I can not ll by rlogin

 
Jack Fan
Regular Advisor

I can not ll by rlogin

all,
I can not ll by rlogin. Can you teach me how to solve it?
1. I logon to server A then telnet to server B, ls and ll is okay.
2. I logon to server A then rlogin to server B, ls is okay but ll be hanged.

server A(K580) : HP-UX 11.0 64bit
server B(J2240) : HP-UX 11.11 64bit

regards,
Jack Fan
13 REPLIES 13
harry d brown jr
Honored Contributor

Re: I can not ll by rlogin


do it again and compare your "env", "aliases", and login "profiles" and you will find them different.

live free or die
harry
Live Free or Die
Printaporn_1
Esteemed Contributor

Re: I can not ll by rlogin

Hi Jack,

Can you do ls ? if yes -> check your alias.
enjoy any little thing in my life
Jack Fan
Regular Advisor

Re: I can not ll by rlogin

sir,

ls is okay. But ll be hanged.
and I got information by alias....

autoload='typeset -fu'
command='command '
functions='typeset -f'
history='fc -l'
integer='typeset -i'
local=typeset
nohup='nohup '
r='fc -e -'
stop='kill -STOP'
suspend='kill -STOP $$'
type='whence -v'

How to verify these information is correct?
Jack Fan
Regular Advisor

Re: I can not ll by rlogin

BTW, ls is okay. But ls -lrt same as ll be hanged. Please kindly help me...

Regards,
Jack Fan
Niraj Kumar Verma
Trusted Contributor

Re: I can not ll by rlogin

Hi,

Check th permission of ll
-r-xr-xr-x 7 bin bin 32768 Sep 29 1999 /usr/bin/ll

Try the following

# command /usr/bin/ll

-Niraj
Niraj.Verma@philips.com
Keith Clark
Valued Contributor

Re: I can not ll by rlogin

It could possibly be a NIS problem. Does you server use NIS? ls does not need any file attributes, yet ls -l needs to show user and group info. If the NIS server is not responding ls -l could hang.
Steven Sim Kok Leong
Honored Contributor

Re: I can not ll by rlogin

Hi Jack,

This is indeed most interesting!!!

Why should ls -lrt work in a telnet session but not in a rlogin session while ls works in both telnet and rlogin sessions?

The more far-fetched reason I can think of is that either your rlogin binary or your login shell on the remote server has been hijacked (i.e. rootkit'ed) to "hang" upon recognising ll from a rlogin session. However, this doesn't make much sense as to why on earth would someone do that i.e. why not "rootkit" all sessions including telnet sessions as well instead of just rlogin sessions?

Please post up the cause when you do find out the reason. Thanks in advance. Regards.

Steven Sim Kok Leong
Steven Sim Kok Leong
Honored Contributor

Re: I can not ll by rlogin

Back to top.
Hartmut Lang
Trusted Contributor

Re: I can not ll by rlogin

Do you login to a nfs-mounted home-directory?

We had various problems with these (login did not show prompt, ll hang, ...) until we patched NFS on server and client side.
Problems were related to NFS file-locking mechanism.

Hartmut