From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B513C6F60B for ; Thu, 21 Dec 2023 12:25:43 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=dev-mail.net Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=dev-mail.net Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="g64OX6N6" Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 9BB875C0255; Thu, 21 Dec 2023 07:25:42 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Thu, 21 Dec 2023 07:25:42 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:reply-to:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1703161542; x=1703247942; bh=ou4Jsn3/BOIKG+I1dSzKNNH2leE8xrHariX faKWToIA=; b=g64OX6N6UhzWmQGc5P0fl+apV6oWHVguF9wtPn10OgUvTZSQNgr rk+ynyAkEsVhN1NMG+qOOaW9PQJFr3iyNRDMmrzUXkJ2L+gMwbzp8DhJmzC+rZk6 +jBOKMynLIdQQvpH4ehCfnD5+gVt+hEP3Gj25Bsir8ep/0EQV19zG9ysY/mTEiCv 8GjTit/ckalJMUOv2nNnYuKyDJgyvgva7yiMletsBvu9Sz3YqawI5iMn4RnV0+SQ jRwdmfH4PzdE3hccklewvd8U23fmDaRdJA+wACZ+Lix4IZwSzSauidxRp2/vbumS UPnFEJJRwnWKoQK09BNqFBYHlLunGWSLkDQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrvdduhedgudehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefkffggfghrufevfhfhvfgjtgfgse htjeertddtvdejnecuhfhrohhmpehpghhnugcuoehpghhnugesuggvvhdqmhgrihhlrdhn vghtqeenucggtffrrghtthgvrhhnpeeulefgtddufefftddujedviedvhfejudduheeggf etgedtjeffkeeitdetveefffenucffohhmrghinhepmhgrthhrihigrdhorhhgnecuvehl uhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepphhgnhguseguvg hvqdhmrghilhdrnhgvth X-ME-Proxy: Feedback-ID: if6e94526:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 21 Dec 2023 07:25:41 -0500 (EST) Message-ID: <7a270d09-9c53-47d4-b3e7-603062faf647@dev-mail.net> Date: Thu, 21 Dec 2023 07:25:40 -0500 Precedence: bulk X-Mailing-List: linux-hotplug@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Reply-To: pgnd@dev-mail.net Subject: Re: udev rule in /etc/udev/rules.d/ FAILS to exec on boot; but OK exec @ shell after boot ? Content-Language: en-US Cc: gregkh@linuxfoundation.org, jeisom@gmail.com References: <2023122117-outlet-generic-f184@gregkh> From: pgnd To: linux-hotplug@vger.kernel.org In-Reply-To: <2023122117-outlet-generic-f184@gregkh> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit > Anyway, try asking on the systemd mailing list, which is where udev help > can be found, this list really isn't alive anymore at all, sorry. np, thx. i've posted in systemd:matrix.org; we'll see what pops up there. > Try running 'udevadm monitor' to watch the events to ensure they are > what you think they are. just to close/comment here before moving on, @ shell after boot udevadm monitor | grep enp5s0 KERNEL[40344.410195] change /devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:05.0/0000:05:00.0/net/enp5s0 (net) UDEV [40344.529849] change /devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:05.0/0000:05:00.0/net/enp5s0 (net) and, checking boot logs, journalctl -b | grep systemd-udevd | grep /etc Dec 20 19:24:16 dev systemd-udevd[522]: Trying to open "/etc/systemd/hwdb/hwdb.bin"... Dec 20 19:24:16 dev systemd-udevd[522]: Trying to open "/etc/udev/hwdb.bin"... Dec 20 19:24:16 dev systemd-udevd[522]: Reading rules file: /etc/udev/rules.d/11-dm.rules Dec 20 19:24:16 dev systemd-udevd[522]: Reading rules file: /etc/udev/rules.d/59-persistent-storage-dm.rules Dec 20 19:24:16 dev systemd-udevd[522]: Reading rules file: /etc/udev/rules.d/59-persistent-storage-md.rules Dec 20 19:24:16 dev systemd-udevd[522]: Reading rules file: /etc/udev/rules.d/59-persistent-storage.rules Dec 20 19:24:16 dev systemd-udevd[522]: Reading rules file: /etc/udev/rules.d/61-persistent-storage.rules Dec 20 19:24:16 dev systemd-udevd[522]: Reading rules file: /etc/udev/rules.d/64-lvm.rules Dec 20 19:24:16 dev systemd-udevd[522]: Reading rules file: /etc/udev/rules.d/65-md-incremental-imsm.rules seemingly missing/ignoring, ls -al /etc/udev/rules.d/ -rw-r--r-- 1 root root 2.2K Dec 20 18:47 99-enp5s0-sysctl.rules where find /usr/lib/dracut/modules.d -type f \ -iname 11-dm.rules \ -o -iname 59-persistent-storage-dm.rules \ -o -iname 59-persistent-storage-md.rules \ -o -iname 59-persistent-storage.rules \ -o -iname 61-persistent-storage.rules \ -o -iname 64-lvm.rules \ -o -iname 65-md-incremental-imsm.rules /usr/lib/dracut/modules.d/90dm/11-dm.rules /usr/lib/dracut/modules.d/90dm/59-persistent-storage-dm.rules /usr/lib/dracut/modules.d/90mdraid/59-persistent-storage-md.rules /usr/lib/dracut/modules.d/90mdraid/65-md-incremental-imsm.rules /usr/lib/dracut/modules.d/95udev-rules/59-persistent-storage.rules /usr/lib/dracut/modules.d/95udev-rules/61-persistent-storage.rules /usr/lib/dracut/modules.d/90lvm/64-lvm.rules