jgt,
Thank you again for the help. I now understand how the program is being started thanks to you training script and the exec command.
I can see that the application is initiated through the user's .profile using the exec command
if I try a
I get
But I can see that in /etc/passwd
Every user has their own home directory, and the shell is common
Here is a .profile
I can see the "exec mz gmain" and when I run that command after I SSH into the box to the command prompt I get right to the application main menu.
I am not clear on the if then else statements but do know that I set the terminal emulator program to use term type as "ansi"
Does this help at all?
Thanks
Dear friends..
Our project has a module that runs on handheld devices. Through the handheld we telnet to solaris where the application actually runs. I noticed that after starting a session through the handheld, if i go out of range or if i remove and replace the battery in the handheld, the... (1 Reply)
{
sleep 2
echo "$user"
sleep 2
echo "$password"
sleep 2
echo " ls"
sleep 10
echo "exit"
}| telnet $server
I have a machine x and i have executed the above script on machine 'x'.
i entered the... (6 Replies)
We're having problems getting disconnected from AIX with our telnet sessions.
I can't ping the server when this happens, either. Other serves can be pinged at the same time.
This happens both at unix and within the database. Database locks remain when editing files. unix logins remain after... (0 Replies)
Hello,
I have AIX 5.3 at home connected to netgear router. Port Forwarding has been enabled on the router. Problem is that if I want to telnet, I have to try 2 or 3 times before I can get a logon prompt. It times out for first or second time (Connection to session <IP_Address> failed: Connection... (1 Reply)
I have intermec handheld device which is connecting to AIX Server on port 12431 or whatever. ( oracle application )
The handheld device connects for few seconds and then disconnects from the AIX server. Once it disconnects the handheld device automatically switches off.
Are there any... (2 Replies)
Our network administrators implemented some sort of check to kill idle sessions and now burden is on us to run some sort of keep alive. Client based keep alive doesn't do a very good job. I have same issue with ssh. Does solution 2 provided above apply for ssh sessions also? (1 Reply)
Hi,
Sorry if this question has been asked before, however, I have tried looking in the forum (and google in general) and I haven't found an answer, so I thought I'd ask here.
I am trying to use a GUI application in Solaris 10. Normally I connect with a VPN then SSH and use Xming to... (2 Replies)
Discussion started by: John_sp
2 Replies
LEARN ABOUT HPUX
tels
tels(7) Miscellaneous Information Manual tels(7)NAME
tels, telm - STREAMS Telnet slave (pseudo-terminal) driver, STREAMS Telnet master driver (used by telnetd only), respectively
SYNOPSIS DESCRIPTION
A Telnet pseudo-terminal consists of a tightly-coupled pair of character devices, called the master device and slave device. The master
and slave device drivers work together to provide a Telnet connection on the server side where the master provides a connection to and the
slave provides a terminal device special file access for the Telnet application processes, as depicted below:
--------------------------
| Pseudo terminal functions|
Application <--> |--------------------------| <--> telnetd
Processes | Slave | Master |
| (tels) | (telm) |
--------------------------
The slave driver, with (STREAMS pty emulation module) and (STREAMS line discipline module) pushed on top (not shown for simplicity), pro-
vides a terminal interface as described in termio(7). Whereas devices that provide the terminal interface described in termio(7) have a
hardware device behind them; in contrast, the slave device has manipulating it through the master side of the Telnet pseudo terminal.
There are no nodes in the file system for each individual master device. Rather, the master driver is set up as a STREAMS clone(7) driver
with its major device number set to the major for the clone driver and its minor device number set to the major for the driver. The master
driver is opened by telnetd using the open(2) system call with as the device file parameter. The clone open finds the next available minor
number for the master device. The master device is available only if it and its corresponding slave device are not already opened.
In order to use the STREAMS Telnet subsystem, a node for the master driver and N number of Telnet slave devices must be installed.
The number of slave devices is set by a kernel tunable parameter called This can be modified using SAM; its default and minimum value is
60. The value of is the upper limit of the number of telnet sessions that can be opened.
Multiple opens are allowed on the Telnet slave device.
The master and slave drivers pass all STREAMS messages to their adjacent drivers. When the connection is closed from the Telnet client
side, an message is sent to the corresponding slave device which will render that slave device unusable. The process on the slave side
gets the errno when attempting a write(2) system call to the slave device file but it will be able to read any data remaining in the slave
stream. Finally, when all the data has been read, the read(2) system call will return 0, indicating that the slave can no longer be used.
AUTHOR
and were developed by HP.
FILES
Streams Telnet master clone device
Streams slave devices where
N is the minor number of the slave device and 0 < N <
SEE ALSO insf(1M), open(2), ioctl(2), streamio(7), ldterm(7), telnetd(1M), ptem(7).
tels(7)