[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: wget in cron issue with dns resolution of local server
From: |
Álvaro Pinel Bueno |
Subject: |
Re: wget in cron issue with dns resolution of local server |
Date: |
Tue, 17 Dec 2019 17:09:09 +0100 |
Hi,
El mar., 17 dic. 2019 a las 16:36, Petr Pisar (<address@hidden>)
escribió:
> On Tue, Dec 17, 2019 at 03:45:57PM +0100, Álvaro Pinel Bueno wrote:
> > El mar., 17 dic. 2019 a las 15:36, Tim Rühsen (<address@hidden>)
> > escribió:
> >
> > > are you sure that " and * are not somehow removed / expanded ?
> > >
> > > To test, put the wget command into a shell script and start that script
> > > in the crontab. Does this make a difference ?
> > >
> >
> > Yes, I fact I realized this behavior using wget inside a bash script in
> > crontab, I copied the wget line from the script and added isolated to
> > root-cron and the behavior keep going.
> >
> Isn't the unwanted resolution of a the machine hostname performed by cron
> (or
> a sendmail command)? Cron can send an output of a job through e-mail. And
> by
> default it sends it to the owner of the crontab at the hostname. I would
> replace the wget command with something that prints to stdout and stderr
> and
> maybe exists with a non-zero exit code to verify that.
>
Of course, It's an issue with cron, with an other command happens too.
Thanks,
>
> -- Pete
>
--
*Álvaro Pinel Bueno *