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
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>