Re: gkrellmd question

On Thursday 14 January 2010, you wrote:
> On Thursday 14 January 2010, you wrote:
> > On Thu, 14 Jan 2010 20:18:35 -0500
> > Rio <[email protected]> wrote:
> > 
> > > and i ran the client using this last configuration and it sees the vid perfectly :)
> > > 
> > > i am going to try running the regular distribution daemon now to see how that works
> > > 
> > > ok here is what happens..
> > > 
> > > i used your debug daemon in place of the production one. i ran it as my desktop 
user.. 
> no 
> > > video temps.. i ran it as root and ran the client as my desktop user and i have 
temps.
> > > 
> > > i have no clue how to check what has permission to open the x display. i could just 
> run 
> > > the daemon as root since it only looks at localhost. i will compile another gkrellmd 
> since 
> > > in my haste to try this i did not makea backup of the binary and try that as root.
> > 
> > So it seems it is a permissions problem.  When you login to X, only the login user
> > has permission to open the X display.  And since nvidia-settings needs to talk
> > to the X display kernel module, the gkrellmd program also needs that permission.
> > The login user can give permission to other users using xhost.  The man page
> > says that you can give permission to individual users, but it doesn't work for me.
> > I can only give permission to all local users with:  xhost +local:
> > Run xhost with no args to see the access list.
> > 
> 
> interesting.. ok thanks.. 
> 
> 

hehe after rebooting, even in local startup file it doesn't work because gkrellmd is 
started before X is initialized i think, and xhost doesnt work there since it cannot find 
a screen yet... i had to move gkrellmd startup to kde's Autostart directory which started 
it with proper visibility. only caveat is the client gives an error it cannot find the 
server but i hit try again and then it works. probably due to desktop inits starting 
before the autostart script. minor inconvenience and im not going to persue it further 
since it does work and if a single click every startup is what it takes then fine. i only 
reboot the machine once a week or so anyway and the only reason i do that is one of my 
applications is a bit messy with memory so within 5 days or so it gets a bit high in usage 
(85%). dont mind reboot once a week, it helps to keep caches and /tmp cleaned up.




> > Bill
> > 
> > 
> > 
> > ______________________________________________
> > Gkrellm mailing list
> > [email protected]
> > Read archives-join-leave-set RSS feed:
> > http://archive.lists.netservicesgroup.com
> > This service is provided by The Network Services Group:
> > http://www.netservicesgroup.com
> > 
> > 
> 
> 
> -- 
> 
> Rio
> 
> 
> ______________________________________________
> Gkrellm mailing list
> [email protected]
> Read archives-join-leave-set RSS feed:
> http://archive.lists.netservicesgroup.com
> This service is provided by The Network Services Group:
> http://www.netservicesgroup.com
> 
> 


-- 

Rio


______________________________________________
Gkrellm mailing list
[email protected]
Read archives-join-leave-set RSS feed:
http://archive.lists.netservicesgroup.com
This service is provided by The Network Services Group:
http://www.netservicesgroup.com