Triode Wrote:
Stuart - if you try the latest 6.5 (today's nightly), you should find
the writePrefs delay is much reduced. Do you see this?
Just picked up this message - I'll give that a try tonight and report
back to this thread. Thanks for the pointer to the update.
--
hickinbottoms
try using wordpad instead of notepad for reading back the logs. in the
dos prompt, it should be reading fine (at least it was on friday)
-kdf
___
beta mailing list
beta@lists.slimdevices.com
http://lists.slimdevices.com/lists/listinfo/beta
I noticed the same thing. There's always been a bit of inconsistency in
the logs with regard to newlines, but now it's unreadable in some
Windows editors. Looks like newlines, which were formerly CR/LF
character pairs are now LF/LF. If you can open the log in an editor
that recognizes these as
My install of 6.5 got to around 100MB of mem used, and when I woke up
this morning the service had stopped.
--
Kurt
SqueezeBox 2, interconnects spun by God himself suspended on 24K gold
support beams placed exactly .9842 inches above the floor, driving
modified Martin Logan's woven with
try using wordpad instead of notepad for reading back the logs. in the
dos prompt, it should be reading fine (at least it was on friday)
I can read it using win32pad (http://www.gena01.com/win32pad/) which is a ncie
small notepad replacement. This detects the file as UNIX format.
My point
Quoting Phil Meyer [EMAIL PROTECTED]:
My point though was that it appears that the format of the file has
recently changed, as I used to double-click to open in notepad, but
it's not very pleasant in notepad now.
I've always thought of it as unix line endings anyway, but the
occasional
kdf Wrote:
I've always thought of it as unix line endings anyway, but the
occasional debug msg erroneously lacks the \n and you get the looping
effect in those cases. Which messages are wrapping? It certainly
shouldn't be all of them, but then I've never tried to read using
Quoting JJZolx [EMAIL PROTECTED]:
The four or five startup messages (connecting to database, loading
config) have always been like this, while most other entries were
always CR/LF.
and this log appears to be all LF, which is correct. Slimserver has
always standardised on unix-style line
kdf Wrote:
I'm not really seeing the problem here. I trust someone will
enlighten me further.
I wouldn't go so far as to say you can be enlightened, but...
The vast majority of SlimServer users don't run *nix desktops. Even
among those running Linux servers, the majority run Windows
On May 15, 2006, at 3:58 PM, JJZolx wrote:
kdf Wrote:
I'm not really seeing the problem here. I trust someone will
enlighten me further.
I wouldn't go so far as to say you can be enlightened, but...
The vast majority of SlimServer users don't run *nix desktops. Even
among those running
I don't have a problem with lines ending with just a LF, if that is the
intention and it is consistent. If most developers are on an OS where this is
the native format, then I guess that may make sense. But there certainly seems
to have been a change fairly recently. Maybe it doesn't matter
Triode Wrote:
Stuart - if you try the latest 6.5 (today's nightly), you should find
the writePrefs delay is much reduced. Do you see this?
I've rerun a similar type of test with r7430 (I'd backed out the patch
to HTTP.pm so it was unmodified from the Subversion version).
As before the
12 matches
Mail list logo
