X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 03D6D3858289
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1684888493;
	bh=yrNFdvCYex9i7nQj6c3p1wiAUC/Qj1m6Iz025hFLGjU=;
	h=Date:Subject:References:To:In-Reply-To:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	 From;
	b=xLXFj7d//7Ab4jBM4UwqP4pTrbDiYu3Iq2bjtDUFH9GH+1p+3PwkPNQnH10T5MA4t
	 wtPDzhf57yVL0M0Cf/I+1A1EVFevRdEMt1ldlnKReVJPRRtbgxUAHDXAm63/QHPX6X
	 Z9SzfwXj8/bCpjw04S6wEE89vgblRoHcIPQoos6o=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 69DB73858D35
X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048;
 t=1684888474; bh=FbQzUMc2zZGwm1j2xW5FyDJ5+44S4CCIVu9RJIriYN3=;
 h=X-Sonic-MF:Date:Subject:To:From:From:Subject;
 b=LPMsvic5ksCtOEYLk8+kHpg56TAli+9ilHIVv1kGIbsyIjMRS2Wyu5ixOo+CRpnFJXNKMgkTkyLFeAPo7GN3etIS3M08isgg3nRqPT17wmHOxp7K9e1DYHHnBgWGuqTYEQEuYhNbQkBIa30pEHJvyJopAa5yhdogJ09Dcdy4tX/xL41Ohusrl8tY92MYLaNENAohlotERHbLFe2OJQh7gXbJRpYK0uyQHS53Hd51Iznj3NFLHpsDzaXPOviWA878SOWDlD5qLYBVHwFUTO87nmY+2LSP2EkA+Wa0JsxvGpL/0Gnvq2IpvvvJKV97coi/FkkHKv7mw5NdC2w0zUMKbQ==
X-YMail-OSG: CdT9ikUVM1mSEOquGLMWEbJs2lyh.ucxPKjZN.6pcUVA2ULrKUTew_WH62xM9pr
 5mAzPkaJMtLm9ZB.zJUbHaSHa.Vw.HLYSSaQW3dHRFtwC13a9d.Ib4NqjkUPNtHoEImnFgNRT_nf
 d7NRNva4ymdST8NpdRylOcuXwd_m5VbDI6PPj.2IxwKaC3Czz2Zt.4qrcpUvKvfMnbi_uEIAzQFN
 HlNTtIPm0OxWQ8dnNf.AuLF5kgsIlDG_8LF2sho3XWM19CGiMXARf6pesuRsFPeYyIFDFXE3p5QO
 zVdRhUl0vHktaIO7Cl9h1RC6o7lk3MeO0tkw14pvRIc15n0xQLxGPkbwe8j727R2KSA0t1nJI7xB
 JQP5ikofq_KL.q9Poo0w2sjbIVWbT9MyBrU_9kRXxm6UC67KzAP7ryr1i3vyAIdG8ccvO9hrSUuM
 zgYv3fC9pTJa_ykwA7N6ZyPLRxfOZT0M_.SVoz9Zwzn2KQ6VKK6mlJdWe5UsiUxBm0.hfIQH1PF0
 1WbBoo71JKJNWIdh_xp0NrIylw9tr2sleZWMQbUYd4IObu4klqDLPPPlANGCnMf_DYJ.TODAcy7k
 GYFv1wXdF3HMibVywcQ5QEhBKn0.DtHD6OtaPMvPyzRHpJnA6WdYmKsrLBL7Vve5rFyKR6cLIOsw
 EWnnaHbehqTwmP23OP0hmqZri7qACOxACzRdZ.maBcK8J2q9tMs8WebXy6Qofj4J3hkw4O580dx3
 0m4L.a59JaaRkannIjZzTg_F3AYhGqmZ6dQ5Hgma1hUluRLseh2ghvSjyUagDoY3WlnL1E5mJnsL
 Lps8cxyqNSL73xlx3P3Ee3xA_CD8GaWIVjc.AyBOHXLTvJm4Gvzniw_hgqT1amS0vjGpYs7abX5A
 dO78.QYXKuR1b_vf0nTAMSrxFjpdumkRYHeX6Oft0RB_Mne0T83HBxYOUsUlAGFVNmZslRYENdaz
 4TL01k7J4QqfDmphmcqx4hpRcQejIeN0.1QFLej22D0OaPYXaSGENT0pLrjalgdhIkeRNTW6OKeH
 foMzD2yULJbRdJxpAc0Dq360_y6hbUMpz8AB0TISZCnu8JKpBVz1eFc22b.cLIcyIlK2lM8.LVj9
 n7jXoJAnKy6YG8GUUQd0mUpnaVmWKS5lkQ2iGBoBK7wneqh2d31jnnMACj4IV3s_BBc4CqfPk8Bg
 LWMLdopnP9JgCZ1__kOKViZUYuKsYzEArQMs4CO3WYJyInQ9KoewNGQaa6o9jcVdbH6YH0dGgSIy
 WLfwjOPTDI.0WjC8ipblWMs.tuL6jfdmVcOcgGE8vSR4ZdmJOYxs_0GGLA.ZaDBx5cwzR8KbtLMW
 GX_fK7Ij.gBEL_LTXSicDddO5rXWnCXXXX1QJsnM1sJ2yd1dHbB8nbR1luYrRp6ZtZjWCxNQ1Ga8
 IPqqfkr7.e3lpcUQP8IcufgtF7y2VEQ9qkuPJjuxam8.qZqOcMb01dlLgr4jb2vG4fm6ytBSVHnl
 4YbgiVQUjQCtScH8_jo8dtdpjtrOmLJQ7yFuy6YzuwyX4QXE.14yk_IqAkvIGfJ_2pMgXwCOAmP2
 xXTdvzcS03xc6wi2sCZghRR6FIaKIFVT7WX1bNQYIcGx0KjoAZgeN2Z_bxLVqiXeXL1i7R_dV0Su
 LDp7tlG2BowN8MsgLjAS5HMzxU2JG4hgf_DOqIok4rbmU34OUIvXOP.SAdWV5jRJOcI9Sj0Nn0wq
 MIAJGc2p8Nzz_q5M2MURMzplSqRqq.xr5.w6dloV16cHk.PwB3CCUdomjP63xOo70v0Ywz2r4QGO
 exgUvxOUf1cs1E7gwqNwqluJw5GGVf.5WSBSgUvzYMLwnlYKg756ewnVK0uPe_v_iw7NYuTNafJY
 wEX8vUGtTU4pQ1DuMDtqXXjWcmvNf9nELU0_1dFi_hv6BI6YDjSH0kCo2.QD.GXKpryDK6W3_Fy5
 VS.Pp3Z.705dNqAhHkiVHazBxShMmPHjrC.JyDDbyrGVKzkFwX1LqNxJ97EGH9Xp62m5Asv6N128
 ql.QnvHUEbw_pzJrURnBaLRz4L_dw2iZ4kaKNPifPFltwb9s37Fi4izfRw_nxKukD8OT9X5caPBu
 j9hH5kApX_hFlcbORmgIH25CRfy8lBXVUj3ObaU.nj.vrN16ua3spqyoGKwggUaEQsIyksMsYqKN
 Z10zm9OmwzXwPoCuOzC8ZX.MAPMso7ILR2GxLyzCTqYNMAVHD_Dmdar.0Oi.sK39QfheUj_GzFSv
 YjDRWe_E6933W2Pc9UhjsGZbwKD8-
