On Tuesday 04 May 2010 09:56:29 Peter Czanik wrote:
Hello,
2010-05-04 09:19 keltezéssel, Andreas Jaeger írta:
Btw. the following packages are still using /var/run (in the last published
factory): [...]
syslog-ng
[...]
Some of these might be fixed already but not yet checked into factory,
What needs to be fixed here? I did not follow this discussion, as many posts were emotional rather than technical... I can take care for syslog-ng, if I know, what I need to fix :-)
http://lizards.opensuse.org/2010/05/03/preparation-for-mounting-varrun-as- tmpfs/
Currently syslog-ng has its pid and ctl file in /var/run, which definitely could stay.
Yes, no problem with that.
There is also a file for additional log sockets generated /etc/init.d/syslogd on each invocation, which is under the directory /var/run/syslog-ng (as discussed with mt). This could me more of a problem. Possible solutions:
- move /var/run/syslog-ng to somwhere else. Where? This would involve changing the following packages: syslogd, syslog-ng and apparmor-profiles.
Do this only if you have data that needs to survive a reboot.
- remove the /var/run/syslog-ng directory from the syslog-ng package and create it dynamically by /etc/init.d/syslogd
Yes.
Both solutions have advantages and disadvantages. Rsyslog has the exact same problem, so should be solved the same way. Which one should be chosen?
Create it if it does not exist, Andreas -- Andreas Jaeger, Program Manager openSUSE, aj@{novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126