You are not logged in.
Pages: 1
Since the change of /var/lock /var/run to /run /run/lock a couple of key functions broke down. For me particularly munin stopped starting.
2012/07/28 16:25:02 Opened log file
2012/07/28 16:25:02 Creating lock /var/lock/munin-update.lock failed: Permission denied
2012/07/28 16:25:02 at /usr/share/perl5/vendor_perl/Munin/Master/Update.pm line 128.I just wonder what reasons there were to break a running system. As I understand that rolling releases do come with a hazard: not all running systems can be tested, I feel that the arch team got a bit ahead of themselves lately. I did spend hours to get and keep logitech media server running where virtually every update broke it and I'm fine with that as LMS is kind of a niche software. Munin on the other hand is not really niche. The change caused quite some havok if this forem counts for anything and it does.
So I wonder what were the reasons?
archlinux on a Gigabyte C1037UN-EU, 16GiB
a Promise PDC40718 based ZFS set
root on a Samsung SSD PB22-J
running LogitechMediaServer(-git), Samba, MiniDLNA, TOR
Offline
Not answering your question, but in case you have not seen: There is an ABS update to munin 2.0 since 2nd July that honours the change you refer to I think - https://projects.archlinux.org/svntogit … ages/munin
Offline
Pages: 1