Having finally fixed its bugs (don't ask) I have a perfect little daemon
that pops itself in background and runs indefinitely, It isn't leaking
memory and its not crashing and there is no reason it ever should, It
accesses files but these will always be present and correct. It will
never need to be killed or HUPed to relaod itself.

What is the absolute simplest way to autostart it. /etc/init.d and a
script linked to etc/rc?.d? systemd?

Raspios is the Os.

--
New Socialism consists essentially in being seen to have your heart in
the right place whilst your head is in the clouds and your hand is in
someone else's pocket.

....an @reboot line in crontab?

--
Take Back Control! -- Mesh The Planet!
I do not play Nethack, I do play GNUS! o;-)
Solid facts do not need 1001 pictures.

On 11/08/2023 12:44, yeti wrote:
> ...an @reboot line in crontab?
>
Yup, I guess that's another one! I'd forgotten that!

--
"Strange as it seems, no amount of learning can cure stupidity, and
higher education positively fortifies it."

- Stephen Vizinczey

On Fri, 11 Aug 2023 12:35:25 +0100
The Natural Philosopher <tnp@invalid.invalid> wrote:

> What is the absolute simplest way to autostart it. /etc/init.d and a
> script linked to etc/rc?.d? systemd?

/etc/rc.local - if it still exists.

--
Steve O'Hara-Smith
Odds and Ends at http://www.sohara.org/
Host: Beautiful Theory meet Inconvenient Fact
Obit: Beautiful Theory died today of factual inconsistency