X-Sonic-MF: <jonathan AT att DOT net>
X-Sonic-ID: fca35371-0de0-4325-9f78-8748063b4c7d
Message-ID: <87bb1215-e594-aec3-8242-df1099b051b2@att.net>
Date: Tue, 23 May 2023 20:32:26 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101
 Thunderbird/102.11.0
Subject: Re: cron: trying and totally failing to run a simple cron job - fixed
 (with comments)
Content-Language: en-GB
References: <58cf0c8a-9f49-fb2d-a2ff-f9985f69e157 DOT ref AT att DOT net>
 <58cf0c8a-9f49-fb2d-a2ff-f9985f69e157 AT att DOT net>
 <7018868f-be47-59bf-0174-8f32307579fc AT Shaw DOT ca>
 <bb6e7f66-03c7-7601-ed2b-88ae9f31fd80 AT att DOT net>
To: cygwin AT cygwin DOT com
In-Reply-To: <bb6e7f66-03c7-7601-ed2b-88ae9f31fd80@att.net>
X-Mailer: WebService/1.1.21495
 mail.backend.jedi.jws.acl:role.jedi.acl.token.atz.jws.hermes.yahoo
X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, NICE_REPLY_A,
 SPF_HELO_NONE, SPF_NONE, TXREP,
 T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
 server2.sourceware.org
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: Jonathan Clark via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Jonathan Clark <jonathan AT att DOT net>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

I got this running. In the hope that it may help others, I give some details here.

It turned out that I was on the right track - it *was* the space in my Windows username which was making cron complain. The simple addition of a (basically completely fake but plausible) MAILTO line in the crontab got past the UNSAFE and the cron job started working, more or less. Brian also mentioned that he used a MAILTO, which was helpful. Thanks!

That was not quite the end of the story. With the cron job working, I went looking for the output.
I couldn't use a real email address in the MAILTO because I don't know how to persuade sendmail to use the SMTP SUBMIT protocol (anyone?), but it took me some time to find the cron.log file, which was hiding in "/cygdrive/c/cygwin64/home/Jonathan Clark". I didn't even know that directory existed, so this was all terribly exciting. Setting HOME in the crontab to my "real" HOME (or at least somewhere I could remember to look) solved that problem.

While poking around Vixie's source code I ran across this bug fix:
https://github.com/vixie/cron/commit/690fc534c7316e2cf6ff16b8e83ba7734b5186d2
which I am fairly sure explains my observation of the delay in picking up a changed crontab.

Anyway, thanks for the help! And thanks again to everyone for the work on cygwin.

Jonathan


-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple