14.05.2019 16:39, Ulrich Windl пишет:
> Hi!
>
> Developing my first systemd service I have some problems I don't understand:
> After installation, I get this status:
> # systemctl status iotwatch.target ● iotwatch.target - iotwatch I/O
> performance monitor
>Loaded: loaded
>>> Lennart Poettering schrieb am 13.05.2019 um 09:45
in
Nachricht <20190513074503.GB9036@gardel-login>:
> On Mo, 13.05.19 09:18, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de)
wrote:
>
> Please guys, stop it.
>
>> > cpuid has *nothing* to do with /proc/cpuinfo
>> >
>> >
>>> Andrei Borzenkov schrieb am 14.05.2019 um 08:40 in
Nachricht
:
> On Tue, May 14, 2019 at 9:35 AM Ulrich Windl
> wrote:
>
>>
>> I knew that. It doesn't answer _why_ /var/run is obsolete.
>>
>
> /var/run needs /var which is not guaranteed to be there when you need
> it which complicates
On Di, 14.05.19 08:03, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) wrote:
> >> > cpuid has *nothing* to do with /proc/cpuinfo
> >> >
> >> > https://en.wikipedia.org/wiki/CPUID
> >> > The CPUID instruction (identified by a CPUID opcode) is a processor
> >> > supplementary instruction
> >>
>
Am Thu, 9 May 2019 11:49:24 +0200
schrieb Olaf Hering :
> With systemd-networkd it is apparently required to specify the MAC in the
> configuration. As a result, such configuration is per host and not generic
> anymore.
This is now https://github.com/systemd/systemd/issues/12558, so it does
On Di, 14.05.19 08:01, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) wrote:
> > systemd matches these UNIX semantics closely: we output error messages
> > exactly the same way as everything else on UNIX: a brief string
> > explaining what was attempted, followed by a colon, followed by a
> >
On Di, 14.05.19 11:02, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) wrote:
> > $ find /i/dont/exist
> > find: ‘/i/dont/exist’: No such file or directory
>
> I was talking about this:
> v04:~> find /var -name no-such-file 2>&1 | grep -v ': Permission denied'
>
> it outputs nothing if
Hello all,
Ulrich Windl [2019-05-14 8:35 +0200]:
> I knew that. It doesn't answer _why_ /var/run is obsolete.
The short reason is that /var can be on a separate partition, so it's not
available during early mount or late shutdown, or in a rescue environment with
only the root fs mounted. Some
On Di, 14.05.19 08:35, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) wrote:
> >>> Reindl Harald schrieb am 13.05.2019 um 08:25 in
> Nachricht <19612492-4b1e-0d87-5360-a67893873...@thelounge.net>:
>
> >
> > Am 13.05.19 um 08:20 schrieb Ulrich Windl:
> >>> Note that "/var/run" is a legacy alias
>>> Lennart Poettering schrieb am 14.05.2019 um 10:55
in
Nachricht <20190514085558.GD21579@gardel-login>:
> On Di, 14.05.19 08:01, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de)
> wrote:
>
>> > systemd matches these UNIX semantics closely: we output error messages
>> > exactly the same way as
>>> Lennart Poettering schrieb am 13.05.2019 um 09:46
in
Nachricht <20190513074653.GC9036@gardel-login>:
> On Mo, 13.05.19 07:48, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de)
wrote:
>
>> >> I guess it's not a file named "Reason" that's missing. Despite of my
>> >> recommendation to create
>>> František Šumšal schrieb am 13.05.2019 um 17:13 in
Nachricht <064ac942-a4d7-b547-0705-22f3262f5...@sumsal.cz>:
> On 5/13/19 8:20 AM, Ulrich Windl wrote:
>
>>> "systemd‑analyze verify" exists. Since a long long time.
>>
>> Not really: You can't verify a unit file while it's not "installed".
>>> Reindl Harald schrieb am 13.05.2019 um 08:25 in
Nachricht <19612492-4b1e-0d87-5360-a67893873...@thelounge.net>:
>
> Am 13.05.19 um 08:20 schrieb Ulrich Windl:
>>> Note that "/var/run" is a legacy alias for "/run". It's highly
>>> recommended not to use the former anymore.
>>
>> It it
>>> Lennart Poettering schrieb am 13.05.2019 um 09:35
in
Nachricht <20190513073539.GA9036@gardel-login>:
> On Mo, 13.05.19 08:25, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de)
wrote:
>
>> >> Whenever I try to enable or disable a target (that exists), I get
>> >> "Failed to execute operation:
On Tue, May 14, 2019 at 9:35 AM Ulrich Windl
wrote:
>
> I knew that. It doesn't answer _why_ /var/run is obsolete.
>
/var/run needs /var which is not guaranteed to be there when you need
it which complicates things.
___
systemd-devel mailing list
> The point I was trying to make was: "CPUID" and the model-specific registers
> (thus the name) depend very much on the CPU being used. While the kernel makes
> grat efforts to get things right, I wondered whether it's the best idea
> whether
> to repeat that effort in an application program.
On Tue, May 14, 2019 at 10:24 AM Ulrich Windl <
ulrich.wi...@rz.uni-regensburg.de> wrote:
> >>> Andrei Borzenkov schrieb am 14.05.2019 um 08:40
> in
> Nachricht
> :
> > On Tue, May 14, 2019 at 9:35 AM Ulrich Windl
> > wrote:
> >
> >>
> >> I knew that. It doesn't answer _why_ /var/run is
On Di, 14.05.19 09:23, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) wrote:
> > /var/run needs /var which is not guaranteed to be there when you need
> > it which complicates things.
>
> Thanks,
>
> I'll start a new thread on this (I wanted to ask anyway):
> AFAIK systemd does socket
>>> Lennart Poettering schrieb am 14.05.2019 um 16:15
in
Nachricht <20190514141520.GA22136@gardel-login>:
> On Di, 14.05.19 16:07, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de)
wrote:
>
>> Hmm, like this:?
>> > systemd‑analyze verify /run/systemd/generator.late/iotwatch.target
>> Failed to
Il giorno lun 13 mag 2019 alle ore 10:00 Lennart Poettering
ha scritto:
> Note that it only works correctly on desktops that support it.
Thank you for your reply. Why does it work only on desktop
environments that support it? I believed that it provides idle infos
to the D.E. not viceversa
On Di, 14.05.19 11:32, Germano Massullo (germano.massu...@gmail.com) wrote:
> Il giorno lun 13 mag 2019 alle ore 10:00 Lennart Poettering
> ha scritto:
> > Note that it only works correctly on desktops that support it.
>
> Thank you for your reply. Why does it work only on desktop
> environments
Hi!
Developing my first systemd service I have some problems I don't understand:
After installation, I get this status:
# systemctl status iotwatch.target ● iotwatch.target - iotwatch I/O
performance monitor
Loaded: loaded (/run/systemd/generator.late/iotwatch.target; bad; vendor
On 5/14/19 8:39 AM, Ulrich Windl wrote:
František Šumšal schrieb am 13.05.2019 um 17:13 in
> Nachricht <064ac942-a4d7-b547-0705-22f3262f5...@sumsal.cz>:
>> On 5/13/19 8:20 AM, Ulrich Windl wrote:
>>
>> That's actually not true. The argument for `systemd-analyze verify` is a
>> file name,
>>
>>> František Šumšal schrieb am 14.05.2019 um 15:46 in
Nachricht :
> On 5/14/19 8:39 AM, Ulrich Windl wrote:
> František Šumšal schrieb am 13.05.2019 um 17:13
in
>> Nachricht <064ac942-a4d7-b547-0705-22f3262f5...@sumsal.cz>:
>>> On 5/13/19 8:20 AM, Ulrich Windl wrote:
>>>
>>> That's actually
On Di, 14.05.19 16:07, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) wrote:
> Hmm, like this:?
> > systemd-analyze verify /run/systemd/generator.late/iotwatch.target
> Failed to open /dev/tty0: Permission denied
This is mostly a cosmetical message you can safely ignore. Moreover this has
On Mo, 13.05.19 16:58, Thadeu Lima de Souza Cascardo (casca...@canonical.com)
wrote:
> When we read from keyring, a temporary buffer is allocated in order to
> determine the size needed for the entire data. However, when zeroing that
> area,
> we use the data size returned by the read instead
26 matches
Mail list logo
