Am Samstag, 21. März 2015 schrieb Gene Heskett:
> 
> On Friday 20 March 2015 22:13:50 Gene Heskett wrote:
> > On Friday 20 March 2015 14:17:30 Gene Heskett wrote:
> > > On Friday 20 March 2015 13:38:37 Gerhard Zintel wrote:
> > > > On Friday 20 March 2015, Gene Heskett wrote:
> > > > > From a konsole:
> > > > > gene@coyote:/etc/apache2/mods-available$ xhost +
> > > > > access control disabled, clients can connect from any host
> > > > >
> > > > > Ooookkaaaayy.  If thats true, why can't cron do it?
> > > > >
> > > > > Wheezy gets more and more confused.  Or I do, but I like the
> > > > > former argument lots better. :)  Saves face at my age yadda
> > > > > yadda.
> > > >
> > > > because the command has to run on that X session to be effective,
> > > > cron is not running on the X session, it's running in the
> > > > background not connected to any X session.
> > > >
> > > > Gerhard
> > >
> > > So I put it in my .bashrc.  It works, AND I can now run a sudo
> > > command as before all this denial of service started that made me
> > > set a root password.  But the only way to get rid of a root password
> > > is a bare metal reinstall.
> > >
> > > Sigh...
> > >
> > > Cheers, Gene Heskett
> >
> > As a delayed PS here, cron, despite my best incantations, is still
> > sending me failure emails, cannot open display 0:0.
> >
> > Humm, thats is a direct command from crontab to xset. Theory:
> > If I put an sh in front of the command, will that sh then see the
> > results of the xhost + command in the .bashrc?
> >
> > Worth a try I think.
> 
> And fails exactly the same, my crontab entry cannot access my  0:0 
> display.  Help!
> 
> Thanks all.
> 
> Cheers, Gene Heskett

Hi Gene!

Your .bashrc is not evaluated by the TDE session till you open a terminal. That's why I siggested to use the Autostart-shortcut :-)

Nik


-- 
Please do not email me anything that you are not comfortable also sharing with the NSA.

Dr. Nikolaus Klepp
Einnehmerstraße 14
A-4810 Gmunden
Tel.: +43 650 82 11 724
email: office@...