Sponsored Content
Full Discussion: Automatic ftp job
Top Forums Shell Programming and Scripting Automatic ftp job Post 68816 by Steve_H on Thursday 7th of April 2005 09:32:54 AM
Old 04-07-2005
duh

1234567890

Last edited by Steve_H; 04-07-2005 at 10:36 AM.. Reason: duh, should have realised this thread was 3 years old
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Automatic FTP

Hi, We have a requirement to transfer(FTP) files created in a particular directory (In Solaris) to NT machine. Also this process neeeds to be automated. I belive a command MAIL in UNIX could be used to find new files created in a directory, but this just sends the file list to the logged user.... (5 Replies)
Discussion started by: shyamrk
5 Replies

2. SCO

SCO 5.06 :automatic shutdown on the job?

Hi Guys I have got a problem and I would really be grateful if some1 could sort out the problem. The problem is that there are a few computers based on SCO 5.0.6 automatic shutdown on the job.and I am anxious to konw the reasons. Looking forward to seeing some messiah helping me out.... (1 Reply)
Discussion started by: rendechen
1 Replies

3. Shell Programming and Scripting

Is it possible..when ftp session disconnect and it can automatic run again?

Hi, Is is possible when ftp script disconnect by remote server and it can restart to tranfer (such as restart in 10 mins, etc)? Please help!!!! (1 Reply)
Discussion started by: happyv
1 Replies

4. Shell Programming and Scripting

Automatic FTP Script from windows to unix machine

Hi i need to FTP files from windows to unix(sun) machine using script. what are the scripts commands i need to use to transfer files Thanks (2 Replies)
Discussion started by: bmkreddy
2 Replies

5. UNIX for Advanced & Expert Users

Cron FTP job

We have a script that we run manually, we want to set it up so that it will run automatically via cron, the problem is during the ftp process nothing is put, the script logs in changes directory fine, but nothing is put to the directory. I have tried it as root, a power user, etc. I have made the... (4 Replies)
Discussion started by: marvin51796
4 Replies

6. SCO

Automatic FTP script

We are using SCO OS 5.05 server and we are doing a manual ftp to another SCO OS 5.05 server to backup our database. We are using the Bourne shell. We would like to automate the ftp backup of our database instead of doing it manually. It would be nice to run a script. Also would there be anyway... (4 Replies)
Discussion started by: texastig
4 Replies

7. AIX

.netrc and Automatic ftp problem

Guy's We have two AIX servers Server1 and Server2 and we have created user1 in Server1 and Server2 ... and .netrc file was confiured under /home/user1 with the below line machine server2 login user1 password abc1234567 -rw------- 1 user1 staff 159 Sep 28 2004 .netrc ... (7 Replies)
Discussion started by: ITHelper
7 Replies

8. Shell Programming and Scripting

Automatic FTP

Hi I am looking for automatic FTP script from UNIX to UNIX servers. I have two problems that anyone may help: 1- The directory where the files have to be FTPed is varied, where it is identified by the date of today (YYYYMMDD) 2- the files come every 15 minutes and named by the time with form... (2 Replies)
Discussion started by: akhadoor
2 Replies

9. Shell Programming and Scripting

Automatic FTP-Download | not files older then x days

Hey Guys, i need to download files from a ftp-server that not older than $VAR (x) days eg for seven days ./script 7 or two weeks ./script 14 all files from the last 14 days will download but how i can explain "ftp" this? sorry for my strange english :/ (2 Replies)
Discussion started by: tetex
2 Replies

10. Shell Programming and Scripting

automatic FTP failed

I have automated ftp for different scripts. every script uses different login and passwords for different server. it reads the username and password from netrc. there is 1 particular script that is failing. this script is failing in FTP step. i have checked the logs it says login failed. but... (5 Replies)
Discussion started by: dazdseg
5 Replies
SG_IDENT(8)							     SG3_UTILS							       SG_IDENT(8)

