On 2016-04-10 01:55, Xen wrote:
Carlos E. R. schreef op 10-04-16 01:34:
Is there such a library? Apparently and probably not because everyone believes we should use syslogd.
You forget that there are many applications in Linux that use their own logging systems.
Which one? Or do they all reinvent the wheel?
As I'm not a Linux programmer, I can't say if a library for the purpose exists or not. For example, procmail uses its own system. At the start of the config, you define where: LOGFILE=$HOME/procmail.log Another one: fetchmail. At the start of the config you tell it whether to use syslog or not: set syslog alternatively, use "nosyslog" and "logfile". Another. Amavis-new. I see this in the configuration (there is no man page for a quick search): $do_syslog = 1; # log via syslogd (preferred) Another one: YaST. Or zypper. That makes two. Wait! Looking at /var/log/ I notice some more: apache, consolekit, apparmor, audit, cacti, cups, gdm, lightdm, mysql, nagios, ntop, sa, samba, smpppd, snort, vmware... I notice them because they have their own log directories. There are a few more that use distinct files under /var/log/, without a separate directory, but differentiating which are used by syslog and which not is a bit more difficult. The first one is now extinct: SaX. But Xorg is not. There are some that log in binary: lastlog And I see more... Just look for yourself. :-)
The user "space" is not really well defined or understood in Linux. There is no middle ground. Something that is readily availabe in Java does not even exist in Linux.
Well, no. Linux, or rather Unix, was designed with a single admin with full powers. It is not that simple to modify this basic idea.
I know, but I'm trying anyway. Cause the current system causes groups to not be used, and causes problems for me. So I need to get around it anyway.
No, you can't. You can use tricks, but there is only one root, and he can not delegate that easily - except with sudo and groups. And acls. You can not define a root.for.mail admin that can do anything on all the mail directories and programs. Instead, you have to modify the permisions for groups on those directories, specify sudo commands for anything he might need, and provision for files that on creation/modification on those directories have appropriate permissions so that he has full control of them. A Windows server admin has a more complex and fine grained set of permissions, including creating partial administrators. Hey, I'm a Linux guy, but the truth is the truth... Not that it is simple in Windows, either. Far from it. Say, a backup admin. In Linux it has to be root.
On the other hand, it is quite feasible for the designer of any application to allow it to be administered by another user.
You mean with a setuid program or something of the kind?
Yes, something, if the application is designed from the start to be administered by somebody else. Databases, for instance, typically have a database admin with a different name from root, if specified. He probably can not install the database on the computer, though. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)