10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello All,
I have a text file containing output from a command that contains lots of escape/control characters that when viewed using vi or view, looks like jibberish. But when viewed using the cat command the output is formatted properly.
Is there any way to take the output from the cat... (7 Replies)
Discussion started by: mrm5102
7 Replies
2. Shell Programming and Scripting
I have been having an extremely annoying problem. For the record, I am relatively new at this. I've only been working with unix-based OS's for roughly two years, mostly Xubuntu and some Kali. I am pretty familiar with the BASH language, as that's the default shell for debian. Now, I've made this... (16 Replies)
Discussion started by: Huitzilopochtli
16 Replies
3. UNIX for Dummies Questions & Answers
Hi all...
Consider me a dummy here...
I do not want any code or for anyone to show me how to do it at this time, but here is the question:-
I have had this brainstorm to be able to control the AudioScope.sh program in the "Shell Scripting And Programming" forum...
Is it possible, by... (4 Replies)
Discussion started by: wisecracker
4 Replies
4. UNIX for Dummies Questions & Answers
I am wondering if the DOS console works like the unix terminal? (1 Reply)
Discussion started by: vistastar
1 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I installed ubuntu recently on my pc. And I installed gnuplot as well.
When I first started working with gnuplot it was working . I did a plot and when I wanted to fit my data something happened and not the default terminal of gnuplot is xwt!
I changed it to: set terminal x11, but it... (0 Replies)
Discussion started by: cosmologist
0 Replies
6. UNIX for Advanced & Expert Users
I am trying to automate a SSH login using Keys using the following command
ssh -i id_rsa usernamw@ipaddr.
I am successful in doing this and i am getting the Warning Screen and I logon successfully.
but when I am executing the command
tail -1cf put.dat | ssh -i id_rsa username@ipaddr > get.dat ... (1 Reply)
Discussion started by: Shivdatta
1 Replies
7. UNIX for Dummies Questions & Answers
Hello,
I'm completely new to UNIX, and as part of a project I'm doing at university I am using a UNIX SOLAR computer. I have been told to SSH tunnel to access it, using Putty and VNC, which I have done and works.
When I could then 'see' the computer from home I had a terminal open, but I was... (10 Replies)
Discussion started by: Jono_H
10 Replies
8. AIX
People, what util can help me as a terminal for COM connection with a Zyxel modem so that I can connect to another server (p630) with the same modem through a dedicated line???
And also does anybody know where can I put a question about Storage Area Networking?? I am having problems with setting... (5 Replies)
Discussion started by: dilshik
5 Replies
9. UNIX for Dummies Questions & Answers
Hi there,
Does anyone know what exactly is the different between a terminal and a console ?
My understanding is a console is normally a local session while a terminal can be a remote as well.
What do you think guys?
Thanks (1 Reply)
Discussion started by: guest100
1 Replies
10. UNIX for Advanced & Expert Users
I just changed from windows NT to XP and I am no longer able
to connect to my unix system. I used to use hyper terminal -- which acts as dumb terminal to my main frame unix system. I think one of the options used to be "direct to comX". This option isn't listed now. I use a serial port and the... (2 Replies)
Discussion started by: michelle
2 Replies
RLOGIND(8) System Manager's Manual RLOGIND(8)
NAME
rlogind, in.rld - remote login server
SYNOPSIS
login stream tcp nowait root /usr/sbin/in.rld in.rld
tcpd login /usr/sbin/in.rld
DESCRIPTION
Rlogind is the server for the rlogin(1) program. The server provides a remote login facility with authentication based on privileged port
numbers from trusted hosts.
Rlogind listens for service requests at the port indicated in the ``login'' service specification; see services(5). When a service request
is received the following protocol is initiated:
1) The server checks the client's source port. If the port is not in the range 0-1023, the server aborts the connection.
2) The server checks the client's source address and requests the corresponding host name (see gethostbyaddr(3), hosts(5) and
named(8)). If the hostname cannot be determined, the dot-notation representation of the host address is used.
Once the source port and address have been checked, rlogind allocates a pseudo terminal (see tty(4)), and manipulates file descriptors so
that the slave half of the pseudo terminal becomes the stdin , stdout , and stderr for a login process. The login process is an instance
of the login(1) program, invoked with the -r option. The login process then proceeds with the authentication process as described in
rshd(8), but if automatic authentication fails, it reprompts the user to login as one finds on a standard terminal line.
The parent of the login process manipulates the master side of the pseduo terminal, operating as an intermediary between the login process
and the client instance of the rlogin program. In normal operation, the packet protocol described in tty(4) is invoked to provide ^S/^Q
type facilities and propagate interrupt signals to the remote programs. The login process propagates the client terminal's baud rate and
terminal type, as found in the environment variable, ``TERM''; see environ(7). The screen or window size of the terminal is requested from
the client, and window size changes from the client are propagated to the pseudo terminal.
SEE ALSO
rlogin(1).
DIAGNOSTICS
All diagnostic messages are returned on the connection associated with the stderr, after which any network connections are closed. An
error is indicated by a leading byte with a value of 1.
``Try again.''
A fork by the server failed.
``/bin/sh: ...''
The user's login shell could not be started.
BUGS
The authentication procedure used here assumes the integrity of each client machine and the connecting medium. This is insecure, but is
useful in an ``open'' environment.
A facility to allow all data exchanges to be encrypted should be present.
A more extensible protocol should be used.
4.2 Berkeley Distribution May 24, 1986 RLOGIND(8)