NAME
sg_ident - sends a SCSI REPORT or SET IDENTIFYING INFORMATION command SYNOPSIS
sg_ident [--ascii] [--clear] [--help] [--itype=IT] [--raw] [--set] [--verbose] [--version] DEVICE DESCRIPTION
Send a SCSI REPORT IDENTIFYING INFORMATION or SET IDENTIFYING INFORMATION command to DEVICE. Prior to SPC-4 (revision 7) these commands were called REPORT DEVICE IDENTIFIER and SET DEVICE IDENTIFIER respectively. SCSI devices that support these two commands allow users to write (set) identifying information and report it back at some later time. The information is persistent (i.e. stored on some non-volatile medium within the SCSI device that will survive a power outage). Typically the space allocated for the information is limited: SPC-4 (revision 7) states that for information type 0, the minimum length is 64 bytes and the maximum is 512 bytes. For other information types (1 to 126 inclusive) the maximum length is 256 bytes. Also information types 1 to 126 (inclusive) should contain a null terminated UTF-8 string. The author has seen older disks that only support 16 bytes. The default action when no options are given is to invoke the Report Identifying Information command with the information type defaulting to zero. Error reports are sent to stderr. By default the information is shown in ASCII-HEX (up to 16 bytes per line) with an ASCII repre- sentation to the right with dots replacing non printable characters. OPTIONS
Arguments to long options are mandatory for short options as well. -A, --ascii invokes the Report Identifying Information command and if anything is found interprets it as ASCII (or UTF-8 depending on the locale) and prints the information to stdout. -C, --clear invokes the Set Identifying Information command with an information length of zero. This has the effect of clearing the existing information. -h, --help output the usage message then exit. -i, --itype=IT where IT is the information type. Defaults to zero. The maximum value is 127 which is special and cannot be used with --set or --clear. The information type of 127 (if supported) causes the REPORT IDENTIFYING INFORMATION command to respond with a list of available information types and their maximum lengths in bytes. The odd numbered information types between 3 and 125 (inclusive) are not to be used (as they clash with the SCC-2 standard). -r, --raw invokes the Report Identifying information command and if anything is found sends the information (which may be binary) to stdout. Nothing else is sent to stdout however error reports, if any, are sent to stderr. -S, --set first reads stdin until an EOF is detected then invokes the Set Identifying Information command to set what has been fetched from stdin as the information. The amount of data read must be between 1 and 512 bytes length (inclusive). -v, --verbose increase the level of verbosity, (i.e. debug output). -V, --version print the version string and then exit. This utility permits users to write their own identifying information to their SCSI devices. There are several other types of descriptors (or designators) that the user cannot change. These include the SCSI INQUIRY command with its standard vendor and product identification strings and the product revision level; plus the large amount of information provided by the "Device Identification" VPD page (see sg_vpd). There is also the READ MEDIA SERIAL NUMBER command (see sg_rmsn). The MMC-4 command set for CD and DVDs has a "media serial number" feature (0x109) [and a "logical unit serial number" feature]. These can be viewed with the sg_get_config utility. EXAMPLES
First, to see if there is an existing information whose format is unknown (for information type 0), use no options: # sg_ident /dev/sdb 00 31 32 33 34 35 36 37 38 39 30 1234567890 If it is ASCII then it can printed as such: # sg_ident --ascii /dev/sdb 1234567890 The information can be copied to a file, cleared and then re-asserted with this sequence: # sg_ident --raw /dev/sdb > t # sg_ident --clear /dev/sdb # cat t | sg_ident --set /dev/sdb EXIT STATUS
The exit status of sg_ident is 0 when it is successful. Otherwise see the sg3_utils(8) man page. AUTHORS
Written by Douglas Gilbert. REPORTING BUGS
Report bugs to <dgilbert at interlog dot com>. COPYRIGHT
Copyright (C) 2005-2009 Douglas Gilbert This software is distributed under a FreeBSD license. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PUR- POSE. SEE ALSO
sg_vpd(sg3_utils), sg_rmsn(sg3_utils), sg_get_config(sg3_utils) sg3_utils-1.28 July 2009 SG_IDENT(8)
All times are GMT -4. The time now is 11:59 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy