mherger wrote:
> > No, AFAIK, 500 is the number of cached tracks. After that, they
> should
> > be closed but I'm not sure that works as expected. I've reduced
> that to
> > 10 and traced DESTROY it's very unclear to me when it happens,
> except
> > when you terminate the slimserver process. The
No, AFAIK, 500 is the number of cached tracks. After that, they should
be closed but I'm not sure that works as expected. I've reduced that to
10 and traced DESTROY it's very unclear to me when it happens, except
when you terminate the slimserver process. The code is in
/usr/share/perl5/Slim (from
https://github.com/ralph-irving/jivelite/tree/master/share/jive/applets
Sorry to ask: is there a description of these applets and how to install
There's not much to install: they already are. Or did you find one which
isn't?
Best description you'd probably find in the strings.txt you'd find
mvordeme wrote:
> That is a fact which makes investigating the problem difficult. When
> there are 500 open file handles, it is difficult to keep track of what
> is happening.
>
> I understand from the code that with a memory configuration of high, the
> process should not use up more than 500
mherger wrote:
> > Not sure if this has been discussed or requested... Is there a way or
> a
> > community project to update Jivelite skin?
>
> Not only can you update it, but you can even add more of them. You could
>
> work on your own skin without touching the existing ones. Skins are
> im
thejeko wrote:
> Hello everybody,
> after a couple of days of full immersion in this project and after
> having read all the messages and tried practically everything I have
> read, I have to annoy you because some things just do not get there.
>
> 1. How do I increase the fluidity and sensitiv
Last I checked, wpa_supplicant is built with the same compile options as
debian. But I have no way to test enterprise stuff.
I would run wpa_cli, and try to execute commands and see what it
says.. it should give you more debugging info. Obviously you will
need a keyboard/monitor or ether
pCP does not use X11
So someone has to work out what their scripts do to see if it is
essential ... and if not then document how to get it working.
If you are lucky someone has already done it and documented it.
So first thing to do is search around.
Something like this might help (towards the e
That is a fact which makes investigating the problem difficult. When
there are 500 open file handles, it is difficult to keep track of what
is happening.
I understand from the code that with a memory configuration of high, the
process should not use up more than 500 MB of memory. Is that correct
mvordeme wrote:
> I am not sure about all the debugging stuff, but it appears to me that
> it is not a matter of configuring things but of changing the code. I
> have tried to increase the amount of logging for a few items but didn't
> learn much. Where is all the code? The directory containing
10 matches
Mail list logo
