From: LRN <lrn1986@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Clean up /tmp on system reboot [was: Xorg server always starting up on DISPLAY 3.0]
Date: Sat, 11 Apr 2015 00:35:00 -0000 [thread overview]
Message-ID: <55286C63.90904@gmail.com> (raw)
In-Reply-To: <CAKf2h5TYzBcP+NQV3DiS+iM937=TbEFUix5VScMq2PrtVeOv3g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 959 bytes --]
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.
>>
>> 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
[-- Attachment #1.2: 0x922360B0.asc --]
[-- Type: application/pgp-keys, Size: 1747 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2015-04-11 0:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 12:51 cyg Simple
2015-04-09 20:29 ` Andrew DeFaria
2015-04-09 22:22 ` Mark Hansen
2015-04-09 23:15 ` Andrew DeFaria
2015-04-09 23:27 ` Mark Geisert
2015-04-10 7:49 ` Kizito Porta Balanyà
2015-04-10 8:20 ` Frank Fesevur
2015-04-10 20:39 ` Andrew DeFaria
2015-04-10 21:56 ` Frank Fesevur
2015-04-11 0:35 ` LRN [this message]
2015-04-13 10:58 ` Kizito Porta Balanyà
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55286C63.90904@gmail.com \
--to=lrn1986@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).