From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 107723 invoked by alias); 10 Apr 2015 21:56:24 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 107699 invoked by uid 89); 10 Apr 2015 21:56:24 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.7 required=5.0 tests=AWL,BAYES_40,KAM_LAZY_DOMAIN_SECURITY,RDNS_DYNAMIC,TVD_RCVD_IP autolearn=no version=3.3.2 X-HELO: s87.webhostingserver.nl Received: from 195-211-72-128.webhostingserver.nl (HELO s87.webhostingserver.nl) (195.211.72.128) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Fri, 10 Apr 2015 21:56:23 +0000 Received: from loadbalance01.mail.antagonist.nl ([141.138.168.72] helo=proxy03.mail.antagonist.nl) by s87.webhostingserver.nl with esmtp (Exim 4.85) (envelope-from ) id 1YgguR-002j9M-8H for cygwin@cygwin.com; Fri, 10 Apr 2015 23:56:19 +0200 Received: by ignm3 with SMTP id m3so22117082ign.0 for ; Fri, 10 Apr 2015 14:56:17 -0700 (PDT) X-Received: by 10.50.18.49 with SMTP id t17mr1365570igd.3.1428702977719; Fri, 10 Apr 2015 14:56:17 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.69.34 with HTTP; Fri, 10 Apr 2015 14:55:47 -0700 (PDT) In-Reply-To: References: <2e6601d072c3$eb17d060$c1477120$@gmail.com> <5526FBA6.4070806@winfirst.com> From: Frank Fesevur Date: Fri, 10 Apr 2015 21:56:00 -0000 Message-ID: Subject: Re: Clean up /tmp on system reboot [was: Xorg server always starting up on DISPLAY 3.0] To: "cygwin@cygwin.com" Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2015-04/txt/msg00184.txt.bz2 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. Regards, Frank -- 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