Page 1 of 1
Why are there different minimum config file requirements?
Posted: Fri Jan 24, 2025 3:09 am
by ETA_2025
On installation on a Raspberry Pi, the config file contains:
Oddly, with such a config file the Windows client won't load. To load, Windows requires:
Why are there different requirements for the config file, for different systems.
Also, can the Windows client be restarted, without rebooting the computer?
Re: Why are there different minimum config file requirements?
Posted: Fri Jan 24, 2025 4:10 am
by calxalot
I thought the default empty config on Linux was
<config/>
The xml parser should be identical on all platforms.
You can stop the Windows client via system tray item menu item quit.
Start it again from start menu or desktop shortcut.
Logging out will also kill the client, but it is recommended to pause folding from the sys tray menu first. It can take up to a minute for all cores to exit.
Re: Why are there different minimum config file requirements?
Posted: Fri Jan 24, 2025 4:47 am
by ETA_2025
calxalot wrote: ↑Fri Jan 24, 2025 4:10 am
I thought the default empty config on Linux was
<config/>
No, the config files end with </config>. The same as quotes end with [/quote]
The xml parser should be identical on all platforms.
I would have thought so, but my the client wouldn't start on my PC with just </config>.
Start it again from start menu or desktop shortcut.
This doesn't work on my system. But, as I shouldn't need to stop the client, as I've sorted out the config file, it shouldn't be a problem for me.
Re: Why are there different minimum config file requirements?
Posted: Fri Jan 24, 2025 5:00 am
by calxalot
Re: Why are there different minimum config file requirements?
Posted: Fri Jan 24, 2025 6:49 am
by ETA_2025
I can't explain why that page contains incorrect xml code, but everywhere else its </config> as in <end config>.
If I create a config file with:
My browser displays it as:
Note the </config> added at the end.
Also,
How to headless install ? (Ubuntu Server) #214 contains:
Code: Select all
<config>
<account-token v="<your account token>"/>
<machine-name v="<a good display name for this machine>"/>
</config>
Re: Why are there different minimum config file requirements?
Posted: Fri Jan 24, 2025 8:29 am
by calxalot
If you see the three lines in log that is a logging error.
<element></element>
is equivalent to
<element/>
Just </element> alone is invalid xml.
Re: Why are there different minimum config file requirements?
Posted: Fri Jan 24, 2025 11:03 am
by ETA_2025
Indeed you are correct. My memory was obviously wrong, and I'm not an expert at XML.
calxalot wrote: ↑Fri Jan 24, 2025 8:29 am
<element></element>
is equivalent to
<element/>
Thank you. Your explanation makes perfect sense.
And, that explains why I needed the extra line in the Windows config file.