X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=b2
	9u1lcE7obBfRc2X9gi1yReITdJj3oel7BVncwG4+BKP0NBXiQdp9asRDPjFe40XB
	Ez8BNQJ5CRjmCx7GFYH1ijkXK8GKNIzx4mZxRwGniNSRi7UJaAyGqOkHMN2rrL82
	ivBZocpIx1wL9lqeLqofuHvlbF5nkYWWoI/3pcLoI=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; s=default; bh=CCc1T1D8
	ZPgTGH5VnTDbvS3us0k=; b=OFmieX+Zr5jcvQftP64567stD7K5e5/vNeB9h/UM
	YNE+plt+uxyWzlsXgYOqUh4HMhK1sBzMueOsqLN1tJufTKSLIGLa4WqhTjERHT8Z
	GSHPA8eEFxFSVfRHof/U9huQNiW7sqiAjaK7vFG9bQriSoczbAcfvwwLSvdoiXRv
	7Cg=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-0.4 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	mail-lb0-f172.google.com
MIME-Version:	1.0
X-Received:	by 10.112.199.36 with SMTP id jh4mr12440439lbc.49.1428922716379; Mon, 13 Apr 2015 03:58:36 -0700 (PDT)
In-Reply-To:	<55286C63.90904@gmail.com>
References:	<2e6601d072c3$eb17d060$c1477120$@gmail.com> <mg6ne3$m61$1 AT ger DOT gmane DOT org> <5526FBA6 DOT 4070806 AT winfirst DOT com> <mg715f$g8i$1 AT ger DOT gmane DOT org> <loom DOT 20150410T012243-602 AT post DOT gmane DOT org> <CAO2ddnaUO+LiEG54GhiM1uLEYPE4p=LeFer0XjwyfRg330Q+vw AT mail DOT gmail DOT com> <CAKf2h5Skv_GbOs6Bt8=T-AieKU2OSfQKarrL4ROz8zX7mqVihg AT mail DOT gmail DOT com> <mg9cc6$22c$1 AT ger DOT gmane DOT org> <CAKf2h5TYzBcP+NQV3DiS+iM937=TbEFUix5VScMq2PrtVeOv3g AT mail DOT gmail DOT com> <55286C63 DOT 90904 AT gmail DOT com>
Date:	Mon, 13 Apr 2015 12:58:36 +0200
Message-ID:	<CAO2ddnbj2NvG1VrkzpMZQKyykHmW7ivBySqKpUma1uY+SxO-VQ@mail.gmail.com>
Subject:	Re: Clean up /tmp on system reboot [was: Xorg server always starting up on DISPLAY 3.0]
From:	=?UTF-8?Q?Kizito_Porta_Balany=C3=A0?= <kfeina AT gmail DOT com>
To:	cygwin AT cygwin DOT com

2015-04-11 2:35 GMT+02:00 LRN <lrn1986 AT gmail DOT com>:
> On 11.04.2015 0:55, Frank Fesevur wrote:
>> 2015-04-10 22:38 GMT+02:00 Andrew DeFaria:
>>>> $ man 5 crontab
>>>>
>>>> See @reboot
>>>>
>>>> Never used it but I assume it will run after cron service is started.

Yes it is.

After reading again the man, reboot is referred to the start / restart
of the cron service itself, not to the status of the reboot machine.



>>>
>>> I haven't used it either, but I saw it there. Makes you wonder what would
>>> happen if you simply restarted the service or stopped it and then started it
>>> again.
>>
>> Have cron installed on my laptop so I just tested. And yes, that is
>> how @reboot works on Cygwin. It runs the job right after the cron
>> daemon is started, regardless how many times you restart the service.
>>
>> On Linux it seems to detect that the system really was rebooted.
>>
>
> Or, if you have a lot of memory, install ImDisk, create a disk and move temp
> directory onto it. It's guaranteed to not to survive reboots. Also, it's
> probably faster than having temp directory on a real disk.
>
>
> --
> O< ascii ribbon - stop html email! - www.asciiribbon.org

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

- Raw text -