|
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| Shell Programming and Scripting Post questions about KSH, CSH, SH, BASH, PERL, PHP, SED, AWK and OTHER shell scripts and shell scripting languages here. |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Strange KSH behaviour - any comments? | gsw_aix | UNIX for Advanced & Expert Users | 7 | 06-24-2008 07:08 PM |
| Longer commands and strange behaviour on ksh | anurags | UNIX for Dummies Questions & Answers | 2 | 03-27-2008 11:04 AM |
| Strange sed behaviour | vino | UNIX for Advanced & Expert Users | 8 | 02-12-2008 06:51 AM |
| A Strange Behaviour!!! | navojit dutta | Shell Programming and Scripting | 5 | 12-21-2007 04:35 AM |
| /etc/passwd strange behaviour! | penguin-friend | Linux | 0 | 06-06-2005 01:00 PM |
Powered by 
|
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
06-26-2008
|
||||
|
||||
|
Strange behaviour from script in crontab
Apologies if this has been mentioned elsewhere, my search skills may be lacking somewhat today.
I have a script that does the following (as a test): Code:
find . -name "*.txt" -exec file {} \; >>$sFullFilePath
However, when this is run using crontab on the identical directory (debug code proves this), it just creates an empty file. When I look at the stack, it doesn't mention the output. Is crontab treating it as 2 seperate lines? The script starts with #!/bin/bash, so why should it act differently? <is confused> |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
Threaded Mode
