Sponsored Content
Top Forums UNIX for Dummies Questions & Answers need help in fixing the hangup issue due to nohup command Post 302450635 by vbe on Friday 3rd of September 2010 10:06:08 AM
Old 09-03-2010
Without seeing the code it will be quite difficult.. (how is done the transfer of information from remote to host?)
 

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

ACL problem due to mv command used in solaris

Hi All, Is there any way to use mv command and that should apply ACL on the moved files that is already set in distination location This mv command is running in a solaris system. File system is NFS. Problem I am facing : Currently mv command removes ACL from moved files and also it... (0 Replies)
Discussion started by: Tlogine
0 Replies

2. UNIX for Advanced & Expert Users

rm & mv command failed due to too many files.

In our directory there are too many files, & if I try to execute mv *.gz or rm *.l command it fails, providing error string as - 'arg list too long'. This doesnt happen always, is there any way we know, limit on the rm & mv command so we can take care of this failure in future executions ? (9 Replies)
Discussion started by: videsh77
9 Replies

3. Red Hat

not able to Send mail due to Security Issue

Hi All, I am trying to send a mail from my application through SMTP in solaris 9 but unable to send a mail.Same code is able to send mail in Windows. As unix has more security,So as per me,it is due to security reason.. So please let me know what I need to do to send a mail properly. what... (5 Replies)
Discussion started by: smartgupta
5 Replies

4. Shell Programming and Scripting

Issue with nohup command

Hi everyone, I am starting a nohup from a script (via scheduling system) as follows: ssh user@server "nohup command & ; exit 0" This command is not returning the command prompt untless I press "ENTER". This is causing the schedule to hang at this job and not continue with the rest of the jobs.... (12 Replies)
Discussion started by: nimo
12 Replies

5. Shell Programming and Scripting

Date increment issue due to day light saving

The date increment worked fine until date reached 25/10, which is DLS change date. /bin/date --date="091025 1 day" +%y%m%d; the output is 091025 Is this a bug or something missing from the code ! (3 Replies)
Discussion started by: rajbravo
3 Replies

6. Windows & DOS: Issues & Discussions

Fixing Cygwin Command Line

How do I change my command line to the standard appearance? (i.e.: The pwd is listed in green above the actual command line). Mine looks like http://sites.google.com/site/flcl178/Cygwin_Window_1.png and I want it to look like this http://sites.google.com/site/flcl178/cygwinLinkSetup.gif ... (2 Replies)
Discussion started by: LanguidLegend
2 Replies

7. Red Hat

Help needed in fixing port issue - Urgent

Hi, One of our web application is running in Linux and using apache web servers. Application is hosted in port 4080 (for soap requests) and port 9999, and its serving behind a vip and cname. Initially it was working fine in another server and recently (2 months back) we have moved to the new... (4 Replies)
Discussion started by: senor.ram
4 Replies

8. Linux

Linking issue due to so version number

Hi all, currently I'm facing a issue in linking a .so file. In my build machine, I've libcrypto.so.6 and there is a softlink as libcrypto.so. In my make file I'm trying to link to the lib using -L -lcrypto and it is success and created my test.exe. When I copy this test.exe to other... (4 Replies)
Discussion started by: vijkrr
4 Replies

9. SCO

Unsuccessful install due to unrecognized disk issue

