On Sat, Apr 19, 2008 at 4:30 PM, Dave Burns <[EMAIL PROTECTED]> wrote:
> I considered that, and edited the file using vim, and retyped that
> line. Is that enough to eliminate that possibility?
Nope, vim will happily preserve the line-ending convention of the
file. Look for an indicator in the
On Fri, Apr 18, 2008 at 6:42 PM, Brian Dessent <[EMAIL PROTECTED]> wrote:
> Dave Burns wrote:
>
> > #!/bin/bash
> > #invoke audit.sh if results are too old
> > /usr/bin/find /cygdrive/c/audit.txt -mtime +7 -exec
> > /cygdrive/c/audit/audit.sh \;
>
> Is the file really wrapped like that or is
On 2008-04-18, Dave Burns wrote:
> I have a bash script that works on one PC, does not work on another. I
> had thought they were configured the same, apparently not!
>
> Here's the script, short and sour:
>
> #!/bin/bash
> #invoke audit.sh if results are too old
> /usr/bin/find /cygdrive/c/audit
Dave Burns wrote:
> #!/bin/bash
> #invoke audit.sh if results are too old
> /usr/bin/find /cygdrive/c/audit.txt -mtime +7 -exec
> /cygdrive/c/audit/audit.sh \;
Is the file really wrapped like that or is it all one line?
> Maybe different versions of find?
Um, that's kind of the sort of thing y
I have a bash script that works on one PC, does not work on another. I
had thought they were configured the same, apparently not!
Here's the script, short and sour:
#!/bin/bash
#invoke audit.sh if results are too old
/usr/bin/find /cygdrive/c/audit.txt -mtime +7 -exec
/cygdrive/c/audit/audit.sh
5 matches
Mail list logo