Re: odd problem - random 2nd copy launches by itself

I believe my procedures worked. After 7.5 hours if the problem were to continue, it would 
have. i believe allowing it to properly autostart without kdesu and allowing the session 
manager to assign a session id has cured that problem. i do not know what would happen if 
i started without them running and then started them keeping the current session. there 
would be no session id. theoretically it should behave fine since other things i run do 
not duplicate. i will test that later to be sure.




On Saturday 09 January 2010, you wrote:
> I couldn't find where session manager stores its data, so I did it the hard way. Wanted 
to 
> clear the session manager completely. I killed all gkrellm, ended the session and 
rebooted 
> to clear any caches, after logging back in i started all gkrellm monitors then repeated 
> logging out rebooting and logging back in. this time, and the first time i have seen it, 
> each gkrellm has an sm-client-id attached to its process.
> 
> Maybe now it will not start it randomly.. previously I suspect the session manager kept 
a 
> memory of the kdesu startups where they had no config so there were many just gkrellm 
with 
> no configs listed in the session manager which caused them all to start as my personal 
> system monitor. at that time allow multiple copies was checked. this last reboot it was 
> unchecked. maybe it won't get confused any more. i am now also running the monitors as 
my 
> user rather than root. i will know by tomorrow since it always has misbehaved within any 
> given 6 hour period.
> 
> 
> 
> On Friday 08 January 2010, you wrote:
> > On Friday 08 January 2010, you wrote:
> > > On Fri, 8 Jan 2010 15:03:17 -0500
> > > Rio <[email protected]> wrote:
> > > 
> > > > won't that prevent me from opening 20+ monitors in one desktop?
> > > 
> > > The option locks out multiple runs only per server and or config.  So for
> > > example if you run "gkrellm -s server1" and select the option, then runs
> > > like "gkrellm -s server1 -c altconfig" or "gkrellm -s server2" will not be locked
> > > out from running.  The lock files are in /var/run/gkrellm and you can see
> > > that they will be unique for each "-c foo" and "-s server" combination.
> > > 
> > 
> > ahh ok.. cool.. now i just have to find out why the session mgr only runs gkrellm 
> without 
> > the cmdline parms.. probably has something to do with kdesu... 
> > 
> > next ill try moving the configs from /root to my user home and run them as my user and 
> see 
> > if there is a difference when it restarts.
> > 
> > 
> > > 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
> 
> 


-- 

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