From mboxrd@z Thu Jan  1 00:00:00 1970
X-Received: by 10.182.245.169 with SMTP id xp9mr50418863obc.44.1427022256849;
        Sun, 22 Mar 2015 04:04:16 -0700 (PDT)
X-BeenThere: voidlinux@googlegroups.com
Received: by 10.182.153.67 with SMTP id ve3ls1147532obb.59.gmail; Sun, 22 Mar
 2015 04:04:16 -0700 (PDT)
X-Received: by 10.182.4.5 with SMTP id g5mr659868obg.24.1427022256658;
        Sun, 22 Mar 2015 04:04:16 -0700 (PDT)
Date: Sun, 22 Mar 2015 04:04:16 -0700 (PDT)
From: biopsin <bio...@gmail.com>
To: voidlinux@googlegroups.com
Message-Id: <09fe8350-dada-4362-8be9-eaf9db2f90ca@googlegroups.com>
In-Reply-To: <5f5980c4-dbcf-4705-902d-a58bb303f275@googlegroups.com>
References: <7361c5d5-2574-4c5b-9215-d81c6e8360f6@googlegroups.com>
 <d9b121da-5a0e-4369-b1d6-17d645035636@googlegroups.com>
 <5f5980c4-dbcf-4705-902d-a58bb303f275@googlegroups.com>
Subject: Re: run dcron down
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_2248_867760274.1427022256255"

------=_Part_2248_867760274.1427022256255
Content-Type: multipart/alternative; 
	boundary="----=_Part_2249_885478341.1427022256255"

------=_Part_2249_885478341.1427022256255
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hello Juan,
I'm not sure why sv status reports dcron the way it does..
0 userx ~ $ sudo sv s dcron
run: dcron: (pid 769) 3704s; down: log: 1832s, normally up

but cronjobs are being executed normal. 
Since first tests relied on notify-send I had to export dbus-sessions which 
I didn't account for at first.


On Sunday, March 22, 2015 at 8:56:29 AM UTC+1, Juan RP wrote:
>
>
> I'm running dcron in all my machines (x86, arm, etc) without any issue.
>
> I'd like to know why you had any issue at all...
>

------=_Part_2249_885478341.1427022256255
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<div dir="ltr">Hello Juan,<div>I'm not sure why sv status reports dcron the way it does..</div><div><div><div>0 userx ~ $ sudo sv s dcron</div><div>run: dcron: (pid 769) 3704s; down: log: 1832s, normally up</div></div><div><br></div></div><div>but cronjobs are being executed normal.&nbsp;</div><div>Since first tests relied on notify-send I had to export dbus-sessions which I didn't account for at first.</div><div><br></div><div><br></div><div>On Sunday, March 22, 2015 at 8:56:29 AM UTC+1, Juan RP wrote:<blockquote class="gmail_quote" style="margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;"><div dir="ltr"><br>I'm running dcron in all my machines (x86, arm, etc) without any issue.<br><br>I'd like to know why you had any issue at all...<br></div></blockquote></div></div>
------=_Part_2249_885478341.1427022256255--

------=_Part_2248_867760274.1427022256255--