On Mon, 3 Oct 2022 07:20:44 +0200
Greg KH wrote:
>
> Network devices do not have a group/owner/mode at all.
>
> > I know it does get triggered, since after replugging the WIFi stick
> > I do get "wlan17" interface.But resulting created device in
> > /dev/bus/usb/00x/00y gets created with
I have heap of problems with udev on systemd.
How is one supposed to troubleshoot rule processing ?
I did do "udevadm control --log-level=debug" and tried to modify
systemd-udevd.service, so that it forks-off just one chiled ( so tha
the log is easier to read), but that still doesn't tell me
On Wed, 28 Sep 2022 23:33:22 +0100
Luca Boccassi wrote:
>
> https://www.freedesktop.org/software/systemd/man/systemd.exec.html#BindPaths=
>
> "This option is particularly useful when RootDirectory=/RootImage= is
> used. In this case the source path refers to a path on the host file
> system,
On Wed, 28 Sep 2022 19:26:58 +1000 (AEST)
Michael Chapman wrote:
> On Wed, 28 Sep 2022, Branko wrote:
> [...]
>
> No.
>
> I've given you a small, self-contained, working example.
>
> It's now your turn to give us a small, self-contained, non-working
> example
it's kind of
pointless...
Try it with chroot somewhere on your disk, e.d. /chroots map or
something and make the service bind-mount executable there.
Like BindPaths=/abssolute/path/to/my_debug-exec:absolute path_into
chroot
and see if it works.
> On Wed, 28 Sep 2022, Branko wrote:
> >
On Wed, 28 Sep 2022 19:07:14 +1000 (AEST)
Michael Chapman wrote:
ExecStart works relative to RootDirectory.
At least for me.
> On Wed, 28 Sep 2022, Branko wrote:
> > OK. You have bound one path. Is the executable within it or is it
> > irrelevant for the case ( and the execut
On Wed, 28 Sep 2022 18:51:01 +1000 (AEST)
Michael Chapman wrote:
> On Wed, 28 Sep 2022, Branko wrote:
> > On Wed, 28 Sep 2022 18:11:14 +1000 (AEST)
> > Michael Chapman wrote:
> >
> > Sure, but this example is kind of useless as it doesn't bind-mount
> >
On Wed, 28 Sep 2022 18:11:14 +1000 (AEST)
Michael Chapman wrote:
Sure, but this example is kind of useless as it doesn't bind-mount
anything into chroot.
We have already established (sorry, didn't post it to the whole list,
it seems):
1. After service fails to start, it doesn't properly
HI,
I have a problem with and FTDI-based device. It keeps dissapearing and
reappearing on every 1-2s or so. Nothing in dmesg to indicate failure.
I'm trying to make my way through systemd-udevd, but it's not easy to
debug things there ( neither is classic udev BTW).
udevadm monitor -u
I have a need to put my NICs in RAID0 so to speak, but according to
materials I have found on net I can't use NIC bonding driver because I
would need LACP (IEEE whatever) aware L2 switch, so I was refered to
teaming driver, which should be ( if those folks is to be believed)
replacing bond
Unless I have overooked something, there seems to be no way to tell dhcp
client to fail and leave card unset after some timeout.
We had popwer interruption, which left dhcp server unconcious and after
rebooting my workstation I couldn't get it up, since it was waiting for
dhcp client to get
Unless I have overlooked something, there seems to be no way to tell
dhcp client to fail and leave card unset after some timeout.
We had power interruption, which left dhcp server unconcious and after
rebooting my workstation I couldn't get it up, since it was waiting for
dhcp client to get
12 matches
Mail list logo
