On Wed, 21 Dec 2011, Brian Swetland wrote:
The result would be much the same amount of code, but an interface which
has
fewer details hard-coded and is generally more versatile and accessible.
That sounds better than what has been done in android, but it is still _far_
more limited than doing something that could be replaced by a fairly
standard syslog daemon.
We're really not interested in adding another daemon to the platform
-- the logging system we have has served us well, is integrated with
our existing development tools, and we're definitely interested in
improving it, but throwing it out and replacing it with a userspace
solution is not interesting to us right now.
Think very hard before you reject any possibility of doing this in
userspace, especially with all the things that you are talking about doing
with logging in the future. I really don't think aht a lot of your
long-0term plans for logging are going to sit well with the kernel
developers, and if your justification is "you don't want to change your
build process", I really doubt that you will get this upstream.
It should be possible to do this without having to change the tools
writing the logs, any change in logging will change what it takes to read
the logs.
I am not saying that you need to have a logging daemon as heavyweight as
syslog-ng or rsyslog for the low-end phones, but I do think that as
android moves up the stack a bit into talets and netbooks (especially in
applications where it will have wifi connectivity almost all the time)
having the capability to move to a full-blown syslog daemon will make a
huge amount of sense, so you should look at how big a minimalist daemon
would be, and what sort of performance it would have.
David Lang
--
To unsubscribe from this list: send the line "unsubscribe linux-embedded" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