Dear Community! i try to instaled the sco 6 in hp proliant ML350g8 but unsucces, the trouble when i do instaled it undetected hardisk please help me :(:o (7 Replies)
Discussion started by: mnr
7 Replies

10. UNIX for Beginners Questions & Answers

DHCP Issue Possibly due to Hardware Clock?

Hello All, OS: openSUSE 13.1 (Bottle) (armv7hl) PC: CuBox-i (*mini-pc) The PC in question is a CuBox-i mini-pc. Since this PC doesn't have a battery, everytime the PC reboots the hardware clock is reset back to the same date every time, which is "2014-07-08 00:00". I have NTP configured... (5 Replies)
Discussion started by: mrm5102
5 Replies
TFTP(1) 						    BSD General Commands Manual 						   TFTP(1)

NAME
tftp -- trivial file transfer program SYNOPSIS
tftp [-e] [host] [port] DESCRIPTION
The tftp utility is the user interface to the Internet TFTP (Trivial File Transfer Protocol), which allows users to transfer files to and from a remote machine. The remote host (and optional port) may be specified on the command line, in which case tftp uses host (and port) as the default for future transfers (see the connect command below). The optional -e argument sets a binary transfer mode as well as setting the extended options as if tout, tsize, and blksize 65464, had been given. COMMANDS
Once tftp is running, it issues the prompt 'tftp>' and recognizes the following commands: ? command-name ... Print help information. ascii Shorthand for mode ascii. binary Shorthand for mode binary. blksize blk-size Set the tftp blksize option to blk-size octets (8-bit bytes). Since the number of blocks in a tftp get or put is 65535, the default block size of 512 bytes only allows a maximum of just under 32 megabytes to be transferred. The value given for blk-size must be between 8 and 65464, inclusive. Note that many servers will not respect this option. connect host-name [port] Set the host (and optionally port) for transfers. Note that the TFTP protocol, unlike the FTP protocol, does not maintain connec- tions between transfers; thus, the connect command does not actually create a connection, but merely remembers what host is to be used for transfers. You do not have to use the connect command; the remote host can be specified as part of the get or put com- mands. get filename get remotename localname get file1 file2 ... fileN Get one or more files from the remote host. When using the host argument, the host will be used as default host for future trans- fers. If localname is specified, the file is stored locally as localname, otherwise the original filename is used. Note that it is not possible to download two files at a time, only one, three, or more than three files, at a time. To specify an IPv6 numeric address for a host, wrap it using square brackets like ``[3ffe:2900:e00c:ffee::1234]:file'' to disam- biguate the colons used in the IPv6 address from the colon separating the host and the filename. mode transfer-mode Set the mode for transfers; transfer-mode may be one of ascii or binary. The default is ascii. put file put localfile remotefile put file1 file2 ... fileN remote-directory Put a file or set of files to the specified remote file or directory. The destination can be in one of two forms: a filename on the remote host, if the host has already been specified, or a string of the form hosts:filename to specify both a host and filename at the same time. If the latter form is used, the hostname specified becomes the default for future transfers. When remotename is specified, the file is stored remotely as remotename, otherwise the original filename is used. If the remote-directory argument is used, the remote host is assumed to be a UNIX machine. To specify an IPv6 numeric address for a host, see the example under the get command. quit Exit tftp. An end of file also exits. rexmt retransmission-timeout Set the per-packet retransmission timeout, in seconds. status Show current status. timeout total-transmission-timeout Set the total transmission timeout, in seconds. tout Toggle the tftp "timeout" option. If enabled, the client will pass its retransmission-timeout to the server. Note that many servers will not respect this option. trace Toggle packet tracing. tsize Toggle the tftp "tsize" option. If enabled, the client will pass and request the filesize of a file at the beginning of a file transfer. Note that many servers will not respect this option. verbose Toggle verbose mode. HISTORY
The tftp command appeared in 4.3BSD. IPv6 support was implemented by WIDE/KAME project in 1999. TFTP options were implemented by Wasabi Systems, Inc., in 2003, and first appeared in NetBSD 2.0. SECURITY CONSIDERATIONS
Because there is no user-login or validation within the TFTP protocol, the remote site will probably have some sort of file-access restric- tions in place. The exact methods are specific to each site and therefore difficult to document here. Files larger than 33488896 octets (65535 blocks) cannot be transferred without client and server supporting blocksize negotiation (RFC1783). BSD
June 11, 2003 BSD
All times are GMT -4. The time now is 09:25 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy