On 01/06/15 11:58, Andrei Borzenkov wrote:
В Tue, 06 Jan 2015 10:52:17 +0530
dE пишет:
Hi.
I dont have a better term.
When you look at the status of a unit or check the output of list-units,
there's a 'load/loaded' column/field also there's an active field/column.
What do these mean? I sus
On Tue, Jan 6, 2015 at 4:34 PM, Nikolai Zhubr wrote:
> Hi,
> 07.01.2015 0:59, me wrote:
> [...]
>>
>> Could someone please explain, what "StandardOutput=journal+console" is
>> supposed to do? Actully, it is not documented, just briefly mentioned in
>> documentation. Intuitively it would seem exact
Hi,
07.01.2015 0:59, me wrote:
[...]
Could someone please explain, what "StandardOutput=journal+console" is
supposed to do? Actully, it is not documented, just briefly mentioned in
documentation. Intuitively it would seem exactly what I want, and it is
even the default setting. Looking at the sou
Hi. It seems you missed my prev. letter. So, I am sending you the patch again.
Typo fix in README in libabc:
-Make your code safe for unexpected termination and any point:
+Make your code safe for unexpected termination at any point:
___
systemd-devel ma
Already fixed by Lennart.
Zbyszek
___
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Hi again,
06.01.2015 21:33, me wrote:
[...]
All messages in system-fsck are generated using log_error().
Now, how to get them also displayed to system console, at boot time?
I supposed "StandardOutput/StandardError=journal+console" option is
there exactly for that, but apparently log_error() onl
Hi again,
06.01.2015 19:46, Andrei Borzenkov wrote:
[...]
By executing "systemctl status systemd-fsck@..." as instructed? Or
journalctl ...
Ok, thanks, I've finally found the messages of my interest by using:
journalctl SYSLOG_IDENTIFIER=system-fsck
All messages in system-fsck are generated us
On Sun, Dec 28, 2014 at 07:18:16PM +0100, Gabriel de Perthuis wrote:
> Change the default through /etc/systemd/bootchart.conf.
> Keep the /sbin/init default in the source code, in case
> some users rely on that.
No, as a rule, all files in /etc installed by systemd can only
contain comments. Boot-w
Hi,
06.01.2015 19:46, Andrei Borzenkov:
[...]
In [email protected] I see "StandardOutput=journal+console", and
"StandardOutput" not set, AFAICS defaulting to "inherit" according to
Ops, correction, this was meant "StandardError" not set.
system config file, which looks good, as all diagnos
Hello all,
Michael Biebl [2015-01-05 10:51 +0100]:
> If a service fails to load, we skip fix_order() and the generator uses
> the static start priorities. This induces bogus orderings against
> unrelated services. So instead, just don't add a service to the
> all_services hash_map, if it fails to
В Tue, 06 Jan 2015 18:23:01 +0300
Nikolai Zhubr пишет:
> Hi again,
>
> Now a have another question.
>
> In [email protected] I see "StandardOutput=journal+console", and
> "StandardOutput" not set, AFAICS defaulting to "inherit" according to
> system config file, which looks good, as all d
Hi,
06.01.2015 17:42, Zbigniew Jędrzejewski-Szmek:
See "systemctl status 'systemd-fsck@dev-disk-by\x2duuid-729...ce'"
for details.
[DEPEND] Dependency failed for /sysroot.
How many disks do you have? I'm pretty sure that only one which matches
/dev/disk/by-uuid/*5-eaedc37c1852.
Here I have jus
Hi,
06.01.2015 18:07, Reindl Harald:
the main point was that it is *not* helpful to truncate outputs as
default regardsless screen width - even if someone is on a terminal with
only 80 chars you don't do him a favor - he is frustrated anyways by the
small screen and got more frustrated for the ad
On Monday 05 January 2015 at 18:32:35, Lennart Poettering wrote:
> On Thu, 25.12.14 23:38, Ivan Shapovalov ([email protected]) wrote:
>
> > Hi!
> >
> > Judging from commit a931ad47a8623163a29d898224d8a8c1177ffdaf,
> > the systemd user instance is intentionally restricted from touching
On Thu, Jan 01, 2015 at 11:15:47PM +0100, Jouke Witteveen wrote:
> On Thu, Jan 1, 2015 at 7:15 PM, Zbigniew Jędrzejewski-Szmek
> wrote:
> > On Tue, Dec 30, 2014 at 08:22:27PM +0100, Jouke Witteveen wrote:
> >> ---
> >>
> >> This fixes #87251
> >
> > This is actually important information that shou
Hi,
06.01.2015 18:04, Elias Probst:
The truncation should take the terminal width into account using
fd_columns(). It looks like in your case it fails to determine the
terminal width of your boot VT and therefore defaults to '80'.
Please try to verify this.
My terminal width is exactly 80, no
Hi again,
Now a have another question.
In [email protected] I see "StandardOutput=journal+console", and
"StandardOutput" not set, AFAICS defaulting to "inherit" according to
system config file, which looks good, as all diagnostic and error
messages coming from systemd-fsck (and they are q
Am 06.01.2015 um 16:04 schrieb Elias Probst:
On 01/06/2015 03:53 PM, Reindl Harald wrote:
Messages are truncated because there's only so much space on 80
column text displays, and filling the screeen with wrapped unit
names is not useful anyway. This is supposed to give you an overview
of what
On 01/06/2015 03:53 PM, Reindl Harald wrote:
>> Messages are truncated because there's only so much space on 80
>> column text displays, and filling the screeen with wrapped unit
>> names is not useful anyway. This is supposed to give you an overview
>> of what is happening. You can always view the
Am 06.01.2015 um 15:42 schrieb Zbigniew Jędrzejewski-Szmek:
On Tue, Jan 06, 2015 at 02:51:50PM +0300, Nikolai Zhubr wrote:
Hi people,
I'm now fighting with opensuse 13.2 failing to mount some or all
disks at boot, obviously resulting in unusable system. This
distribution is systemd-based, henc
On Tue, Jan 06, 2015 at 02:51:50PM +0300, Nikolai Zhubr wrote:
> Hi people,
>
> I'm now fighting with opensuse 13.2 failing to mount some or all
> disks at boot, obviously resulting in unusable system. This
> distribution is systemd-based, hence I'm here. While I haven't yet
> exactly understood m
Hi people,
I'm now fighting with opensuse 13.2 failing to mount some or all disks
at boot, obviously resulting in unusable system. This distribution is
systemd-based, hence I'm here. While I haven't yet exactly understood my
disks problem, one other thing is absolutely clear: systemd messages
22 matches
Mail list logo
