On Monday 21 December 2020 10:05:11 Gene Heskett via tde-users wrote:
On Monday 21 December 2020 09:41:12 Michael via tde-users wrote:
On Monday 21 December 2020 07:28:00 am Gene Heskett via tde-users
wrote:
On Sunday 20 December 2020 16:54:40 Gene Heskett via tde-users wrote:
Now I am bumfuzzled.
I put those 2 commands in MY crontab since I can issue them without any errors.
But my crontab can't issue them. From an email I see this morning:
Cron gene@coyote /opt/trinity/bin/dcop kmail KMailIface resumeBackgroundJobs From: Cron Daemon root@coyote.coyote.den To: gene@coyote.coyote.den
ERROR: Couldn't attach to DCOP server! Two questions. And I'm starting to get pissed:
Why the hell is MY crontab sending me mail from root@coyote.den And if I can do it, why the hell can't MY crontab do it?
Thanks for any enlightenment.
No crontab knows about your $DISPLAY ;) . Check your display and add a line like I listed earlier.
If successfull, there is no display. None needed
AFAIK all email from crontabs send from root? (Well all my servers do, but check with someone who knows the guts of cron better than I.)
I cannot setuid or seteuid, crontabs error checking says that a bad minute error. Do obviously that isn't how its done. Tomas was good enough to dig up some dcop docs but it appears that I'll have to write a script to wrap those commands up after setting up an env and registering with dcop each and every time I want to automate this. Docs by doxygen are best described as contaminated by excess verbiage. Hopefully I can find something usable.
Thanks Michael.
Tomas@tuxstream.de dug up the docs for dcop at the kde 3.5 level, and that 8 pages of excess verbiage may contain the seeds that will make it work. The question then is: has anything significant been changed in the tde version?
Thanks Michael.
Cheers, Gene Heskett