2015-04-11 2:35 GMT+02:00 LRN :
> 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 ref
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 yo
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 th
On 4/10/2015 1:19 AM, Frank Fesevur wrote:
2015-04-10 9:49 GMT+02:00 Kizito Porta Balanyà:
I'm wondering how cron knows when a machine is rebooted.
What does cron check? Which parameter / file?
Do you know it?
$ man 5 crontab
See @reboot
Never used it but I assume it will run after cron serv
On 4/9/2015 5:51 AM, cyg Simple wrote:
From: Jim Reisert AD1C
Wouldn't it be nice if Cygwin cleaned up the /tmp directory each time the
computer is re-booted? I don't know how that would work in real life,
however.
Simply create a scheduled task to execute a windows batch file on system
s
From: Jim Reisert AD1C
>
> Wouldn't it be nice if Cygwin cleaned up the /tmp directory each time the
> computer is re-booted? I don't know how that would work in real life,
however.
>
Simply create a scheduled task to execute a windows batch file on system
start that changes directory to the Cy
On Mon, Mar 30, 2015 at 8:17 AM, Jon TURNEY wrote:
> You have stale lock files /tmp/.X0-lock etc.
>
> Unfortunately startx(|win) is not as smart as it should be about detecting
> that the process owning the lock file is no longer running.
That was indeed the problem. I didn't find them because m
On 27/03/2015 15:48, Jim Reisert AD1C wrote:
I'm running Cygwin/X server Version 1.17.1. For the last couple of
weeks, it's always starting on DISPLAY 3.0:
DISPLAY=:3.0
I can't figure out how to get it back to 0.0. There must be some
piece of state somewhere that I can't find.
You have
I'm running Cygwin/X server Version 1.17.1. For the last couple of
weeks, it's always starting on DISPLAY 3.0:
DISPLAY=:3.0
I can't figure out how to get it back to 0.0. There must be some
piece of state somewhere that I can't find.
Thanks - Jim
--
Jim Reisert AD1C, , http://www.ad1c.us
9 matches
Mail list logo
