[opensuse] xinetd logs go to the wrong place
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have in /etc/xinetd.conf this line: log_type = FILE /var/log/xinetd.log But entries are going to syslog instead: <3.6> 2014-03-01 13:58:34 Telcontar xinetd 979 - - EXIT: nntp status=0 duration=626(sec) <3.6> 2014-03-01 14:08:54 Telcontar xinetd 979 - - START: nntp from=127.0.0.1 <3.6> 2014-03-01 14:08:54 Telcontar xinetd 979 - - START: nntp from=127.0.0.1 <3.6> 2014-03-01 14:08:55 Telcontar xinetd 979 - - EXIT: nntp status=0 duration=622(sec) And nothing to /var/log/xinetd.log since I upgraded to 13.1: 14/2/25@02:25:46: EXIT: nntp status=0 duration=21(sec) 14/2/25@02:25:46: EXIT: nntp status=0 duration=925(sec) ; - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - : ; Upgrading from 12.3 to 13.1 here ; ; - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Is this a bug? - -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlMR5lYACgkQtTMYHG2NR9XOqQCdHv8JaoNTyHLX0jH+GwLKUD9h 1EYAoIGmI78ibCl5OHwBpngqQHwMpvaL =qSF+ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 01/03/14 10:53, Carlos E. R. escribió:
Is this a bug?
Maybe, what package provides this particular nntp thing ? it has to be changed to just use systemd and not xinetd.. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-03-01 15:55, Cristian Rodríguez wrote:
El 01/03/14 10:53, Carlos E. R. escribió:
Is this a bug?
Maybe, what package provides this particular nntp thing ? it has to be changed to just use systemd and not xinetd..
Why? xinetd is an openSUSE provided package, and it has not been deprecated, AFAIK. That's not the issue. The package is leafnode, anyway. And there are many other packages using xinetd, like "vsftpd", for instance. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
El 01/03/14 12:16, Carlos E. R. escribió:
Why? xinetd is an openSUSE provided package, and it has not been deprecated, AFAIK. That's not the issue.
Yes but both the management of services and log collection has to be centralized to systemd and the journal.
The package is leafnode, anyway. And there are many other packages using xinetd, like "vsftpd", for instance.
Yeah, but we have to change that at some point. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-03-01 19:33, Cristian Rodríguez wrote:
El 01/03/14 12:16, Carlos E. R. escribió:
Why? xinetd is an openSUSE provided package, and it has not been deprecated, AFAIK. That's not the issue.
Yes but both the management of services and log collection has to be centralized to systemd and the journal.
So, you are saying that xinetd fails to obey its own config file, because systemd people orders that to happen? I don't understand. And you also say that syslog does not control what goes into its own log file, if they are systemd entries?
The package is leafnode, anyway. And there are many other packages using xinetd, like "vsftpd", for instance.
Yeah, but we have to change that at some point.
So, everything in Linux will be systemd? No more small applications doing perfectly their jobs, as the age old practice was? Sigh :-/ So, welcome to the systemd Empire. No more Linux. :-/ - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlMSN28ACgkQtTMYHG2NR9WoWwCdEbNlSGmAR/21marCYuH6GsdT 4iwAn3QOkhbPlj0NAdmTrhb8I2ezCvrO =D4Lu -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 01/03/14 16:39, Carlos E. R. escribió:
So, you are saying that xinetd fails to obey its own config file, because systemd people orders that to happen?
Nope...
And you also say that syslog does not control what goes into its own log file, if they are systemd entries?
No, the journal forwards all data it receives to a socket that is then consumed by a syslog implementation if any.
The package is leafnode, anyway. And there are many other packages using xinetd, like "vsftpd", for instance.
Yeah, but we have to change that at some point.
So, everything in Linux will be systemd? No more small applications doing perfectly their jobs, as the age old practice was?
No, nothing will stop you from using xinetd..but *packages* should only include systemd native units for service management, to centralize it in one place and reduce duplication of functionality and maintenance burden.. This is similar to cronjobs that have to be migrated as some point to use systemd timers..of course no one is going to modify the sysadmin cronjobs or remove cron from the installed system.. just those scripts included in packages. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2014-03-01 at 17:05 -0300, Cristian Rodríguez wrote:
El 01/03/14 16:39, Carlos E. R. escribió:
...
No, nothing will stop you from using xinetd..but *packages* should only include systemd native units for service management, to centralize it in one place and reduce duplication of functionality and maintenance burden..
This is similar to cronjobs that have to be migrated as some point to use systemd timers..of course no one is going to modify the sysadmin cronjobs or remove cron from the installed system.. just those scripts included in packages.
Ok. So, as I'm using packages supplied by the distribution (xinetd, vsftp, leafnode...) it is not my job to alter them to use systemd services, and I am correct to expect that they work as supplied. It is somebody else's job to change them to work, some day in the future, to work via systemd instead. So, the question still is, why does xinetd not work? Well, I found it. The default configuration is: +++······························ # Previous default in SUSE - please don't forget to use the logrotate. The # sample configuration is in /usr/share/packages/doc/xinetd/logrotate # log_type = FILE /var/log/xinetd.log # Define general logging characteristics. log_type = SYSLOG daemon info log_on_failure = HOST ATTEMPT log_on_success = HOST EXIT DURATION ······························++- It is not enough to remove the comment from the first entry; the second entry has to be commented out, or perhaps the entire paragraph: +++······························ # Previous default in SUSE - please don't forget to use the logrotate. The # sample configuration is in /usr/share/packages/doc/xinetd/logrotate log_type = FILE /var/log/xinetd.log # Define general logging characteristics. # log_type = SYSLOG daemon info log_on_failure = HOST ATTEMPT log_on_success = HOST EXIT DURATION ······························++- Or, I can leave it as it is now, logging via syslog, and using "/etc/rsyslog.conf" to reroute it again to "/var/log/xinetd.log". I'll have to find out what the differences are. - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlMSUyUACgkQtTMYHG2NR9VTEACgiMrraFXbR8GfmDBeS/zFmCzX sqgAn2+frwqMXVmFv1fPbJ5P4uwrT+Q+ =6LVs -----END PGP SIGNATURE-----
On 01/03/14 08:53 AM, Carlos E. R. wrote:
I have in /etc/xinetd.conf this line:
log_type = FILE /var/log/xinetd.log
But entries are going to syslog instead: [....]
Is this a bug?
My read of the man page is that the settings are for each service. The way I had things set up was to have each service in a separate file and then be included. See the "includedir" entry in the man page. You don't say what service*S* you have this applied to. I do note that the man page says <quote> The configuration file may also contain a single defaults entry that has the form defaults { <attribute> = <value> <value> ... ... } -- My definition of an expert in any field is a person who knows enough about what's really going on to be scared. P. J. Plauger, Computer Language, March 1983 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-03-01 16:04, Anton Aylward wrote:
On 01/03/14 08:53 AM, Carlos E. R. wrote:
I have in /etc/xinetd.conf this line:
log_type = FILE /var/log/xinetd.log
But entries are going to syslog instead: [....]
Is this a bug?
My read of the man page is that the settings are for each service. The way I had things set up was to have each service in a separate file and then be included. See the "includedir" entry in the man page.
You don't say what service*S* you have this applied to.
ALL. It is a global configuration, in "/etc/xinetd.conf". I simply removed the comment mark in the line, which came from the distribution. If it comes with the distributed package, the line has to be correct, I should not need to read the documentation for that.
I do note that the man page says
<quote> The configuration file may also contain a single defaults entry that has the form
defaults { <attribute> = <value> <value> ... ... }
Well, it is inside the defaults section: defaults { # The next two items are intended to be a quick access place to # temporarily enable or disable services. # # enabled = # disabled = # Previous default in SUSE - please don't forget to use the logrotate. The # sample configuration is in /usr/share/packages/doc/xinetd/logrotate log_type = FILE /var/log/xinetd.log ... } includedir /etc/xinetd.d -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 01/03/14 10:27 AM, Carlos E. R. wrote:
I should not need to read the documentation
After all, you've years of experience... -- Ah well! I am their leader, I really ought to follow them! - Alexandre Auguste Ledru-Rollin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-03-01 18:23, Anton Aylward wrote:
On 01/03/14 10:27 AM, Carlos E. R. wrote:
I should not need to read the documentation
After all, you've years of experience...
It is not that. It is an entry that already exists in the config file supplied by the distribution. I assume that the packager, or the developer, has written in the config file entries that are correct, I should not need to verify them. And in fact, that entry worked previously. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
participants (4)
-
Anton Aylward -
Carlos E. R. -
Carlos E. R. -
Cristian Rodríguez