Xen wrote:
What if I write an application and I want to run it on a shell server on which I am just a guest. I want it to do logging within my personal user space. Now what?
Just write to a file?
The whole point was features remember.
No, I'm sorry, I was not aware. Features of what?
Now I need to ship my application with its own syslog daemon and logrotate facility? Maybe actually log4j also does those things so I don't need anything for java applications.
Why would you need your own syslog daemon and logrotation?
[snip]
So the answer to your question is really simple:
to have those features as part of my program instead of as part of the system on which the program runs.
That still does not explain why you _need_ your own syslog daemon and logrotation.
But on Linux, I seem to be required to use existing daemons that are system-wide, I don't know.
Applications that don't fit into to the syslog categories/facilities should probably just write their own logs. Examples - mysql, squid, apache, vsftp, zypper, snmp, plenty of them. Perhaps you can describe the problem in some more detail, I'm not sure I've really understood it.
There is a different between writing your own logs without any kind of functionality, and writing your own logs when an API for that is already present as part of existing libraries.
Not much of a difference, I submit. Whether you use your own write2log() call or that of an existing library does not make a real difference, except in the packaging (if you plan to distribute your code). -- Per Jessen, Zürich (6.9°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org