03-06-2008
ftp waits for longer time to reply
If i fire followin command on unix (linux/solaris) and windows
ftp serverX where serverX is not in the network,
it takes more time to get reply [connection timed out] on unix(3-4 mins) rather windows(1 min),
can anybody tell me why this happens? and how to reduce this time span?
8 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
This works if it's not in a function. I pulled it into one and I get syntax error, no mathcing '<'. I have to call it several times and need it to be a function. Any ideas?
function FTP_Engine_File {
ftp -inv ${FTP_SERVER} << EOF_FTP >> ${FTP_LOG}
user ${FTP_USER} ${FTP_PSWD}
... (4 Replies)
Discussion started by: brdholman
4 Replies
2. Shell Programming and Scripting
Hi all,
I have a script that checks for the existence of files in a directory. Problem is,
if a file suddenly appears, I need to move it to another directory and then
call another program that does not import routines (within our DBMS).
Now, this script is ever running and uses the sleep... (3 Replies)
Discussion started by: gseyforth
3 Replies
3. Shell Programming and Scripting
I thought a program's elapsed time, some program language call it real time, should be the time of a program from start to finish. And it should be equal or longer than CPU time. This is true for the most of the cases. However, I do see some of my programs CPU time is longer than Elapsed time. ... (1 Reply)
Discussion started by: visio2000
1 Replies
4. Shell Programming and Scripting
Hi
I have an ftp script which works fine when i execute through a test scheduler(UC4), but when i run it through the prod scheduler(UC4), it hungs indefinetely, when we cancel the job and re-run it it works perfectly fine. here is the code,, any idea why this is happening ????
... (1 Reply)
Discussion started by: selvankj
1 Replies
5. AIX
Guys,
I have a question - when nmon reports a sizeable %CPU wait, does that mean -
1) IO operations are slowing CPU down, OR
2) paging slowing the CPU down, OR
3) one cant tell??
I thought the nmon documentation clearly suggested that CPU waits reported in nmon were from disk... (4 Replies)
Discussion started by: getback0
4 Replies
6. UNIX for Dummies Questions & Answers
Hello,
I have an ftp loop script which I was going to use to login to various Linux systems but as It's my first connection I'm being prompted to add it to the known_hosts. Can this script be modified to reply 'yes' before passing the user/pass ?
usname="someuser"
pass="somepass"
while read... (1 Reply)
Discussion started by: Grueben
1 Replies
7. Shell Programming and Scripting
Hello,
I am in need of running an executable provided by a vendor that basically syncs files to a db. This tool can only be run against one folder at a time and it cannot have more than one instance running at a time. However, I need to run this tool against multiple folders. Each run of the... (5 Replies)
Discussion started by: vipertech
5 Replies
8. SuSE
Hi Guys
I am running an Oracle database and most of my sessions are waiting for tcp.
Now, how do I check if tcp from the O/S level is servicing requests properly?
Please Help!!!
Thanks in advance... (4 Replies)
Discussion started by: Phuti
4 Replies
WRITE(1) Linux Programmer's Manual WRITE(1)
NAME
write - send a message to another user
SYNOPSIS
write user [ttyname]
DESCRIPTION
Write allows you to communicate with other users, by copying lines from your terminal to theirs.
When you run the write command, the user you are writing to gets a message of the form:
Message from yourname@yourhost on yourtty at hh:mm ...
Any further lines you enter will be copied to the specified user's terminal. If the other user wants to reply, they must run write as
well.
When you are done, type an end-of-file or interrupt character. The other user will see the message EOF indicating that the conversation is
over.
You can prevent people (other than the super-user) from writing to you with the mesg(1) command. Some commands, for example nroff(1) and
pr(1), may disallow writing automatically, so that your output isn't overwritten.
If the user you want to write to is logged in on more than one terminal, you can specify which terminal to write to by specifying the ter-
minal name as the second operand to the write command. Alternatively, you can let write select one of the terminals - it will pick the one
with the shortest idle time. This is so that if the user is logged in at work and also dialed up from home, the message will go to the
right place.
The traditional protocol for writing to someone is that the string `-o', either at the end of a line or on a line by itself, means that
it's the other person's turn to talk. The string `oo' means that the person believes the conversation to be over.
SEE ALSO
mesg(1), talk(1), who(1)
HISTORY
A write command appeared in Version 6 AT&T UNIX.
AVAILABILITY
The write command is part of the util-linux-ng package and is available from ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/.
12 March 1995 WRITE(1)