Dear everyone,
TL;DR: It appears that a systemd unit containing
ProtectSystem=full
SystemCallFilter=~@mount
ReadWritePaths=-/boot/EFI
and launched on a system where /boot is initially mounted ro, keeps
thinking /boot is read-only even after it has been remounted rw; it is
necessary for the
(if online) and if it fails just wait and
retry or so? Any idea if it's fixed in newer version of systemd?
Thanks and BR,
marek
--
as simple and primitive as possible
-
Marek Belisko - OPEN-NANDRA
Freelance Developer
Ruska Nova Ves 219 | Pre
Hi,
I have a case when a board boots without network connection but RTC
have the correct date/time. Does systemd use RTC date/time to set
systemd time or it needs to be done manually?
Thanks and regards,
marek
--
as simple and primitive as possible
to connect to
port 19532: No route to host
but I'm able to ping server from client side and also
netstat -tulpn shows:
tcp6 0 0 :::19532:::*
LISTEN 1/systemd
but not on tcp only tcp6
Any ideas what should I check?
Thanks and regards,
marek
--
as simple
also
checked code with debug and cannot see any crash (strecktrace etc.)
Any ideas what I should look for and how to debug this issue?
Thanks and BR,
marek
--
as simple and primitive as possible
-
Marek Belisko - OPEN-NANDRA
Freelance Developer
On Thu, Oct 22, 2020 at 12:57 PM Lennart Poettering
wrote:
>
> On Do, 22.10.20 11:53, Belisko Marek (marek.beli...@gmail.com) wrote:
>
> > > Hmm? this service has nothing to do with epoch/clock setting. It's
> > > used for systems that have a "reboot-for-update
On Thu, Oct 22, 2020 at 11:51 AM Lennart Poettering
wrote:
>
> On Do, 22.10.20 11:47, Belisko Marek (marek.beli...@gmail.com) wrote:
>
> > On Thu, Oct 22, 2020 at 10:52 AM Lennart Poettering
> > wrote:
> > >
> > > On Mi, 21.10.20 22:13, Belisk
On Thu, Oct 22, 2020 at 10:52 AM Lennart Poettering
wrote:
>
> On Mi, 21.10.20 22:13, Belisko Marek (marek.beli...@gmail.com) wrote:
>
> > Hi,
> >
> > I'm facing a strange issue. When I boot system using systemd (244.3)
> > and in one service I'm generating
On Thu, Oct 22, 2020 at 7:58 AM Tomasz Torcz wrote:
>
> On Wed, Oct 21, 2020 at 10:13:10PM +0200, Belisko Marek wrote:
> > Hi,
> >
> > I'm facing a strange issue. When I boot system using systemd (244.3)
> > and in one service I'm generating some certificates. When
certificates but I have only issues that some files are
created and I'm getting date/time creation also epoch. Shouldn't it be
the date/time of build? Can this be caused somehow by using read only
rootfs? Thanks a lot for any pointers.
BR,
marek
--
as simple and primitive as possible
l/1848 but this part is already
included in the systemd we're using (v234) and it's about persistent
logging. Any ideas on what we can check or what can cause this
behavior?
Thanks and BR,
marek
--
as simple and primitive as possible
-
Marek Belisko - O
systemd enable sshd.socket but systemd
cannot see ssh.service. Is there some other way to create a link to an
existing socket file? Thanks
BR,
marek
--
as simple and primitive as possible
-
Marek Belisko - OPEN-NANDRA
Freelance Developer
Ruska
On Mon, Jan 13, 2020 at 12:59 PM Ulrich Windl
wrote:
>
> >>> Belisko Marek schrieb am 13.01.2020 um 10:19 in
> Nachricht
> :
> > Hi,
> >
> > I have embedded system which contains fat32 partition at the end of
> > partition table. I
and reformat it. Is there some simple way to
detect that condition? Thanks for any pointers.
BR,
marek
--
as simple and primitive as possible
-
Marek Belisko - OPEN-NANDRA
Freelance Developer
Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421
On Thu, Nov 21, 2019 at 7:25 AM Chris Murphy wrote:
>
> On Tue, Nov 12, 2019 at 3:52 AM Belisko Marek wrote:
> >
> > On Mon, Nov 11, 2019 at 4:47 PM Lennart Poettering
> > wrote:
> > >
> > > On Mo, 11.11.19 13:33, Belisko Marek (marek.beli...@gma
Hi Andrei,
On Sat, Nov 16, 2019 at 9:31 AM Andrei Borzenkov wrote:
>
> 12.11.2019 13:52, Belisko Marek пишет:
> > On Mon, Nov 11, 2019 at 4:47 PM Lennart Poettering
> > wrote:
> >>
> >> On Mo, 11.11.19 13:33, Belisko Marek (marek.beli...@gmail.
On Mon, Nov 11, 2019 at 4:47 PM Lennart Poettering
wrote:
>
> On Mo, 11.11.19 13:33, Belisko Marek (marek.beli...@gmail.com) wrote:
> 65;5802;1c
> > Hi,
> >
> > I'm using systemd 234 (build by yocto) and I've setup automount of
> > sdcard in fstab. This works per
boot. Reading manual it should be enough to set
passno (6th column in fstab) to anything higher then 0. I set ti to 2
but inspecting logs it doesn't seems fsck is performed. Am I still
missing something? Thanks.
BR,
marek
--
as simple and primitive as possible
On Mon, Jul 1, 2019 at 9:48 AM Lennart Poettering
wrote:
>
> On Mo, 01.07.19 08:25, Belisko Marek (marek.beli...@gmail.com) wrote:
>
> > Hi,
> >
> > I'm working on rpi3 by using mender OTA system and for identifying
> > devices I would like to have f
:01 321 systemd-hostnamed[336]: Failed
to write static host name: Read-only file system
Jul 03 17:26:01 321 systemd-resolved[135]: System hostname changed to '321'.
while / and /data are both rw.
Any ideas how to overcome this problem? Thanks.
BR,
marek
--
as simple and primitive as possi
s up?
Thanks.
[1] - https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
BR,
marek
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Time zone: Universal (UTC, +)
Network time on: yes
NTP synchronized: yes
RTC in local TZ: no
Is this known problem or there is some issue with my setup (I'm using
systemd-networkd + systemd-timesyncd services).
Thanks and BR,
marek
--
as simple and primitive as possible
On Fri, Dec 7, 2018 at 12:45 PM Belisko Marek wrote:
>
> On Fri, Dec 7, 2018 at 12:34 PM Lennart Poettering
> wrote:
> >
> > On Do, 06.12.18 22:58, Belisko Marek (marek.beli...@gmail.com) wrote:
> >
> > > [Unit]
> > > Description=D
On Fri, Dec 7, 2018 at 12:34 PM Lennart Poettering
wrote:
>
> On Do, 06.12.18 22:58, Belisko Marek (marek.beli...@gmail.com) wrote:
>
> > [Unit]
> > Description=Demo
> > After=systemd-user-sessions.service
> >
> > [Service]
> > ExecStart=-/usr/bi
Hi Tomasz,
On Fri, Dec 7, 2018 at 6:26 AM Tomasz Torcz wrote:
>
> On Thu, Dec 06, 2018 at 10:58:31PM +0100, Belisko Marek wrote:
> > Hi,
> >
> > I'm trying to run qt qml application on intel nuc but when booted from
> > hdd I'll get an eror when app is started:
&
Lennart Poettering píše v Pá 30. 11. 2018 v 18:16 +0100:
> On Fr, 30.11.18 17:04, Marek Howard (marek...@gmail.com) wrote:
> > I understand, but that's by design and there's nothing wrong with that.
> > It's even useful for the case where you want wrap a thing with a
> > scr
Lennart Poettering píše v Pá 30. 11. 2018 v 14:53 +0100:
> On Fr, 30.11.18 14:25, Marek Howard (marek...@gmail.com) wrote:
>
> > - Lennart keeps repeating that passing secrets via environment variable
> > is insecure because they are passed down the process tree. They are, if
Marek Howard píše v Pá 30. 11. 2018 v 14:25 +0100:
> Give me one solid reason why it's insecure to pass passwords via
> environment variables please. So far it seems that systemd just broke
> this concept for no valid reason and now you try to defend with
> completely unrelated reasons
David Parsley píše v St 14. 11. 2018 v 08:45 -0500:
>
> On Wed, Nov 14, 2018 at 3:43 AM Lennart Poettering
> wrote:
> > I mean, seriously, people do lots of stuff. It doesn't mean that all
> > what people do is actually a good idea or just safe.
>
> Certainly agreed on this point. It is my
Marek Howard píše v St 14. 11. 2018 v 01:35 +0100:
> Lennart Poettering píše v Út 13. 11. 2018 v 15:17 +0100:
> > On Di, 13.11.18 07:49, David Parsley (pars...@linuxjedi.org) wrote:
> > Well, you are of course welcome to ignore whatever I say, but again,
> > environ
Lennart Poettering píše v Út 13. 11. 2018 v 15:17 +0100:
> On Di, 13.11.18 07:49, David Parsley (pars...@linuxjedi.org) wrote:
>
> > I disagree; privacy of environment variables to individual users on the
> > system is as fundamental as Unix file permissions. If a privileged process
> > (systemd)
So many revealings in one reply! Thank you very much for explaining it
in basic terms to me.
Mantas Mikulėnas píše v Ne 04. 11. 2018 v 18:18 +0200:
> You should just put an entry in /etc/crypttab instead, and let
> systemd-cryptsetup handle it via the existing dependencies mechanism.
>
>
Hello.
I'm trying to unlock my LUKS (type luks2) encrypted backup drive via
udev rule /etc/udev/rules.d/99-unlock-backupdrive.rules:
ACTION=="add", SUBSYSTEM=="block", ENV{DEVTYPE}=="partition", \
ENV{ID_SERIAL}=="FZ133888", ENV{ID_PART_ENTRY_UUID}=="8c347a-02", \
On Wed, May 23, 2018 at 1:50 PM Mantas Mikulėnas <graw...@gmail.com> wrote:
> On Wed, May 23, 2018 at 2:37 PM Belisko Marek <marek.beli...@gmail.com>
wrote:
>> Hello,
>> I'm using system 234 build by yocto for BeagleBoneBlack. I ave some
strange
>> issue t
cause this issue?
Thanks and BR,
marek
--
as simple and primitive as possible
-
Marek Belisko - OPEN-NANDRA
Freelance Developer
Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web
Dnia środa, 9 sierpnia 2017 14:54:25 CEST piszesz:
> 2017-08-09 14:51 GMT+02:00 Marek Floriańczyk <marek.florianc...@gmail.com>:
> > Dnia środa, 9 sierpnia 2017 11:51:07 CEST Tilman Baumann pisze:
> >> On 09.08.2017 11:28, Tilman Baumann wrote:
> > NUT
everything to NUT would take more
time that I actually got for this.
Thank You all. I will try to write some simple binary, place it in
/lib/systemd/system-shutdown/
and test it.
Best Regards
Marek
> systemd-devel mailing list
> systemd-devel@lists.freedesktop.org
> https://lists.freedesk
> schedules the UPS poweroff.
Thanks for suggestion
I will stick to the approach suggested by Lennart it looks like a simple
solution to me, and the binary is called at the very late stage of shutdown
process after every databases and daemons are closed.
>
> On Wed, Aug 9, 2017, 12
Dnia środa, 9 sierpnia 2017 10:29:37 CEST Lennart Poettering pisze:
> On Di, 08.08.17 16:03, Marek Floriańczyk (marek.florianc...@gmail.com) wrote:
> > Hi all,
> >
> > I have a small device MicroUPS which helps me to shutdown my system on
> > embedded devices, it i
change my code.
Best Regards
Marek
>
> Normally services are given a certain amount of time to stop after SIGTERM
> (or whatever KillSignal was set, or whatever ExecStop command was
> specified). Even if microupsd doesn't handle SIGTERM nicely (which I'd call
> a bug), it's possible
Dnia wtorek, 8 sierpnia 2017 21:04:18 CEST Andrei Borzenkov pisze:
> 08.08.2017 17:03, Marek Floriańczyk пишет:
> > What would be the proper way to distinguish between system is going down
> > for reboot and for shutdown ?
>
> Straightforward way is to make your service Wan
going down for
reboot and for shutdown ?
Best Regards
Marek
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
/systemd/systemd/compare/master...systemd-mailing-devs:1461978784-6374-1-git-send-email-marex%40denx.de>
>
> https://github.com/systemd/systemd/pull/3159
>
Cool, thanks :)
--
Best regards,
Marek Vasut
___
systemd-devel mailing list
syste
Add nios2 architecture support. The nios2 is a softcore by Altera.
Signed-off-by: Marek Vasut <ma...@denx.de>
---
src/basic/architecture.c | 3 +++
src/basic/architecture.h | 4
2 files changed, 7 insertions(+)
diff --git a/src/basic/architecture.c b/src/basic/architecture.c
index a
2015 at 05:51:11PM +0100, Marek wrote:
>> those too :) but it's a rare situation.
>
> Programs are all about having to handle the "rare" situations properly.
>
> And you didn't say _why_ you care about this. Just iterate over all
> block devices and you should be fine if
thanks Robert, eample2 does list all disks but doens't differentiate
between ata and usb.
On Sun, Dec 6, 2015 at 10:49 AM, Robert Milasan <rmila...@suse.com> wrote:
> On Sun, 6 Dec 2015 01:49:41 +0100
> "Marek" <mlf.c...@gmail.com> wrote:
>
>>
>> ude
those too :) but it's a rare situation.
On Sun, Dec 6, 2015 at 5:48 PM, Greg KH <gre...@linuxfoundation.org> wrote:
> On Sun, Dec 06, 2015 at 05:38:37PM +0100, Marek wrote:
>> i'm trying to get only ata devices because my application requires i
>> only list disks that a
i'm trying to get only ata devices because my application requires i
only list disks that are sata drives
inside the computer.
On Sun, Dec 6, 2015 at 2:37 AM, Greg KH <gre...@linuxfoundation.org> wrote:
> On Sun, Dec 06, 2015 at 01:49:41AM +0100, Marek wrote:
>> >
>> /sys
>
/sys/
> And "ata" devices are not the same thing as a "usb" device is in any way
> or form, so the fact that they have to be shown differently is totally
> natural. You can iterate over them, you just have to find the correct
> class that the kernel uses for them ("ata_device"), but there is no
ed values, but changing "usb", "usb_device" to
ata and ata_device doesn't work and the program doesnt output
anything.
Marek
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Im trying to list ata devices in the same manner i am able to list usb devices.
On Fri, Nov 20, 2015 at 11:00 PM, Greg KH <gre...@linuxfoundation.org> wrote:
> On Fri, Nov 20, 2015 at 08:59:21PM +0100, Marek wrote:
>> hi,
>>
>> i'm using the following code:
>> h
* udev_device_get_parent_with_subsystem_devtype
(struct
udev_device *udev_device,
const char *subsystem,
const char *devtype);
Marek
Why shouldn't they matter? Can you clarify? Where does the kernel
provide these values? Are they documented
somewhere or is there a way to look them up?
On Wed, Nov 18, 2015 at 12:45 AM, Greg KH <gre...@linuxfoundation.org> wrote:
> On Wed, Nov 18, 2015 at 12:37:17AM +0100, Marek wro
53 matches
Mail list logo
