From: Luis.F.Correia <Lui...@se...> - 2003-08-07 16:39:22
|
> >>>in our system we do not have /prog/kcore, so lots of info=20 > >>do not appear. > >>The only client that uses /proc/kcore is "Ram" (forgot about=20 > >>the token=20 > >>now), it uses "sizeof(/proc/kcore)" because /proc/meminfo=20 > gives wrong=20 > >>results here. > > We do have /proc, but one of our security fixes,=20 > grsecurity, disables > > access to /proc/kcore. >=20 > Hmm... I do not "access" it. I just call 'stat("/proc/kcore",=20 > &buf)'. I=20 > don't understand why this is disabled, I don't see any=20 > security reasons=20 > here. If you have /proc/kcore you can open it and read/write the memory positions... >=20 > > We will find a way to display the correct amount of system memory. >=20 > Well, I've to change this thing anyway, because I recently=20 > noticed that=20 > with "highmem" (or whatever this stuff is called) gives wrong results = > with the sizeof(kcore) approach. >=20 > Anybody has got a hint how to detect the "real" amount of=20 > memory built=20 > into a PC? >=20 > >>>>From the docs and the token list, i cannot find the=20 > >>equivalent of 'uptime'. > >>No. This is a good example for a plugin. have a look at the=20 > >>"%x" tokens... >=20 > There's another thread "Text overlay problem", looks like this guy=20 > already has written (or stolen :-) such a plugin. >=20 >=20 > >>my > >>notebook was stolen during a flight from d=FCsseldorf to graz. = Shit! > > Very bad indeed, I hope you can sue the travel agency for that... > No, I can't. Nobody can. It's explicitly stated in their=20 > "Bef=F6rderungsbedingungen" (what's the english word?) that = electronic=20 "Terms of use"? > devices such as computers are not assured. And even if they would be, = > not based on their value, but only on weight! Strange... >=20 > >>>The daemon must know about the 'pid' file. can you add support? > > Some changes must be made until we consider it production package. > > The most important is the start-stop thing... >=20 > Ok, I will implement this stuff really soon (at least I'll try to). >=20 > Anybody with hints where one could steal^Hlook up good code=20 > for pid file=20 > handling? No. well at least no now... i'll keep you posted. >=20 > What should happen if there are two instances of lcd4linux=20 > running? Two=20 > pid files? This should not happen. At least on a router. |