On 11/08/2023 12:35, The Natural Philosopher wrote:
> Having finally fixed its bugs (don't ask) I have a perfect little daemon
> that pops itself in background and runs indefinitely, It isn't leaking
> memory and its not crashing and there is no reason it ever should, It
> accesses files but these will always be present and correct. It will
> never need to be killed or HUPed to relaod itself.
>
> What is the absolute simplest way to autostart it. /etc/init.d and a
> script linked to etc/rc?.d? systemd?
>
> Raspios is the Os.
>
>
I've just installed pigpiod

/lib/systemd/system/pigpiod.service

[Unit]
Description=Daemon required to control GPIO pins via pigpio
[Service]
ExecStart=/usr/bin/pigpiod -l
ExecStop=/bin/systemctl kill pigpiod
Type=forking
[Install]
WantedBy=multi-user.target

And then 'systemctl enable pigpiod.service' to put in a link in
/etc/systemd/system/multi-user.target.wants

If you change the relevant lines, it should work.

--

Chris Elvidge, England
I WILL NOT SELL MY KIDNEY ON eBAY

On 11/08/2023 13:21, Ahem A Rivet's Shot wrote:
> On Fri, 11 Aug 2023 12:35:25 +0100
> The Natural Philosopher <tnp@invalid.invalid> wrote:
>
>> What is the absolute simplest way to autostart it. /etc/init.d and a
>> script linked to etc/rc?.d? systemd?
>
> /etc/rc.local - if it still exists.
>
Seems to. Whether it is as redundant as tits on a bull, is less obvious.
--
In a Time of Universal Deceit, Telling the Truth Is a Revolutionary Act.

- George Orwell

On 11/08/2023 14:35, Chris Elvidge wrote:
> On 11/08/2023 12:35, The Natural Philosopher wrote:
>> Having finally fixed its bugs (don't ask) I have a perfect little
>> daemon that pops itself in background and runs indefinitely, It isn't
>> leaking memory and its not crashing and there is no reason it ever
>> should, It accesses files but these will always be present and
>> correct.  It will never need to be killed or HUPed to relaod itself.
>>
>> What is the absolute simplest way to autostart it. /etc/init.d and a
>> script linked to etc/rc?.d? systemd?
>>
>> Raspios is the Os.
>>
>>
> I've just installed pigpiod
>
> /lib/systemd/system/pigpiod.service
>
> [Unit]
> Description=Daemon required to control GPIO pins via pigpio
> [Service]
> ExecStart=/usr/bin/pigpiod -l
> ExecStop=/bin/systemctl kill pigpiod
> Type=forking
> [Install]
> WantedBy=multi-user.target
>
> And then 'systemctl enable pigpiod.service' to put in a link in
> /etc/systemd/system/multi-user.target.wants
>
> If you change the relevant lines, it should work.
>
>
Ah, that looks neat. Is the "Type=forking" there to tell systemd not to
expect it *not* to return?

--
In a Time of Universal Deceit, Telling the Truth Is a Revolutionary Act.

- George Orwell

On 8/11/23 10:15, The Natural Philosopher wrote:

> Ah, that looks neat.  Is the "Type=forking" there to tell systemd not to
> expect it *not* to return?
>

Type=simple for a program that just goes off on its own.

--

Knute Johnson

On 11/08/2023 16:15, The Natural Philosopher wrote:
> On 11/08/2023 14:35, Chris Elvidge wrote:
>> On 11/08/2023 12:35, The Natural Philosopher wrote:
>>> Having finally fixed its bugs (don't ask) I have a perfect little
>>> daemon that pops itself in background and runs indefinitely, It isn't
>>> leaking memory and its not crashing and there is no reason it ever
>>> should, It accesses files but these will always be present and
>>> correct. It will never need to be killed or HUPed to relaod itself.
>>>
>>> What is the absolute simplest way to autostart it. /etc/init.d and a
>>> script linked to etc/rc?.d? systemd?
>>>
>>> Raspios is the Os.
>>>
>>>
>> I've just installed pigpiod
>>
>> /lib/systemd/system/pigpiod.service
>>
>> [Unit]
>> Description=Daemon required to control GPIO pins via pigpio
>> [Service]
>> ExecStart=/usr/bin/pigpiod -l
>> ExecStop=/bin/systemctl kill pigpiod
>> Type=forking
>> [Install]
>> WantedBy=multi-user.target
>>
>> And then 'systemctl enable pigpiod.service' to put in a link in
>> /etc/systemd/system/multi-user.target.wants
>>
>> If you change the relevant lines, it should work.
>>
>>
> Ah, that looks neat. Is the "Type=forking" there to tell systemd not to
> expect it *not* to return?
>

See: https://www.freedesktop.org/software/systemd/man/systemd.service.html

--

Chris Elvidge, England
WEDGIES ARE UNHEALTHY FOR CHILDREN AND OTHER LIVING THINGS

The Natural Philosopher <tnp@invalid.invalid> wrote:
> On 11/08/2023 13:21, Ahem A Rivet's Shot wrote:
>> On Fri, 11 Aug 2023 12:35:25 +0100
>> The Natural Philosopher <tnp@invalid.invalid> wrote:
>>
>>> What is the absolute simplest way to autostart it. /etc/init.d and a
>>> script linked to etc/rc?.d? systemd?
>>
>> /etc/rc.local - if it still exists.
>>
> Seems to. Whether it is as redundant as tits on a bull, is less obvious.

As of some years ago it existed, but didn't do anything, in RPi OS.
I found various guides online for enabling it with Systemd, none of
which worked because Systemd obviously changes its workings every
other week. I eventually wrote a script to perform all the
ridiculously over-complicated and opaque configuration scripts to
make it work on a fresh install. I posted that script once in this
group. I won't bother digging it up again now because it seems
extremely likely that by now Systemd will have changed again and it
will be as broken in current RPi OS as the various outdated
tutorials that I spent hours trying to follow originally.

The complication is wanting a process to run after everything else,
not just after some specific things have been started. Systemd is
designed to cater for the latter case, and if you're building the
OS from the ground up that's probably fine, but making it so
complicated to do the former is just unforgivable in my opinion.

I now consider RPi OS as just an example system from which to take
inspiration for implementing software in a more sane, Systemd-free,
environment.

--
__ __
#_ < |\| |< _#

The Natural Philosopher <tnp@invalid.invalid> wrote:
> On 11/08/2023 13:21, Ahem A Rivet's Shot wrote:
>> On Fri, 11 Aug 2023 12:35:25 +0100
>> The Natural Philosopher <tnp@invalid.invalid> wrote:
>>
>>> What is the absolute simplest way to autostart it. /etc/init.d and a
>>> script linked to etc/rc?.d? systemd?
>>
>> /etc/rc.local - if it still exists.
>>
> Seems to. Whether it is as redundant as tits on a bull, is less obvious.

As of some years ago it existed, but didn't do anything, in RPi OS.
I found various guides online for enabling it with Systemd, none of
which worked because Systemd obviously changes its workings every
other week. I eventually wrote a script to perform all the
ridiculously over-complicated and opaque configuration scripts to
make it work on a fresh install. I posted that script once in this
group. I won't bother digging it up again now because it seems
extremely likely that by now Systemd will have changed again and it
will be as broken in current RPi OS as the various outdated
tutorials that I spent hours trying to follow originally.

The complication is wanting a process to run after everything else,
not just after some specific things have been started. Systemd is
designed to cater for the latter case, and if you're building the
OS from the ground up that's probably fine, but making it so
complicated to do the former is just unforgivable in my opinion.

I now consider RPi OS as just an example system from which to take
inspiration for implementing software in a more sane, Systemd-free,
environment.

--
__ __
#_ < |\| |< _#
. Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Tauno Voipio <tauno.voipio@notused.fi.invalid>
Newsgroups: comp.os.linux.misc,comp.sys.raspberry-pi
Subject: Re: Weird code crash
Date: Thu, 14 Sep 2023 10:55:34 +0300
Organization: A noiseless patient Spider
Lines: 75
Message-ID: <udue9m$2i19r$1@dont-email.me>
References: <udu5c4$2gutd$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Thu, 14 Sep 2023 07:55:34 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="13e0ecad3cea277ecfe9b1ace36dd0f0";
logging-data="2688315"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/tWqZq7C2RWGZnKghmwj/m+5b9VDedqh4="
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0)
Gecko/20100101 Thunderbird/102.15.1
Cancel-Lock: sha1:iNXReMIJIWplOOs1MInGpi7VYyw=
In-Reply-To: <udu5c4$2gutd$1@dont-email.me>
Content-Language: en-US
Xref: rslight comp.os.linux.misc:12284 comp.sys.raspberry-pi:8026

The first try should be to check if the system runs fine from a
backup memory card (you have it?).

It is fairly possible that the memory card has some flipped bits,
and the effects are hard to predict.

--

-TV

On 14.9.2023 8.23, The Natural Philosopher wrote:
> I don't expect people to know the answer, but I could use some help in
> puzzling out where to look.
>
> I had a power cut that did leave my network a bit sketchy and it took
> two reboots on this desktop to get back to normal.  This may or may not
> be relevant.
>
> But my question refers to my Pi  Zero W server I am developing.
>
> It came up, ok, but then after a while my relay daemon crashed...
>
> Sep 13 11:26:36 heating-controller systemd[1]: relayd.service: Main
> process exit
> ed, code=killed, status=6/ABRT
> Sep 13 11:26:36 heating-controller systemd[1]: relayd.service: Failed
> with resul
> t 'signal'.
> Sep 13 11:26:36 heating-controller systemd[1]: relayd.service: Consumed
> 15.074s
> CPU time.
>
> I rebooted it, and after awhile - about ten minutes, it happened again -
> that is the above trace.
>
> I restarted it manually, and it hasn't crashed since.
>
> The web is flooded with instances of this messaqe all on different
> platforms and applications, and it would appear this is a very generic
> message possibly to do with memory issues.
>
> One person 'fixed' it by changing CPUs...
> Now *as far as I know* there was nothing special about the data the
> daemon would be operating on it this point to cause it to crash. I am
> fairly sure I have no memory leaks in it - in normal operation it
> strdups() and frees()  and opens and closes files... and 'top' shows
> memory usage is rock steady.
>
> One possibility is that it is opening and reading a file at the precise
> time another process is writing it...in both cases the read and write
> operations are atomic and done with C code.
>
> READ
> ====
> fp=fopen(fullname, "r");
> len=fread(filbuf,1,255,fp); // read entire file
>
> WRITE
> =====
> fp=fopen(filename, "w");
> if (fp)
>     {
>     fprintf(fp,"%s%s\n",filedata,timestamp);
>     fclose(fp);
>     }
>
> Could this cause a problem?
>
> I tend to suspect some sort of asynchronous timing issue because it is
> such a rare occurrence. I have been utterly unable to make it happen on
> demand...
>
>

.
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Bob Latham <bob@sick-of-spam.invalid>
Newsgroups: comp.sys.raspberry-pi
Subject: Re: Limiting the capacity of SD cards for the pi
Date: Wed, 20 Sep 2023 16:34:23 +0100
Organization: None
Lines: 14
Message-ID: <5ae6ec0ddebob@sick-of-spam.invalid>
References: <5ae53c469cbob@sick-of-spam.invalid> <650786bd@news.ausics.net>
<5ae5bad225bob@sick-of-spam.invalid> <6508d35c@news.ausics.net>
<uecvs7$2gotn$1@dont-email.me> <5ae6d95530bob@sick-of-spam.invalid> <kn0892Fsjp7U1@mid.individual.net>
X-Trace: individual.net /8Y93dDTeqfOnX0llDy8bwV483GgtgYMMt6NAfCEm+C2jnolhY
X-Orig-Path: sick-of-spam.invalid!bob
Cancel-Lock: sha1:YvFy6/mCehUtp7Kx1Q/NZHd3rQI= sha256:kKa7HC5t86QFGECkZ6jt7ik/2jd5epV/pJf+keoQYso=
X-No-Archive: Yes
User-Agent: NewsHound/v1.53-32 RC1
Xref: rslight comp.sys.raspberry-pi:8026

In article <kn0892Fsjp7U1@mid.individual.net>,
Andy Burns <usenet@andyburns.uk> wrote:
> Bob Latham wrote:

> > Not got a linux machine only PIs doing little jobs.

> What is an rPi, other than a Linux machine?

It could be a RISCOS machine, I've got one of those running on a PI4.
No linux in site. What I meant was, I don't have a desktop linux PC
only headless units.

Bob.

.
Path: i2pn2.org!i2pn.org!news.nntp4.net!news.hispagatos.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: The Natural Philosopher <tnp@invalid.invalid>
Newsgroups: comp.sys.raspberry-pi
Subject: Re: PCBs available
Date: Fri, 13 Oct 2023 14:35:43 +0100
Organization: A little, after lunch
Lines: 63
Message-ID: <ugbh3f$36utl$1@dont-email.me>
References: <ug8lq4$2fkip$1@dont-email.me>
<yqC*NXHsz@news.chiark.greenend.org.uk> <ugb97s$34vit$6@dont-email.me>
<BqC*R2Ksz@news.chiark.greenend.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Fri, 13 Oct 2023 13:35:43 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="b16245e9d333a2f8f6579c6dad0fba74";
logging-data="3374005"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/HIX6YxpWIZH07X3sN1OgVKIPAMhpfYjg="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:QSxdNJNBP32hFnCjWLog/qeHWx4=
Content-Language: en-GB
In-Reply-To: <BqC*R2Ksz@news.chiark.greenend.org.uk>
Xref: rslight comp.sys.raspberry-pi:8026

On 13/10/2023 13:23, Theo wrote:
> The Natural Philosopher <tnp@invalid.invalid> wrote:
>> Since when I did this professionally it was black tape on clear film, I
>> ended up using Corel Draw! I started with a 3D modelling program to make
>> sure the physical bits fitted, then exported the copper to Corel,
>> because I am very fluent in it
>>
>> I found a CDR to Gerber conversion utility online. That made all the
>> difference and it even worked for the legend. The drill file was harder
>> but again I found a utility to create that.
>
> Nice. An ex-colleague of mine has a startup which does 'PCB art', ie using
> the PCB medium for artistic design that happens to be a functional circuit:
> https://boldport.com/
>
> He has a flow that uses Inkscape for the 'artistry' and then turns it into
> Gerbers:
> https://github.com/boldport/pcbmode
>
> but if you don't need any of the schematic/netlist/ERC/DRC/etc support that
> a PCB tool gives you, just hand drawing it in the drawing package works well
> enough. It's quite a nice idea for making attractive and not-complicated
> boards.
>
>>> I now need to trigger one mains coil from a Pi without exporting mains or
>>> putting any DC wiring in the all-mains enclosure (where I can't get good
>>> isolation). Current plan is to make a photo-triac triggered by light from
>>> an LED on the Pi carried on some optical fibre...
>>
>> If a discrete optical coupler is a nono that might work.
>
> It's a bit annoying... with no DC in the box and not wanting to risk
> exporting mains to the Pi, or making another box with a relay, the obvious
> option is an optocoupler, but you can't really ensure good isolation unless
> you put it in a good enclosure, which is tricky here because I'm shoving it
> in an existing mains box dangling on flying leads.
>
> Aha, I thought, you can get optotriacs to switch AC, so what about if I just
> get a phototriac and shine a light at it to trigger the triac instead of
> having the LED in the optotriac. Trouble is, phototriacs don't exist as a
> discrete component. So the next plan is to use an LDR (photoresistor) to
> trigger the gate of a regular triac (street lights use this for the
> dawn-to-dusk circuit). Only finding an LDR rated for 339Vpeak is tricky, so
> I probably need to voltage divide first...
>
> I suppose I should just bite the bullet with an optotriac, put it in a
> little case with wire tail connections, and pot it all with some HV safe
> resin. Although the idea of a mains box with just an optical fibre input
> does have its appeal...
>
> Theo
yes, you have thought it through all right., I didnt think LDRs had a
'maximum voltage' rating TBH.

On 2023-11-05, 56d.1152 <56d.1152@ztq9.net> wrote:
>
> Nothing beats a static IP. DHCP can, and eventually WILL,
> move stuff around - and then you get weird annoying failures.

Actually does not have to be true.

It is possible to run a dhcp server that hands out a fixed IP address
for a specific MAC. Many home routers allow this feature too. I run my
own DHCP server exactly to have full control over this and many other
features.

Not defending Debian here at all :-) Though I do use debain derived OSes
- but much reconfigured.

In article <OBGdncacO82Jvtr4nZ2dnZfqn_udnZ2d@earthlink.com>,
56d.1152 <56d.1152@ztq9.net> wrote:

> I'll provide a skeleton for a /system-connections template
> on Monday ... there ARE a very few example on the web, but
> VERY few and hard to find. They look nothing like anything
> from before.

If I understand you correctly, I'm looking forward to that.

Thanks.

Bob.

On Sun, 5 Nov 2023 10:40:28 -0000 (UTC)
Jim Jackson <jj@franjam.org.uk> wrote:

> It is possible to run a dhcp server that hands out a fixed IP address
> for a specific MAC.

Which can be a pain when you upgrade a box or want to hand a fixed
IP to something like a phone that randomly changes MAC address to prevent
IPv6 auto allocation being used for tracking.

Many DHCP servers can also allocate a static IP based on hostname
which is really handy especially with DNS/DHCP integrated as in dnsmasq.

--
Steve O'Hara-Smith
Odds and Ends at http://www.sohara.org/
Host: Beautiful Theory meet Inconvenient Fact
Obit: Beautiful Theory died today of factual inconsistency

On 05/11/2023 11:05, Bob Latham wrote:
> In article <OBGdncacO82Jvtr4nZ2dnZfqn_udnZ2d@earthlink.com>,
> 56d.1152 <56d.1152@ztq9.net> wrote:
>
>> I'll provide a skeleton for a /system-connections template
>> on Monday ... there ARE a very few example on the web, but
>> VERY few and hard to find. They look nothing like anything
>> from before.
>
> If I understand you correctly, I'm looking forward to that.
>
> Thanks.
>
> Bob.
>

For my Pi Zero W running bookworm.

I did an in-place upgrade from bullseye to bookworm and then a later
upgrade broke the networking. See the thread "Arrgh!! systemd strikes
again!"

Using a separate Linux system to access the Pi's SDcard I added the
following files

/etc/network/interfaces.d/wlan0
/etc/wpa_supplicant/wpa_supplicant.conf

In my case the content is

/etc/network/interfaces.d/wlan0
allow-hotplug wlan0
iface wlan0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

/etc/wpa_supplicant/wpa_supplicant.conf
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=GB

network={
ssid="MyHomeWifiName"
psk="XXXXXXXXXXXXXXXXXXXXXXXXXX"
}

My router is setup to allocate a set of fixed IP addrs based on MAC
address for some devices that use DHCP. The rest have fixed IP addrs anyway.

In article <ui8b6h$1k37$1@dont-email.me>,
mm0fmf <none@invalid.com> wrote:

> Using a separate Linux system to access the Pi's SDcard I added the
> following files

> /etc/network/interfaces.d/wlan0
> /etc/wpa_supplicant/wpa_supplicant.conf

> In my case the content is

> /etc/network/interfaces.d/wlan0
> allow-hotplug wlan0
> iface wlan0 inet dhcp
> wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

> /etc/wpa_supplicant/wpa_supplicant.conf
> ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
> update_config=1
> country=GB

> network={
> ssid="MyHomeWifiName"
> psk="XXXXXXXXXXXXXXXXXXXXXXXXXX"
> }

Fantastic !! It works !! Well done - thank you.

On a raspberry pi 2 with no built in wi-fi I tried a couple of
different dongles but they both worked

> My router is setup to allocate a set of fixed IP addrs based on MAC
> address for some devices that use DHCP. The rest have fixed IP
> addrs anyway.

Yes, same here.

Thanks again.

Bob.

On 05/11/2023 16:31, Bob Latham wrote:
> In article <ui8b6h$1k37$1@dont-email.me>,
> mm0fmf <none@invalid.com> wrote:
>
>> Using a separate Linux system to access the Pi's SDcard I added the
>> following files
>
>> /etc/network/interfaces.d/wlan0
>> /etc/wpa_supplicant/wpa_supplicant.conf
>
>
>> In my case the content is
>
>> /etc/network/interfaces.d/wlan0
>> allow-hotplug wlan0
>> iface wlan0 inet dhcp
>> wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
>
>
>> /etc/wpa_supplicant/wpa_supplicant.conf
>> ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
>> update_config=1
>> country=GB
>
>> network={
>> ssid="MyHomeWifiName"
>> psk="XXXXXXXXXXXXXXXXXXXXXXXXXX"
>> }
>
> Fantastic !! It works !! Well done - thank you.
>
> On a raspberry pi 2 with no built in wi-fi I tried a couple of
> different dongles but they both worked
>
>> My router is setup to allocate a set of fixed IP addrs based on MAC
>> address for some devices that use DHCP. The rest have fixed IP
>> addrs anyway.
>
> Yes, same here.
>
> Thanks again.
>
> Bob.
>

Glad to be of help. I found stuff about this online so it's not my own
hard work here just the distillation of someone else's efforts.

On 11/5/23 2:25 PM, mm0fmf wrote:
> On 05/11/2023 16:31, Bob Latham wrote:
>> In article <ui8b6h$1k37$1@dont-email.me>,
>>     mm0fmf <none@invalid.com> wrote:
>>
>>> Using a separate Linux system to access the Pi's SDcard I added the
>>> following files
>>
>>> /etc/network/interfaces.d/wlan0
>>> /etc/wpa_supplicant/wpa_supplicant.conf
>>
>>
>>> In my case the content is
>>
>>> /etc/network/interfaces.d/wlan0
>>> allow-hotplug wlan0
>>> iface wlan0 inet dhcp
>>>     wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
>>
>>
>>> /etc/wpa_supplicant/wpa_supplicant.conf
>>> ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
>>> update_config=1
>>> country=GB
>>
>>> network={
>>>           ssid="MyHomeWifiName"
>>>           psk="XXXXXXXXXXXXXXXXXXXXXXXXXX"
>>> }
>>
>> Fantastic !! It works !! Well done - thank you.
>>
>> On a raspberry pi 2 with no built in wi-fi I tried a couple of
>> different dongles but they both worked
>>
>>> My router is setup to allocate a set of fixed IP addrs based on MAC
>>> address for some devices that use DHCP. The rest have fixed IP
>>> addrs anyway.
>>
>> Yes, same here.
>>
>> Thanks again.
>>
>> Bob.
>>
>
>
> Glad to be of help. I found stuff about this online so it's not my own
> hard work here just the distillation of someone else's efforts.

Did that work on BOOKWORM ???

In article <FcGcnQ_s4rd39dX4nZ2dnZfqn_idnZ2d@earthlink.com>,
56d.1152 <56d.1152@ztq9.net> wrote:
> On 11/5/23 2:25 PM, mm0fmf wrote:
> > On 05/11/2023 16:31, Bob Latham wrote:
> >> In article <ui8b6h$1k37$1@dont-email.me>,
> >> mm0fmf <none@invalid.com> wrote:

> >>> I added the following files

> >>> /etc/network/interfaces.d/wlan0
> >>> /etc/wpa_supplicant/wpa_supplicant.conf
> >>
> >>
> >>> In my case the content is
> >>
> >>> /etc/network/interfaces.d/wlan0
> >>> allow-hotplug wlan0
> >>> iface wlan0 inet dhcp
> >>> wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
> >>
> >>
> >>> /etc/wpa_supplicant/wpa_supplicant.conf
> >>> ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
> >>> update_config=1
> >>> country=GB
> >>
> >>> network={
> >>> ssid="MyHomeWifiName"
> >>> psk="XXXXXXXXXXXXXXXXXXXXXXXXXX"
> >>> }
> >>
> >> Fantastic !! It works !! Well done - thank you.

> Did that work on BOOKWORM ???

Yes it does!

However, one word of caution. There is a strong tendency for the OS
to overwrite the file /etc/wpa_supplicant/wpa_supplicant.conf with
zeros. I've seen this with bullseye too. I suspect it is some weird
security measure to try to stop tinkering.

The solution with bullseye is to copy that file not to
/etc/wpa_supplicant but whilst the SD card is still in the PC copy it
to the boot partition. The Pi then copies this into the correct place
at boot up and marks it as valid in some way to prevent overwrite.
I've not tried this yet on bookworm, that's up next...

Bob.

On 06/11/2023 08:24, Bob Latham wrote:
> In article <FcGcnQ_s4rd39dX4nZ2dnZfqn_idnZ2d@earthlink.com>,
> 56d.1152 <56d.1152@ztq9.net> wrote:
>> On 11/5/23 2:25 PM, mm0fmf wrote:
>>> On 05/11/2023 16:31, Bob Latham wrote:
>>>> In article <ui8b6h$1k37$1@dont-email.me>,
>>>> mm0fmf <none@invalid.com> wrote:
>
>>>>> I added the following files
>
>>>>> /etc/network/interfaces.d/wlan0
>>>>> /etc/wpa_supplicant/wpa_supplicant.conf
>>>>
>>>>
>>>>> In my case the content is
>>>>
>>>>> /etc/network/interfaces.d/wlan0
>>>>> allow-hotplug wlan0
>>>>> iface wlan0 inet dhcp
>>>>> wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
>>>>
>>>>
>>>>> /etc/wpa_supplicant/wpa_supplicant.conf
>>>>> ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
>>>>> update_config=1
>>>>> country=GB
>>>>
>>>>> network={
>>>>> ssid="MyHomeWifiName"
>>>>> psk="XXXXXXXXXXXXXXXXXXXXXXXXXX"
>>>>> }
>>>>
>>>> Fantastic !! It works !! Well done - thank you.
>
>
>> Did that work on BOOKWORM ???
>
> Yes it does!
>
> However, one word of caution. There is a strong tendency for the OS
> to overwrite the file /etc/wpa_supplicant/wpa_supplicant.conf with
> zeros. I've seen this with bullseye too. I suspect it is some weird
> security measure to try to stop tinkering.
>
> The solution with bullseye is to copy that file not to
> /etc/wpa_supplicant but whilst the SD card is still in the PC copy it
> to the boot partition. The Pi then copies this into the correct place
> at boot up and marks it as valid in some way to prevent overwrite.
> I've not tried this yet on bookworm, that's up next...
>
> Bob.
>

Not happening here but I do note that nmcli says wlan0 is unmanaged.

On 06/11/2023 08:47, mm0fmf wrote:
> On 06/11/2023 08:24, Bob Latham wrote:
>> In article <FcGcnQ_s4rd39dX4nZ2dnZfqn_idnZ2d@earthlink.com>,
>>     56d.1152 <56d.1152@ztq9.net> wrote:
>>> On 11/5/23 2:25 PM, mm0fmf wrote:
>>>> On 05/11/2023 16:31, Bob Latham wrote:
>>>>> In article <ui8b6h$1k37$1@dont-email.me>,
>>>>>      mm0fmf <none@invalid.com> wrote:
>>
>>>>>> I added the following files
>>
>>>>>> /etc/network/interfaces.d/wlan0
>>>>>> /etc/wpa_supplicant/wpa_supplicant.conf
>>>>>
>>>>>
>>>>>> In my case the content is
>>>>>
>>>>>> /etc/network/interfaces.d/wlan0
>>>>>> allow-hotplug wlan0
>>>>>> iface wlan0 inet dhcp
>>>>>>      wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
>>>>>
>>>>>
>>>>>> /etc/wpa_supplicant/wpa_supplicant.conf
>>>>>> ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
>>>>>> update_config=1
>>>>>> country=GB
>>>>>
>>>>>> network={
>>>>>>            ssid="MyHomeWifiName"
>>>>>>            psk="XXXXXXXXXXXXXXXXXXXXXXXXXX"
>>>>>> }
>>>>>
>>>>> Fantastic !! It works !! Well done - thank you.
>>
>>
>>>     Did that work on BOOKWORM ???
>>
>> Yes it does!
>>
>> However, one word of caution. There is a strong tendency for the OS
>> to overwrite the file /etc/wpa_supplicant/wpa_supplicant.conf with
>> zeros. I've seen this with bullseye too. I suspect it is some weird
>> security measure to try to stop tinkering.
>>
>> The solution with bullseye is to copy that file not to
>> /etc/wpa_supplicant but whilst the SD card is still in the PC copy it
>> to the boot partition. The Pi then copies this into the correct place
>> at boot up and marks it as valid in some way to prevent overwrite.
>> I've not tried this yet on bookworm, that's up next...
>>
>> Bob.
>>
>
> Not happening here but I do note that nmcli says wlan0 is unmanaged.

Oh dear, replying to myself....

As it's unmanaged by NetworkManagaer, then it's being left alone. That's
just fine for what this PiZeroW is used for. I have another PiZeroW with
the same release of software that I'll play with and will add wlan0 to
NetworkManager's grasp so I can see what it does (if anything).

In article <uia9di$dimp$1@dont-email.me>,
mm0fmf <none@invalid.com> wrote:
> On 06/11/2023 08:47, mm0fmf wrote:
> > On 06/11/2023 08:24, Bob Latham wrote:

> >> However, one word of caution. There is a strong tendency for the
> >> OS to overwrite the file /etc/wpa_supplicant/wpa_supplicant.conf
> >> with zeros. I've seen this with bullseye too. I suspect it is
> >> some weird security measure to try to stop tinkering.
> >>
> >> The solution with bullseye is to copy that file not to
> >> /etc/wpa_supplicant but whilst the SD card is still in the PC
> >> copy it to the boot partition. The Pi then copies this into the
> >> correct place at boot up and marks it as valid in some way to
> >> prevent overwrite. I've not tried this yet on bookworm, that's
> >> up next...
> >>
> >> Bob.
> >>
> >
> > Not happening here but I do note that nmcli says wlan0 is
> > unmanaged.

> Oh dear, replying to myself....

> As it's unmanaged by NetworkManagaer, then it's being left alone.
> That's just fine for what this PiZeroW is used for. I have another
> PiZeroW with the same release of software that I'll play with and
> will add wlan0 to NetworkManager's grasp so I can see what it does
> (if anything).

Further testing just, has revealed that bookworm doesn't seem to copy
the wpa_supplicant.conf file from boot partition at boot up like
bullseye did. The only way I've found to get that file there is via
ethernet and in my case samba.

Upon reboot, sometimes the wpa_supplicant.conf files gets overwritten
with zeros and sometimes not. I've no idea why.

Bob.

On 06/11/2023 09:17, Bob Latham wrote:
> In article <uia9di$dimp$1@dont-email.me>,
> mm0fmf <none@invalid.com> wrote:
>> On 06/11/2023 08:47, mm0fmf wrote:
>>> On 06/11/2023 08:24, Bob Latham wrote:
>
>>>> However, one word of caution. There is a strong tendency for the
>>>> OS to overwrite the file /etc/wpa_supplicant/wpa_supplicant.conf
>>>> with zeros. I've seen this with bullseye too. I suspect it is
>>>> some weird security measure to try to stop tinkering.
>>>>
>>>> The solution with bullseye is to copy that file not to
>>>> /etc/wpa_supplicant but whilst the SD card is still in the PC
>>>> copy it to the boot partition. The Pi then copies this into the
>>>> correct place at boot up and marks it as valid in some way to
>>>> prevent overwrite. I've not tried this yet on bookworm, that's
>>>> up next...
>>>>
>>>> Bob.
>>>>
>>>
>>> Not happening here but I do note that nmcli says wlan0 is
>>> unmanaged.
>
>> Oh dear, replying to myself....
>
>> As it's unmanaged by NetworkManagaer, then it's being left alone.
>> That's just fine for what this PiZeroW is used for. I have another
>> PiZeroW with the same release of software that I'll play with and
>> will add wlan0 to NetworkManager's grasp so I can see what it does
>> (if anything).
>
> Further testing just, has revealed that bookworm doesn't seem to copy
> the wpa_supplicant.conf file from boot partition at boot up like
> bullseye did. The only way I've found to get that file there is via
> ethernet and in my case samba.
>
> Upon reboot, sometimes the wpa_supplicant.conf files gets overwritten
> with zeros and sometimes not. I've no idea why.
>
> Bob.
>

Just 'cos of this thread, I've been frigging around with bookworm lite
on a PiB+. After getting the firmware for my dongle - took a long time
to compile - TP-Link AC600 wireless Realtek RTL8811AU [Archer T2U Nano],
I just did:
nmcli d wifi connect "myssid" password "mypassword" ifname wlan0

It survives a reboot. My wpa_supplicant.conf file stays unchanged (and
unneeded). The bit about it not being copied from /boot/ is documented
here:
https://www.raspberrypi.com/documentation/computers/configuration.html#connect-to-a-wireless-network

Quote: "Previous versions of Raspberry Pi OS made use of a
wpa_supplicant.conf file which could be placed into the boot folder to
configure wireless network settings. This is no longer possible from
Raspberry Pi OS Bookworm onwards."

I found Jeff Geerling's blog handy:
https://www.jeffgeerling.com/blog/2023/nmcli-wifi-on-raspberry-pi-os-12-bookworm

What exactly is the problem being fixed here?

BTW Bookworm is (subjectively) faster than Bullseye on a PiB+

--
Chris Elvidge, England
I AM NOT A LEAN MEAN SPITTING MACHINE

On 06/11/2023 12:22, Chris Elvidge wrote:
> What exactly is the problem being fixed here?

In my case I had working Buster and upgraded in situ to Bullseye then
Bookworm on a headless PiZeroW. The legacy network setup was moved and
the automatic power up connection to Wifi stayed active. Then a recent
update to Bookworm changed NetworkManager and Wifi was broken. The fix
is as described early.

I've been playing with nmcli on a Pi with some USB Wifi dongles and have
played with nmcli d wifi connect.... and yes, it works and survives
reboots. My built wlan0 is currently unmanaged by NM.

I'm thinking a clean install of Bookworm would have put wlan0 under NM
control. But as it was using the old style setup it was left as is (and
working). The later NM update didn't / couldn't cope with that style of
setup, failed and broke the old style network setup. What I've done
(which I found somewhere online) works and leaves wlan0 outside of NM
control.

I'm just considering whether to leave as it as it is working or to do a
sudo nmcli dev set wlan0 managed yes, remove the files I added and let
NM manage it from now on. Probably the best course of action in the long
run as it's possible and probable a future NM update may break things
again.

In article <uialr1$fcug$1@dont-email.me>,
Chris Elvidge <chris@mshome.net> wrote:

> Just 'cos of this thread, I've been frigging around with bookworm
> lite on a PiB+. After getting the firmware for my dongle - took a
> long time to compile - TP-Link AC600 wireless Realtek RTL8811AU
> [Archer T2U Nano], I just did:

> nmcli d wifi connect "myssid" password "mypassword" ifname wlan0

> It survives a reboot. My wpa_supplicant.conf file stays unchanged
> (and unneeded).

<stunned gulp>

Are you saying that you get a wi-fi dongle to work with just one
command?

Wow, I'll try this out later.

> The bit about it not being copied from /boot/ is
> documented here:
> https://www.raspberrypi.com/documentation/computers/configuration.html#connect-to-a-wireless-network

> Quote: "Previous versions of Raspberry Pi OS made use of a
> wpa_supplicant.conf file which could be placed into the boot folder
> to configure wireless network settings. This is no longer possible
> from Raspberry Pi OS Bookworm onwards."

Well at least my testing was correct then. :-)

> I found Jeff Geerling's blog handy:
> https://www.jeffgeerling.com/blog/2023/nmcli-wifi-on-raspberry-pi-os-12-bookworm

I'll have a read of that, thanks.

> What exactly is the problem being fixed here?

Recently I've been using secondhand pi3 devices because they have
wi-fi built in and that just worked from raspi-config on bookworm.

Then I saw this thread and thought I'd try a pi2 with a wi-fi dongle
and I couldn't get it to work certainly not as I'd done on bullseye.

Clever fold on here told me a way to get it going and that did work.

Later I'll try your suggestion and see if that works for me. I just
don't know how you find out this stuff. :-)

Thanks for the suggestion.

Bob.