<div><span class="gmail_quote">2008/3/17, Simon McVittie <<a href="mailto:simon.mcvittie@collabora.co.uk">simon.mcvittie@collabora.co.uk</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Mon, 17 Mar 2008 at 14:27:06 +0100, Adrián Bravo Navarro wrote:<br> > > There's no need for environment variables and the system bus.<br> <br> <br>I assume Thiago meant "... variables *on* the system bus". Cron jobs are<br>
system services, so they should probably be using the system bus (and<br> you shouldn't need to set any environment variables to access that).<br> </blockquote></div><br>Well, what we would like is that a user crontab task could invoke a python script capable of comunicate with the daemon through dbus, so it should bind to the crontab owners bus. I think this should be the best way, but it seems that I will have to make some tricky code to achieve that goal. Anyway if you can sugest any other option to comunicate cron with the running daemon we will think about it.<br>
<br>Thanks for all the answers.<br>Adrián<br><br><br>