Re: [systemd-devel] Ordering of systemd-tmpfiles-setup.service and systemd-modules-load.service
On 6/23/21 1:31 PM, Tomasz Torcz wrote: https://github.com/lm-sensors/lm-sensors/blob/master/doc/libsensors-API.txt I'm using ctypes-based bindings for Python from https://github.com/paroj/sensors.py Interesting. I may look into porting my application to that at some point. OTOH, reading and writing from a few sysfs files is *really* simple, so that's probably not going to happen any time soon. -- In Soviet Russia, Google searches you! ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Ordering of systemd-tmpfiles-setup.service and systemd-modules-load.service
Dnia Wed, Jun 23, 2021 at 01:25:58PM -0500, Ian Pilcher napisał(a): > On 6/23/21 1:18 PM, Tomasz Torcz wrote: > >lm_sensors library ought to be used as abstraction layer, hiding > > specific hwmon? devices. You can call ‘sensors it8728-isa-0a30' > > and have the same output regardless of module loading order. > > Try sesnors with -u, -j or language bindings for full flexibility. > > AFAIK, lm_sensors does not provide an API that an application can use > to read sensor values, control fan speeds, etc. https://github.com/lm-sensors/lm-sensors/blob/master/doc/libsensors-API.txt I'm using ctypes-based bindings for Python from https://github.com/paroj/sensors.py -- Tomasz Torcz “If you try to upissue this patchset I shall be seeking to...@pipebreaker.pl an IP-routable hand grenade.” — Andrew Morton (LKML) ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Ordering of systemd-tmpfiles-setup.service and systemd-modules-load.service
On 6/23/21 1:18 PM, Tomasz Torcz wrote: lm_sensors library ought to be used as abstraction layer, hiding specific hwmon? devices. You can call ‘sensors it8728-isa-0a30' and have the same output regardless of module loading order. Try sesnors with -u, -j or language bindings for full flexibility. AFAIK, lm_sensors does not provide an API that an application can use to read sensor values, control fan speeds, etc. -- In Soviet Russia, Google searches you! ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Ordering of systemd-tmpfiles-setup.service and systemd-modules-load.service
Dnia Wed, Jun 23, 2021 at 01:03:08PM -0500, Ian Pilcher napisał(a): > I'd like to ensure that I have a stable path to the sysfs files > associated with the IT8728F hardware monitoring chip in this system. > Depending on the order in which various modules are loaded, I've seen > them show up at different paths: > > * /sys/devices/platform/it87.656/hwmon/hwmon0 > * /sys/devices/platform/it87.656/hwmon/hwmon1 > > Is there a better way than udev to achieve this? lm_sensors library ought to be used as abstraction layer, hiding specific hwmon? devices. You can call ‘sensors it8728-isa-0a30' and have the same output regardless of module loading order. Try sesnors with -u, -j or language bindings for full flexibility. -- Tomasz Torcz “If you try to upissue this patchset I shall be seeking to...@pipebreaker.pl an IP-routable hand grenade.” — Andrew Morton (LKML) ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Ordering of systemd-tmpfiles-setup.service and systemd-modules-load.service
On 6/23/21 12:52 PM, Greg KH wrote: sysfs should be "self-contained", trying to add symlinks to it from external places is racy and guaranteed to not work over time. Hmm. Is that true even when the symlink is created by an appropriate udev rule (i.e. linking from /run/$known_location to /sys/$devpath)? What problem are you trying to solve here that links into sysfs is an attempted solution? I'd like to ensure that I have a stable path to the sysfs files associated with the IT8728F hardware monitoring chip in this system. Depending on the order in which various modules are loaded, I've seen them show up at different paths: * /sys/devices/platform/it87.656/hwmon/hwmon0 * /sys/devices/platform/it87.656/hwmon/hwmon1 Is there a better way than udev to achieve this? -- In Soviet Russia, Google searches you! ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Ordering of systemd-tmpfiles-setup.service and systemd-modules-load.service
On Wed, Jun 23, 2021 at 12:27:53PM -0500, Ian Pilcher wrote: > I would like to add a udev rule that creates a symlink to a sysfs > directory, and a subdirectory of /run seem like the right place to put > it. Of course this means that the subdirectory needs to exist. sysfs should be "self-contained", trying to add symlinks to it from external places is racy and guaranteed to not work over time. What problem are you trying to solve here that links into sysfs is an attempted solution? thanks, greg k-h ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Ordering of systemd-tmpfiles-setup.service and systemd-modules-load.service
I would like to add a udev rule that creates a symlink to a sysfs directory, and a subdirectory of /run seem like the right place to put it. Of course this means that the subdirectory needs to exist. The device in question is an "it87" hardware monitoring chip, so the module doesn't get loaded until systemd-modules-load.service runs. It looks like systemd-tmpfiles-setup.service is running before systemd-modules-load.service on my system, but a quick look at the unit files doesn't seem to show any explicit ordering. Is there some sort of explicit or implicit ordering that I've missed? If not, would I break things horribly by adding such ordering? Thanks! -- In Soviet Russia, Google searches you! ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Entry-level bugs/features
On Tue, Jun 22, 2021 at 08:15:53PM -0400, Albert Brox wrote: > Hi folks, > > I'm an experienced developer though have never worked on a large C > project before. > Can anyone point me at a relatively approachable bug or feature > request that I can sink my teeth into? > Trying to gain some familiarity with the world of systems programming. Hi Albert, we don't have such a list handy. You could try https://github.com/systemd/systemd/issues?q=is%3Aopen+is%3Aissue+label%3Aneeds-better-log-message or https://github.com/systemd/systemd/issues?q=is%3Aopen+is%3Aissue+label%3Adocumentation Zbyszek ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
