On 21/04/2020 19:35, Anders Buch wrote:
> Hello,
>
> Are there any plans to update the pypi version of python-sytemd here:
> https://pypi.org/project/systemd-python/
>
> The following results in errors on Ubuntu 18.04 with latest python3.8
> packages installed (as well as libsystemd-dev and pytho
Hello,
Are there any plans to update the pypi version of python-sytemd here:
https://pypi.org/project/systemd-python/
The following results in errors on Ubuntu 18.04 with latest python3.8
packages installed (as well as libsystemd-dev and python3-systemd):
python3.8 -m venv systemd_test
. systemd
On Di, 21.04.20 20:52, Amit anand ([email protected]) wrote:
> Apr 21 16:27:16 [xxx] valgrind[4252]: valgrind: m_ume.c: can't open
> interpreter
There's something not right with the ELF interpretor in your
binaries. maybe some cross-building fuck-up? It's probably best to
ping the valgrind com
Hi,
Tried to run debug-symbol enabled systemd-udevd through valgrind.
root@[xxx]:/var/opt# vi /etc/systemd/system/.../systemd-udevd.service
ExecStart=/usr/bin/valgrind --tool=memcheck
/lib/systemd/.debug/systemd-udevd // Modified to run debug-symbol enabled
systemd.udevd binary through valgrind.
Am Dienstag, den 21.04.2020, 14:33 + schrieb Wieschke, Thomas:
> Hi,
> thanks fort he quick response. After having a first look at the man pages, I
> mentioned that I would have a choice between
> a fstab based solution or a unit file based one, right?
> Because I have a mix of ~ 10 different
Hi,
thanks fort he quick response. After having a first look at the man pages, I
mentioned that I would have a choice between
a fstab based solution or a unit file based one, right?
Because I have a mix of ~ 10 different Mounts (CIFS, NFS) /workdir/in,
/workdir/out, /workdir/bla, /workdir/send .
Am 21.04.20 um 15:26 Uhr schrieb Wieschke, Thomas:
> I'm writing on a RH 7 system to an automounted FS and get an disruption
> because systemd (??) is,
> besides working in this directory, obviously trying an umount in the
> background.
> The umount doesn't work because the FS is in use (returned
On Di, 21.04.20 13:26, Wieschke, Thomas ([email protected]) wrote:
>
> Hi,
> I hope someone can help with the following case.
>
> I'm writing on a RH 7 system to an automounted FS and get an disruption
> because systemd (??) is,
> besides working in this directory, obviously trying an um
>>> Silvio Knizek schrieb am 21.04.2020 um 15:45 in
Nachricht
<24197_1587476741_5E9EF905_24197_143_1_61f65bea728c37e386b1212f4f282aefc193ab0c.
[email protected]>:
> Am Dienstag, den 21.04.2020, 13:26 + schrieb Wieschke, Thomas:
>> Hi,
>> I hope someone can help with the following case.
>>
>> I'm wr
Am Dienstag, den 21.04.2020, 13:26 + schrieb Wieschke, Thomas:
> Hi,
> I hope someone can help with the following case.
>
> I'm writing on a RH 7 system to an automounted FS and get an disruption
> because systemd (??) is,
> besides working in this directory, obviously trying an umount in the
Hi,
I hope someone can help with the following case.
I'm writing on a RH 7 system to an automounted FS and get an disruption because
systemd (??) is,
besides working in this directory, obviously trying an umount in the background.
The umount doesn't work because the FS is in use (returned busy),
On Di, 21.04.20 19:54, www ([email protected]) wrote:
> hi Lennart,
>
>
> I mean the DBUS property.
>
> root@demoboard:/# busctl set-property org.freedesktop.DBus
> /org/freedesktop/DBus org.freedesktop.DBus Features as 1 x
>
> Cannot set read-only property -- the default
>
>
>
>
> roo
hi Lennart,
I mean the DBUS property.
root@demoboard:/# busctl set-property org.freedesktop.DBus
/org/freedesktop/DBus org.freedesktop.DBus Features as 1 x
Cannot set read-only property -- the default
root@demoboard:/# busctl set-property com.sugon.sensors.DISCRETE
/com/sugon/sens
>>> "Ulrich Windl" schrieb am 21.04.2020
um
10:31 in Nachricht <[email protected]>:
Damian Ivanov schrieb am 20.04.2020 um 17:30
in
> Nachricht
>
<20744_1587396582_5E9DBFE6_20744_10_1_CAPVS_cc7s7ZUhvy3HcfKWST+0F3DUrdFB7fKK9
> tre
> [email protected]>:
>>
Seems not, ctr + ] worked.
And when using nano all the ctrl keys are also marked as ^key
On Tue, Apr 21, 2020 at 11:31 AM Ulrich Windl
wrote:
>
> >>> Damian Ivanov schrieb am 20.04.2020 um 17:30 in
> Nachricht
> <20744_1587396582_5E9DBFE6_20744_10_1_CAPVS_cc7s7ZUhvy3HcfKWST+0F3DUrdFB7fKK9tre
> p_
>>> Damian Ivanov schrieb am 20.04.2020 um 17:30 in
Nachricht
<20744_1587396582_5E9DBFE6_20744_10_1_CAPVS_cc7s7ZUhvy3HcfKWST+0F3DUrdFB7fKK9tre
[email protected]>:
> Hello!
>
> Please enlighten me: which key is ^]
Isn't it Escape (ESC)?
>
> Br,
> Damian
> _
Hi,
After bootstrapping os and mariadb into $DIR
I booted the machine with:
systemd-nspawn -D $DIR -b --resolv-conf=bind-host --capability=all
I had to remove $DIR/etc/resolv.conf first as bind-host seems to fail
if $DIR/etc/resolv.conf already exists.
mariadb.service was failing, after looking
17 matches
Mail list logo
