Op 24 okt. 2012 21:56 schreef David Rosenstrauch dar...@darose.net het
volgende:
On 10/24/2012 11:39 AM, Karol Blazewicz wrote:
On Wed, Oct 24, 2012 at 5:34 PM, David Rosenstrauch dar...@darose.net
wrote:
It looks like some recent package update broke logging on my machine,
and
nothing has
On 10/25/2012 08:03 AM, Guus Snijders wrote:
It can really help to pay attention to the output of pacman during updates
;-).
(it's also in pacman's log,btw).
mvg, Guus
I usually do. Not always easy to spot, though, when you upgrade a whole
bunch of packages at once.
DR
It looks like some recent package update broke logging on my machine, and
nothing has been written to my system logs since 10/21:
[darose@daroselin log]$ ls -l messages.log* syslog.log* daemon.log*
everything.log*
-rw-r- 1 root log 0 Oct 22 11:39 daemon.log
-rw-r- 1 root log 612714
On Wed, Oct 24, 2012 at 5:34 PM, David Rosenstrauch dar...@darose.net wrote:
It looks like some recent package update broke logging on my machine, and
nothing has been written to my system logs since 10/21:
Anyone have any idea what broke / how to fix?
If you're not running systemd, maybe it's
On 10/24/2012 11:39 AM, Karol Blazewicz wrote:
On Wed, Oct 24, 2012 at 5:34 PM, David Rosenstrauch dar...@darose.net wrote:
It looks like some recent package update broke logging on my machine, and
nothing has been written to my system logs since 10/21:
Anyone have any idea what broke / how to
5 matches
Mail list logo
