On Mon, 2 Dec 2019 at 10:26, Pascal via arch-general
wrote:
>
> hello,
> when I use journalctl to track system events, I introduce line breaks for
> better readability.
> like multitail, I would like to introduce more verbose line breaks...
> I wrote these few lines but it doesn't work as expected
Hi Pascal,
> exec 6<&0
> exec 0< <( while :; do read -sn1 k; echo $'\n'"# $( date +%H:%M:%S )
> ---"$'\n'; done )
> journalctl -f
> exec 0<&6 6<&-
>
> the second instruction "exec 0< <( while..." played alone works perfectly
> in my terminal, but not as a re
Hi Jens, *,
Am 23.06.19 um 13:05 schrieb Jens John:
> On Sun, 23 Jun 2019, at 00:22, Friedrich Strohmaier wrote:
>> Anyone around who knows or did this already?
[..]
> Going by these facts, it seems like there is no way to archieve what you
> want just with journalctl.
Thats definitly not wha
On Sun, 23 Jun 2019, at 00:22, Friedrich Strohmaier wrote:
> Anyone around who knows or did this already?
>From casually scimming the journalctl source code, unless I've overlooked
>something, it seems like only journalctl handles the presentation of the
>data in the specified OutputMode which
On 8 February 2014 12:06, Janna Martl wrote:
>
> On Thu, Feb 6, 2014 at 1:03 AM, Sébastien Leblanc
> wrote:
>
> > Conclusion (as I understand it):
> >
> > 1. There is definitely a bug in Journalctl: it crashes (segfaults) on I/O
> > errors.
> >
> > 2. You have a drive that is failing, or your BIO
On Thu, Feb 6, 2014 at 1:03 AM, Sébastien Leblanc wrote:
> Conclusion (as I understand it):
>
> 1. There is definitely a bug in Journalctl: it crashes (segfaults) on I/O
> errors.
>
> 2. You have a drive that is failing, or your BIOS might not be set
> correctly.
>
Thanks, all, for the analysis.
Hi
I agree on both points.
On Wed, Feb 5, 2014 at 10:03 PM, Sébastien Leblanc
wrote:
> Conclusion (as I understand it):
>
> 1. There is definitely a bug in Journalctl: it crashes (segfaults) on I/O
> errors.
A few months ago I had a problem with btrfs. I set +C attribute
(disable copy-on-write)
Conclusion (as I understand it):
1. There is definitely a bug in Journalctl: it crashes (segfaults) on I/O
errors.
2. You have a drive that is failing, or your BIOS might not be set
correctly. This is causing the I/O errors. How large is the drive? You
might have to turn off settings such as "SAT
On Tue, Feb 4, 2014 at 7:33 AM, Janna Martl wrote:
> On Mon, Feb 3, 2014 at 5:48 AM, Martti Kühne wrote:
>>Mind sharing the coredump so we could have a look? :)
>
> Here's a backtrace, in case that helps:
>
> (gdb) bt full
> #0 journal_file_move_to_object (f=f@entry=0x969cbc0, type=type@entry=3,
On Mon, Feb 3, 2014 at 5:48 AM, Martti Kühne wrote:
>Mind sharing the coredump so we could have a look? :)
Here's a backtrace, in case that helps:
(gdb) bt full
#0 journal_file_move_to_object (f=f@entry=0x969cbc0, type=type@entry=3,
offset=2638264, ret=ret@entry=0xbfc6505c) at src/journal/journ
On Thu, Jan 30, 2014 at 7:28 PM, Janna Martl wrote:
>>> You are able to read all the journald files, aren't you? You are running
>>> cp -r so it looks like so.
>>
>> IO errors can also cause a process to hang, and enter the dreaded "D"
>> state.
>
>
> It varies. Sometimes it hangs as a D-state pro
>> You are able to read all the journald files, aren't you? You are running
>> cp -r so it looks like so.
>
> IO errors can also cause a process to hang, and enter the dreaded "D"
> state.
It varies. Sometimes it hangs as a D-state process; sometimes it
explicitly says 'segmentation fault' and ot
On Thu, 30 Jan 2014 01:11:54 -0500
Janna Martl wrote:
> A couple months ago, I started getting I/O errors (see below) whenever
> I tried to do journalctl -n X for sufficiently large X (and journalctl
> would segfault). I assumed my hard drive was going to die, but in the
> mean time this was anno
Am 30.01.2014 11:46, schrieb Nowaker:
> If it's possible to read the file,
> journalctl should not segfault IMO, so it should be OK to file an issue.
No program should ever segfault. Unexpected input or errors must be
handled properly.
signature.asc
Description: OpenPGP digital signature
On Thursday 30 Jan 2014 11:46:38 Nowaker wrote:
> > A couple months ago, I started getting I/O errors (see below)
whenever
> > I tried to do journalctl
>
> You are able to read all the journald files, aren't you? You are running
> cp -r so it looks like so. `cp` would die with non-zero exit statu
A couple months ago, I started getting I/O errors (see below) whenever
I tried to do journalctl
You are able to read all the journald files, aren't you? You are running
cp -r so it looks like so. `cp` would die with non-zero exit status if
there were read errors I guess. If it's possible to re
On Tuesday 23 Apr 2013 15:14:41 Thomas Bächler wrote:
> Am 23.04.2013 15:08, schrieb Paul Gideon Dann:
> > Hello all,
> >
> > This should have been easy to find, but I haven't had any luck. What's
> > the
> > systemd equivalent to "tail -f /var/log/kernel.log"? I'm trying to slowly
> > start usi
Am 23.04.2013 15:08, schrieb Paul Gideon Dann:
> Hello all,
>
> This should have been easy to find, but I haven't had any luck. What's the
> systemd equivalent to "tail -f /var/log/kernel.log"? I'm trying to slowly
> start using journalctl instead of syslog...
journalctl -f _TRANSPORT=kernel
On Tue, Sep 4, 2012 at 9:24 PM, DR wrote:
> On Wed, 29 Aug 2012 16:32:04 +0800, Aurko Roy wrote:
>
> Hi,
>>I have been getting the following error whenever I try to run
>> journalctl:
>>
>> Assertion 'size > 0' failed at src/journal/mmap-cache.c:615, function
>> mmap_cache_get(). Aborting.
On Wed, 29 Aug 2012 16:32:04 +0800, Aurko Roy wrote:
Hi,
I have been getting the following error whenever I try to run
journalctl:
Assertion 'size > 0' failed at src/journal/mmap-cache.c:615, function
mmap_cache_get(). Aborting.
zsh: abort journalctl
Initially I thought it had some
20 matches
Mail list logo
