Sponsored Content
Full Discussion: FTP Cron issues
Top Forums Shell Programming and Scripting FTP Cron issues Post 302075391 by bryanthomas on Friday 2nd of June 2006 10:13:43 AM
Old 06-02-2006
Yes $HOME is defined, The error is with ftp wanting me to input username and Password. I turned writing stdout and stderr to dev/null off so I could see the error.

I do not get this error when I execute the script at command line
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

cron ftp job help

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

2. Shell Programming and Scripting

FTP Cron Issue

I have an automated FTP script that is giving me grief. The script runs a ftp sweep for one of our accounts. It gets about 90 files then hangs. When i run ftp manually from cli everything runs great and I pickup the thousands of files waiting. I used to run lftp, but it has been behaving even... (7 Replies)
Discussion started by: edua
7 Replies

3. 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

4. UNIX for Advanced & Expert Users

FTP issues between mainframe and UNIX

Hi All, The issue is that, we have a dataset in mianframe whose record length is 153 characters. And a batch job ftpies it to the unix server(SunOS) as a test file. But the ftpied file in unix does not have a record length of 153 chars. Each record of 153 chars gets splited into two line of... (8 Replies)
Discussion started by: hareeshkumaru
8 Replies

5. UNIX for Dummies Questions & Answers

Permissions Issues FTP server

Hi all, Quick question, im going to find this a bit hard to explain but ill give it a go. Basically i have an admin account on an FTP server that i want to be able to control ALL files without having to use sudo (as i need to run cron scripts to move files that are owned by a number of... (2 Replies)
Discussion started by: mokachoka
2 Replies

6. Solaris

cron / crontab issues - solaris 10

I am having some issues with my cronjobs not running in solaris 10. Cron is running: ~> ps -ef | grep cron root 202 1 0 Jul 18 ? 0:01 /usr/sbin/cron bender 1646 1562 0 01:57:49 syscon 0:00 grep cron crontab -l lists the cronjob and I *think* its in the... (8 Replies)
Discussion started by: ippy98
8 Replies

7. UNIX for Advanced & Expert Users

Cron security issues?

Does the use of cron (HP-UX 11) present a security risk IF it is only given to accounts which have shell access anyway. If it does present a risk, what is the risk? Can a script (or command) run via cron; run anything, write anywhere or read anywhere that the same user can not do outside of... (2 Replies)
Discussion started by: eileenkeeney
2 Replies

8. Shell Programming and Scripting

Bash/cron issues

Hi all, I am trying to run a cronjob to push my files to my git repo once a week and output a prompt to a logfile, my script works fine if I invoke it manually but my cronjob wont run for some reason, I have sourced the file, and restarted my Mac to no avail, right now I believe I have the cronjob... (8 Replies)
Discussion started by: gmenfan83
8 Replies

9. UNIX for Dummies Questions & Answers

Db2 command issues with cron

Hi, I have a very simple script that queries from a DB2 table. The script has 3 parts - (i) Sets the db2profile (ii) connects to db2 using credentials (iii) executes the query.This script works fine if i run it manually from the command prompt. However when scheduled in crontab, it proceeds... (2 Replies)
Discussion started by: VeePee
2 Replies
GRC(1)							      General Commands Manual							    GRC(1)

NAME
grc - frontend for generic colouriser grcat(1) SYNOPSIS
grc [options] command [args] DESCRIPTION
grc will execute command command with optional parameters [args] piping its stdout or stderr into grcat, with apropriate configuration file. Configuration file for grc is determined by /etc/grc.conf file. Format of /etc/grc.conf: each entry consists of 2 lines, between entries there can be any number of empty lines or lines beginning with # (comments) First line is regular expression, second line the name of configuration file for grcat. Configuration file after the first regular expression matching command [args] will be passed to grcat as its configuration file OPTIONS
--help Show summary of options. --version Display version. -e --stderr Redirect error output. Unless -s is selected as well, this cancels redirection of standard output via grcat -s --stdout Redirect standard output. Used to redirect standard output together with --stderr option. --colour=x x is one of on off auto --colour=on will colourise (default) --colour=off will just execute command without colourising. --colour=auto will test if standard output is a tty, and colourise only when it is. SEE ALSO
grcat(1) AUTHOR
Written by Radovan Garabik <garabik @ kassiopeia.juls.savba.sk> GRC(1)
All times are GMT -4. The time now is 05:55 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy