Hi, Happy new year and thank you for your contribution.
> On 2. Jan 2025, at 02:58, Riley Beckett <[email protected]> wrote: Index: package/network/iwd/iwd.init =================================================================== --- package/network/iwd/iwd.init (nonexistent) +++ package/network/iwd/iwd.init (working copy) + block_begin(start, `Starting iwd') + D_libexecdir/iwd 1>/dev/null 2>/dev/null & + sleep 1 + check(`iwctl station list >/dev/null') We usually don’t check for status. IMHO the only status relevant for init is whether the deamon started. This would possible also fail if you start you laptop in a remote location w/o any wifi signals around. + block_begin(stop, `Stopping iwd') + check(`killall D_libexecdir/iwd') + block_end + + block_begin(restart, `Restarting iwd') + killall D_libexecdir/iwd + sleep 1 + D_libexecdir/iwd 1>/dev/null 2>/dev/null & + sleep 1 + check(`iwctl station list >/dev/null') + block_end As this is identical to stop … start I think our .m4 glue auto generates restart, so I removed that part for now, too. Committed revision 72732. If more changes and polishing is required please feel free to send further incremental patches. I guess we have no init script for wpa_supplicantd or other such things, I think the best way to start fwd is probably from new rocknet script glue for the interface based on the etc/ network configuration. Thanks! René -- ExactCODE GmbH, Lietzenburger Str. 42, DE-10789 Berlin http://exactcode.com | http://exactscan.com | http://ocrkit.com
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [email protected] with a subject of: unsubscribe t2
