<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#333333" text="#cccccc"> On 03.12.2010 14:19, Marius Tolzmann wrote: <blockquote cite="mid:4CF8FC62.10809@molgen.mpg.de" type="cite"> hi.. i have configured a syslog.service which works well.. but the syslog.socket which activated systemd-kmsg-syslog.service is still active and running.. the socket does not activate the service anymore but it is still listed as listening.. </blockquote> The socket just creates the socket and programms can write to it... so it is kind of listening. If then later on syslog.service is started it ideally should just take the existing socket and read all messages written so far. So you get all the messages since the creation of the socket, but you do not have to bother starting the actual daemon in this early stage. <blockquote cite="mid:4CF8FC62.10809@molgen.mpg.de" type="cite"> how is this supposed to be configured correctly.. since i think i need the systemd-kmsg-syslog as long as my syslog.service ist not running and able to write its logfiles to the filesystem.. ?? </blockquote> If I understood correctly the kmsg-syslog thing just gets all the messages from kmsg and puts them into the syslog socket /dev/log but not sure about that. <blockquote cite="mid:4CF8FC62.10809@molgen.mpg.de" type="cite">but how do i get rid of this socket activated /dev/log handling and replace it with my syslog.service completely? </blockquote> Actually I think its not socket activated. It's just that the socket is created before starting the actual daemon. (socket activation would mean that the deamon is only started on traffic through that socket). In our case syslog.service is always started if multi-user.target is started. <blockquote cite="mid:4CF8FC62.10809@molgen.mpg.de" type="cite"> i am confused... ...again 8) thanks @all for the links to all the systemd unit repositories.. -> why is it that all *syslog*.service files are WantedBy multi-user.target and not let's say WantedBy basic.target? </blockquote> Well all the messages are cached in the socket. So no harm in starting it late! enaut </body> </html>