previously on this list Helmut Grohne contributed:
> > It's just occurred to me that the binary format may not work with append
> > only logging?
>
> That's true for the journal. When the journal opens its binary log, it
> flags the file as being opened, but what is the issue with not being
> a
On Tue, Feb 18, 2014 at 08:05:12PM +, Kevin Chadwick wrote:
> It's just occurred to me that the binary format may not work with append
> only logging?
That's true for the journal. When the journal opens its binary log, it
flags the file as being opened, but what is the issue with not being
app
previously on this list Helmut Grohne contributed:
> So for the time being (i.e. until all of my systems and recovery systems
> are converted to systemd), I do see a slight[2] disadvantage
> It may take even longer until all initramfs will use
> systemd (and I do want to read logs from the initra
On 02/18/2014 10:03 AM, Helmut Grohne wrote:
> Thanks. Unlike tools like xz, just installing systemd does have
> side-effects on the system. These are usually considered bugs and
> quickly ironed out, but I believe some are still present in the wheezy
> package and I am thus reluctant to install wh
On Sun, Feb 16, 2014 at 02:18:08PM +0100, Michael Biebl wrote:
> > For the record: If the recovery system does run systemd, you go
> > journalctl -D /path/to/your/journal/copy.
>
> Small correction here: The recovery system needs to have systemd
> *installed*, not running. All you need is the jour
]] The Wanderer
> (And now I wait for someone to point out an obvious specialized format
> and/or tool that everyone uses that I've overlooked...)
.deb files? :-)
--
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are
--
To UNSUBSCRIBE, email to debian-devel-req
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/16/2014 10:00 AM, Philipp Matthias Hahn wrote:
> Hello,
>
> On Sun, Feb 16, 2014 at 09:17:46AM +0100, Helmut Grohne wrote:
>> There is no journalctl on that system. So what do I do now?
>
> The same you do when your log file has those .Z, .
On Sun, 2014-02-16 at 16:45 +0100, Matthias Urlichs wrote:
> Hi,
>
> The Wanderer:
> > What is the log flow here? Specifically, does the logged information
> > flow from source - that is, from the process generating the message
> > which gets logged - to journald and also, separately, from source
Hi,
The Wanderer:
> What is the log flow here? Specifically, does the logged information
> flow from source - that is, from the process generating the message
> which gets logged - to journald and also, separately, from source to
> syslog (presumably in the form of rsyslogd), or does it flow from
Hello,
On Sun, Feb 16, 2014 at 09:17:46AM +0100, Helmut Grohne wrote:
> Heh. Maybe we can turn this into a useful question:
...
> There is no journalctl on that system. So what do I do now?
The same you do when your log file has those .Z, .gz, .bz2, .lzma, .xz,
.pgp, "your compresion program of t
On Sun, Feb 16, 2014 at 09:17:46AM +0100, Helmut Grohne wrote:
> Heh. Maybe we can turn this into a useful question:
>
> Assume that I have a broken system (maybe the disk is partially broken
> or it got owned and I don't want to rely on its toolbox anymore). Now
> for some reason, I can still acce
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/16/2014 08:18 AM, Michael Biebl wrote:
> With my rsyslog (and systemd maintainer) hat on, let me add a few
> remarks here:
>
> We still do install rsyslog by default and will continue to do so for
> the forseeable future (for reasons like the
> On Wed, Feb 12, 2014 at 02:53:39PM +0400, Oleg wrote:
>> scp /var/log/syslog ...
>>
>> Why do i need an unneeded layer for this - journalctl?
>
> Heh. Maybe we can turn this into a useful question:
>
> Assume that I have a broken system (maybe the disk is partially broken
> or it got owned and
13 matches
Mail list logo
