I know this isn't exactly what you're asking here but your post prompted me to realise that the ;@AC modifier will alleviate any potential RAM issues for in-car use.
Yes.
The kernel doesn't specifically allocate anything for the ktelnetd until it actually launches the daemon (
after the player starts and reads config.ini) -- at which point, it will require typical process resources, which I'd guestimate at somewhere between 4 and 8 pages (4KBytes each) of RAM.
On my own players, I use this:
[startup]
;@AC ReserveCache=8But I'm not sure if that's good or not. Works for me (
EDIT: though I used to use 64 here..)
And I've discovered a nifty method of producing an out-of-memory error on request: just run
hdparm -t /dev/hda (from a telnet session) and it will give a mysterious error message from
/bin/bash, whilst Hijack shows an out of memory popup on the display.
Cheers
Previous Topic
Index
