10-16-2009
If FTP cron job fails to connect = quit
Im having a problem with my ftp CRON jobs. I have another related (but not the same question in shell scripting).
My FTP CRON jobs connect to a server and drop some files off, if for some reason it cannot connect to the server (timesout/password wrong etc) instead of stopping, it tries again 1min later... overnight this caused me alot of problems are the server maxed out its 512mb ram... can i change it so IF the connection fails it doesnt attempt it again 1min later... instead it just fails and quits...
please help
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am writing a script that will be placed in a crontab, which basically retrieves a file that is overwritten everyday (with current customer data) and then sent to another company. I was wondering what the best way to ensure that ftp was successful and notification of a success or failure message.... (3 Replies)
Discussion started by: walterja
3 Replies
2. UNIX for Dummies Questions & Answers
I am new to cron and am trying to set a cron job that will run everyday at 2 to go out to a server (via ftp with user name and password) and get a file and then bring it back to my sever. Below is what I have but it doesn't seem to be working. Any help would be appreciated.
cron command - will... (4 Replies)
Discussion started by: bernfuss
4 Replies
3. UNIX for Advanced & Expert Users
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
4. Shell Programming and Scripting
I have a very basic script that essentially sends a log file, via FTP, to a backup server. My cron entry to run this every night is:
55 23 * * * /usr/bin/archive_logs
The script runs perfectly when executed manually, and actually worked via cron for about three weeks. However, it mysteriously... (3 Replies)
Discussion started by: cdunavent
3 Replies
5. Shell Programming and Scripting
Hello,
Im fairly new to this and am hoping for your help in moving forward.
1. I need to carry out a FTP transfer from SERVER1 to SERVER2 at 3am every morning.
2. The FTP is to work on SERVER1
3. There will be many files to transfer (96 files per day)
4. I want to delete the files... (3 Replies)
Discussion started by: nozerf
3 Replies
6. UNIX for Advanced & Expert Users
I added a shell script to cron that executes every 5-15 minutes. It's used to monitor multiple environments, so it has to ssh to each machine to check the status of that machine. Sometimes, I may have more than one instance of this script running at the same time. So, here's my problem. I've... (2 Replies)
Discussion started by: mrwatkin
2 Replies
7. Shell Programming and Scripting
Hey,
same problem. i want to check if files have been successfuly transferred after getting them back, but after I quit the ftp, nothing gets executed.
Difference from original post is that I get 226 and 221 feedbacks from the server.
226 Transfer complete.
2409 bytes received in 0.0086... (5 Replies)
Discussion started by: fpflug
5 Replies
8. UNIX for Advanced & Expert Users
i have a text file in this format: which creates a new one everyday in the form of filename _zing__r200_2012_8_10_log.txt
Fri Aug 10 07:29:17 EDT 2012, usera(192.168.0.245) to anotheruser: hey top, this is a private test
Fri Aug 10 07:29:28 EDT 2012, anotheruser(192.168.0.245) to usera: got... (2 Replies)
Discussion started by: bkkid
2 Replies
9. Shell Programming and Scripting
Hi,
When run the script directly...it executes as expected. But when put it in crontab the job fails with this error:
Connection not open
08003: Connection not open
Unable to connect to the database...
how come it is not able to connect when cron job fires?... Do I need to... (7 Replies)
Discussion started by: nuthakki
7 Replies
LEARN ABOUT REDHAT
pserver
PSERVER(1) pserver PSERVER(1)
NAME
pserver - NetWare print server
SYNOPSIS
pserver [ -S server ] [ -h ] [ -U user name ] [ -P password | -n ] [ -C ] [ -q queue name ] [ -c command ] [ -j job type ] [ -t timeout ] [
-d ]
DESCRIPTION
pserver is a program that connects to print queues on NetWare servers and feeds incoming print jobs to the Linux printing system.
OPTIONS
-h
-h is used to print out a short help text.
-S server
server is the name of the server you want to use.
-U user
user is the print server name at the server.
-P password
password is the password to use for the print server at the server. If neither -n nor -P are given, and the user has no open connection
to the server, pserver prompts for a password.
-n
-n should be given if the print server does not require a password.
-C
By default, passwords are converted to uppercase before they are sent to the server, because most servers require this. You can turn off
this conversion by -C.
-q queue name
queue name is the name of the print queue you want to service.
-c command
When a job is received from the print queue, pserver forks off a new process, and feeds the job file to stdin. command is the printing
command that is executed for each job. The default command is 'lpr'.
You can insert several flags into the command, preceded by %. These are replaced with values retrieved from the queue structure for the
print job.
%u: This field will be replaced by the name of the user who posted this print job.
%d: This field will be replaced by the job description field of this print job.
-j job type
Each job in a NetWare print queue has a job type. For print jobs, this corresponds to the number of the form the job should be printed
on. You can tell pserver that it should only receive jobs for one specific form from the queue. The default is -1, which means that
everything is received.
-t timeout
Pserver is not informed by NetWare servers when new jobs arrive. So a polling scheme has to be used. When there are no jobs to service,
timeout tells pserver how long to wait between two requests. The default is 30 seconds. When a job is finished, pserver asks the NetWare
server immediately for a new job, and does not wait timeout seconds.
-d
Normally, pserver daemonizes itself. -d tells it not to do so. This is useful if you want to see the diagnostic messages that are
printed when a error occurs.
SEE ALSO
nwclient(5), slist(1), pqlist(1), ncpmount(8), ncpumount(8)
CREDITS
pserver was written by Volker Lendecke (lendecke@math.uni-goettingen.de)
pserver 10/22/1996 PSERVER(1)