You are not logged in.
I do not have a systemd archlinux. I was only following the new suggestions about initscripts.
However, at boot, I see a message error like this:
Error binding socket; addr='AF_UNIX(/run/systemd/journal/syslog)', error='No such file or directory (2)'
etc.
There is another post about this, but it is related to a systemd arch installation.
???
Last edited by hifi25nl (2012-10-21 10:38:41)
Offline
Edit your syslog-ng.conf.
unix-dgram("/dev/log");
Offline
Hi, I double checked that and IMHO in such a case a .pacnew file should've been created ?
I'm not a developer, but I just wanted to put my user opinion here.
IMHO an update should never break my config this way...
Personal website: reboot.li
GitHub: github.com/rebootl
Offline
Hi, I double checked that and IMHO in such a case a .pacnew file should've been created ?
I'm not a developer, but I just wanted to put my user opinion here.
IMHO an update should never break my config this way...
pacnew files are created according to the gospel in pacman's manpage.
Offline
I see (man pacman):
The current file is the same as the original but the new one differs. Since the user did not ever modify the file, and the new one may contain improvements or bugfixes, install the new file.
Makes sense.
Shame on me, for never reading or overseeing this...
Thanks for the pointer.
Last edited by rebootl (2012-10-21 18:30:03)
Personal website: reboot.li
GitHub: github.com/rebootl
Offline
Thank you for the suggestion. However I have switched to systemd and all is working very well.
Offline
Edit your syslog-ng.conf.
unix-dgram("/dev/log");
I had also the same problem. It has been resolved by editing syslog-ng.conf as described above!
Last edited by nitralime (2012-11-01 12:42:35)
Offline
Same for me : many thanks indeed !!! :-)
Offline
I got bit by this on a recent upgrade of an installation made in October. I am completely confused. I didn't get a .pacnew file, yet the conf file had never been changed from the install and had the wrong line in it.
What am I missing here? It was only by finding this thread that I could fix my system.
Offline
I had the same thing. Seems quite bad it breaks without any means of intervention during update.
Offline
works for me. thank you!
Edit your syslog-ng.conf.
unix-dgram("/dev/log");
Offline
Edit your syslog-ng.conf.
unix-dgram("/dev/log");
Thank you so much, it worked for me as well
Offline