Void Linux discussion
 help / color / mirror / Atom feed
* run dcron down
@ 2015-03-15 13:20 biopsin
  2015-03-15 17:05 ` Stefan Mühlinghaus
                   ` (3 more replies)
  0 siblings, 4 replies; 9+ messages in thread
From: biopsin @ 2015-03-15 13:20 UTC (permalink / raw)
  To: voidlinux


[-- Attachment #1.1: Type: text/plain, Size: 976 bytes --]

I want to play with dcron but I'm having a user issue..

I linked /etc/sv/dcron to /etc/runit/runsvdir/current/dcron
and started the service but I get
run: /var/service/dcron: (pid 8134) 10s; down: log: 1s, normally up, want up

/etc/sv/dcron/run
-rwxr-xr-x 1 root root 40 Mar 15 12:19 run
exec /usr/sbin/crond -f 2>&1   # -f or -b ?

/
-rwx------ 1 root root 36576 Oct 13 18:42 /usr/sbin/crond
-rwsr-xr-x 1 root root 13192 Oct 13 18:42 /usr/bin/crontab

/var/spool/
drwxr-xr-x  2 root root 4096 Mar 15 13:43 cron
-rw-r----- 1 root root   513 Oct 13 18:42 root

drwxr-xr-x  2 root root 4096 Mar 15 13:43 cronstamps
-rw-r--r-- 1 root root    16 Mar 15 13:19 root.sys-daily
-rw-r--r-- 1 root root    16 Mar 15 12:48 root.sys-hourly
-rw-r--r-- 1 root root    22 Mar 15 11:45 root.sys-monthly
-rw-r--r-- 1 root root    22 Mar 15 11:45 root.sys-weekly

run-parts --test /etc/cron.hourly
/etc/cron.hourly/yr
-rwxr-xr-x  1 root root  219 Mar 15 11:41 yr


[-- Attachment #1.2: Type: text/html, Size: 1411 bytes --]

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: run dcron down
  2015-03-15 13:20 run dcron down biopsin
@ 2015-03-15 17:05 ` Stefan Mühlinghaus
  2015-03-15 19:17   ` biopsin
  2015-03-15 23:01 ` JD Robinson
                   ` (2 subsequent siblings)
  3 siblings, 1 reply; 9+ messages in thread
From: Stefan Mühlinghaus @ 2015-03-15 17:05 UTC (permalink / raw)
  To: voidlinux


[-- Attachment #1.1: Type: text/plain, Size: 89 bytes --]

Try running "crond -f" manually as root and see if that gives you any error 
messages.

[-- Attachment #1.2: Type: text/html, Size: 106 bytes --]

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: run dcron down
  2015-03-15 17:05 ` Stefan Mühlinghaus
@ 2015-03-15 19:17   ` biopsin
  0 siblings, 0 replies; 9+ messages in thread
From: biopsin @ 2015-03-15 19:17 UTC (permalink / raw)
  To: voidlinux


[-- Attachment #1.1: Type: text/plain, Size: 139 bytes --]

Runs ok under root and with sudo.
Just can't get it to execute any crontabs if run as service..
Might stick crond in rc.conf for now...

[-- Attachment #1.2: Type: text/html, Size: 176 bytes --]

^ permalink raw reply	[flat|nested] 9+ messages in thread

* run dcron down
  2015-03-15 13:20 run dcron down biopsin
  2015-03-15 17:05 ` Stefan Mühlinghaus
@ 2015-03-15 23:01 ` JD Robinson
  2015-03-15 23:41 ` Stefan Mühlinghaus
  2015-03-16 13:38 ` Stefan Mühlinghaus
  3 siblings, 0 replies; 9+ messages in thread
From: JD Robinson @ 2015-03-15 23:01 UTC (permalink / raw)
  To: voidlinux

[-- Attachment #1: Type: text/plain, Size: 226 bytes --]

Instead try:

sv up crond

And see if that gives you any information.

You might try running crond with different command line arguments. There doesn't seem to be a cron group by default and this might also be an issue. 

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: run dcron down
  2015-03-15 13:20 run dcron down biopsin
  2015-03-15 17:05 ` Stefan Mühlinghaus
  2015-03-15 23:01 ` JD Robinson
@ 2015-03-15 23:41 ` Stefan Mühlinghaus
  2015-03-16  8:54   ` biopsin
  2015-03-16 13:38 ` Stefan Mühlinghaus
  3 siblings, 1 reply; 9+ messages in thread
From: Stefan Mühlinghaus @ 2015-03-15 23:41 UTC (permalink / raw)
  To: voidlinux


[-- Attachment #1.1: Type: text/plain, Size: 230 bytes --]

I can see no problem with the service. Maybe you just need to do a 
"xbps-reconfigure -f dcron"?
No explicit "cron" group should be needed.
Are you sure the crontabs are processed as intended if you run the daemon 
manually?

[-- Attachment #1.2: Type: text/html, Size: 263 bytes --]

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: run dcron down
  2015-03-15 23:41 ` Stefan Mühlinghaus
@ 2015-03-16  8:54   ` biopsin
  0 siblings, 0 replies; 9+ messages in thread
From: biopsin @ 2015-03-16  8:54 UTC (permalink / raw)
  To: voidlinux


[-- Attachment #1.1: Type: text/plain, Size: 720 bytes --]

Thank you both for the time and helpfulness..

There was a update to dcron today and even the status of service still 
remains 
run: /var/service/dcron: (pid 780) 109s; down: log: 0s, normally up, want up

it's executing my tests as we speak after a reboot, and I also did 
-reconfigure but unsure if anything changed..

by the way how do I edit my post to change the head to SOLVED ? 

On Monday, March 16, 2015 at 12:41:25 AM UTC+1, Stefan Mühlinghaus wrote:
>
> I can see no problem with the service. Maybe you just need to do a 
> "xbps-reconfigure -f dcron"?
> No explicit "cron" group should be needed.
> Are you sure the crontabs are processed as intended if you run the daemon 
> manually?
>

[-- Attachment #1.2: Type: text/html, Size: 970 bytes --]

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: run dcron down
  2015-03-15 13:20 run dcron down biopsin
                   ` (2 preceding siblings ...)
  2015-03-15 23:41 ` Stefan Mühlinghaus
@ 2015-03-16 13:38 ` Stefan Mühlinghaus
  2015-03-22  7:56   ` Juan RP
  3 siblings, 1 reply; 9+ messages in thread
From: Stefan Mühlinghaus @ 2015-03-16 13:38 UTC (permalink / raw)
  To: voidlinux


[-- Attachment #1.1: Type: text/plain, Size: 271 bytes --]

You cannot change your posts after you have posted them. Maybe the groups 
owner can, but I am not certain about that.
The best you can do is to post that your problem has been solved and maybe 
how it was solved, if that is not already evident from the prior posts.

[-- Attachment #1.2: Type: text/html, Size: 295 bytes --]

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: run dcron down
  2015-03-16 13:38 ` Stefan Mühlinghaus
@ 2015-03-22  7:56   ` Juan RP
  2015-03-22 11:04     ` biopsin
  0 siblings, 1 reply; 9+ messages in thread
From: Juan RP @ 2015-03-22  7:56 UTC (permalink / raw)
  To: voidlinux


[-- Attachment #1.1: Type: text/plain, Size: 127 bytes --]


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...

[-- Attachment #1.2: Type: text/html, Size: 156 bytes --]

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: run dcron down
  2015-03-22  7:56   ` Juan RP
@ 2015-03-22 11:04     ` biopsin
  0 siblings, 0 replies; 9+ messages in thread
From: biopsin @ 2015-03-22 11:04 UTC (permalink / raw)
  To: voidlinux


[-- Attachment #1.1: Type: text/plain, Size: 522 bytes --]

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...
>

[-- Attachment #1.2: Type: text/html, Size: 805 bytes --]

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2015-03-22 11:04 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-03-15 13:20 run dcron down biopsin
2015-03-15 17:05 ` Stefan Mühlinghaus
2015-03-15 19:17   ` biopsin
2015-03-15 23:01 ` JD Robinson
2015-03-15 23:41 ` Stefan Mühlinghaus
2015-03-16  8:54   ` biopsin
2015-03-16 13:38 ` Stefan Mühlinghaus
2015-03-22  7:56   ` Juan RP
2015-03-22 11:04     ` biopsin

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 NNTP newsgroup(s).