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 OSF1
iptos
iptos(4) Kernel Interfaces Manual iptos(4)NAME
iptos - Defines the IP Type Of Service (TOS) for FTP and Telnet
SYNOPSIS
/etc/iptos
DESCRIPTION
The /etc/iptos file configures the Type Of Service (TOS) of the Internet Protocol (IP) used by FTP and Telnet.
The TOS field in the Internet datagram is to specify how the datagram should be handled. It is a mechanism to allow control information to
have precedence over data.
Generally, protocols that are involved in direct interaction with a human should select low delay, while data transfers that involve large
blocks of data need high throughput. Finally, high reliability is most important for datagram-based Internet management functions.
In the Tru64 UNIX operating system, the ftp and telnet applications and the ftpd and telnetd daemons allow the configuring of TOS values.
These applications check to see if the /etc/iptos file exists; if the file exists, the applications obtain the TOS value from the file and
use that value to set the TOS field. If the /etc/iptos file does not exist, the applications default to the following TOS values recom-
mended by RFC1060: Low delay High throughput Low delay
Users who want to configure their own TOS values for the TOS field should provide the /etc/iptos file.
Note
Most IP routers do not differentiate based on TOS, and therefore providing values other than the default would have no affect. You
should not change the default values for FTP and Telnet.
Each entry should consist of a single line of the form:
Application Proto TOS-bits aliases
The entry fields contain the following information: The name of an application TOS entry. The protocol name for which the entry is appro-
priate. The TOS value to be set for the entry. A list of aliases that exist for the entry.
Items on an entry line are separated by any number of blanks, tabs, or combination of blanks and tabs. A number sign (#) indicates that
the rest of the line is a comment and is not interpreted by routines that search the file. Blank lines in the file are ignored.
Valid TOS entry names are ftp-control and ftp-data for FTP and telnet for Telnet.
The TOS value for the entry should be one of the following hexadecimal numbers, corresponding to TOS bits: Low delay High throughput High
reliability
If you need to disable the use of TOS bits, because you are having troubling communicating with a TCP/IP host that doe not conform entirely
with the IP specification, you can disable the TOS bits by using the the following settings in the /etc/iptos file:
# # Format of this file: # Application Proto TOS-bits aliases #
ftp-control tcp 0x0 ftp-data tcp 0x0 telnet tcp 0x0
EXAMPLES
The following example shows typical entries in the /etc/iptos file:
# # Format of this file: # Application Proto TOS-bits aliases #
ftp-control tcp 0x10 ftp-data tcp 0x08 telnet tcp 0x10
RELATED INFORMATION
RFC1060, ftp(1), telnet(1), ftpd(8), telnetd(8) delim off
iptos(4)