Date: Mon, 7 Jun 2021 00:51:41 -0700 From: =?utf-8?Q?Ask_Bj=C3=B8rn_Hansen?= <ask@develooper.com> To: Ronald Klop <ronald-lists@klop.ws> Cc: freebsd-stable@freebsd.org Subject: Re: cron line continuation? Message-ID: <8C2E306D-032F-4224-B03F-194C30E13D43@develooper.com> In-Reply-To: <50183224.330.1623051742099@localhost> References: <0d9ed5fb-7b98-8fa5-2429-a00c615afc69@klop.ws> <20210606165738.f944a3649687a4ae09bb3cf6@getmail.no> <50183224.330.1623051742099@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_A83D529E-C52D-4500-A5AE-FAFB1DDE2243 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Jun 7, 2021, at 00:42, Ronald Klop <ronald-lists@klop.ws> wrote: >=20 > which is much better readable. I can't get this to work so the = documentation might be inconsistent. I don=E2=80=99t think cron supports escaping newline. You can escape % = as described, but (as you know) that=E2=80=99s something else. The standard solution to this is not to write programs in the cron = config. Write a script or program elsewhere and have cron execute it. Ask= --Apple-Mail=_A83D529E-C52D-4500-A5AE-FAFB1DDE2243--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8C2E306D-032F-4224-B03F-194C30E13D43>