It has no effect whatsoever with regard to what gpioset/gpioget are doing over and above retaining the state configured via gpioset.Not sure what versions of 'libgpiod' you're referring to, but if it's 'libgpiod ver 2.1' I still wonder if the Pi04 patch mentioned by 6by9 is having an effect?
The 'non-daemonize' case where 'gpioset' requires a Ctrl-C to terminate doesn't seem right to me. That is a change from previous behaviour and will play havoc with program code which shells out to run 'gpioset' commands.
...[snip]
I have no idea what it's doing now. Whether there are bugs in 'gpioset', 'gpioget', or any kernel patches, the behaviour you are seeing is not right in my opinion, is worse than it was.
gpioset --daemonize leaves gpioset running (run ps and see), therefore that instance of gpioset has still claimed the gpio and blocks gpioget from using it.
I'll agree that the fact gpioset requires interaction to quit is a little odd, but it does make some sense due to the normal operation of libgpio being to restore the state of the gpio. These are really only test tools though and should never be used for production code (same as was documented for sysfs gpio usage). Scripting with them makes no sense as there is no guarantee over the state of the GPIO after the app quits.
Statistics: Posted by 6by9 — Sun Dec 24, 2023 9:20 pm