Heh -- just having checked my own post, I see that trn doesn't bother to add either a 'Content-type:' or a 'Content-Transfer-Encoding:' header, so I wonder if that causes problems elsewhere? (There's at least one utf-8 character there, copied over in the quoted section.)
These are MIME headers, originally intended for email.
Usenet predates MIME by a long way, and it's only relatively recently that it has been updated to allow MIME. Although MIME has worked for many users who read Usenet through email clients which supported MIME for a long time, strictly it was not in the spec.
trn is probably written to RFC1036, where usenet articles are only permitted to be 7-bit ASCII. MIME is added to Usenet in RFC5536 in Nov 2009.
[email address is not usable -- followup in the newsgroup]
I tried and installed mysql on the Pi (modell B). After converting the
everything worked well. It seemed.
But then I tried to sync approx. 400 vcards via carddav ? load increased to 12, peaked at 20 (!) and even my 100 MB swap ran full (this never, never happened before in one year). And? Well, owncloud could not manage it, it seems. The second computer synced and got nearly 600 vcards, but looots of doublettes. And I could not reach the adressbook via https.
So, sad but true, it seems the Pi won?t be able to handle this combination. Bad due to sqlite is too slow and blocks with locks. With mysql this did not happen, but the machine maybe had not enough power? I run it with 800 MHz scaling governor.
Make sure it's not swapping first. Really. That's important - if it swaps, then you'll lost 99% of any avalable anything )-:
Edit /etc/my.cnf and look for the numbers.
I've never installed Debians version of MySQL though - but the MySQL source distribution comes with small, medium and large standard configuration files - seeing if they exist might be a good starting point (ie. start with the small one)
Ehm, I just switched the database type from sqlite to mysql ? means, let owncloud convert and switch. So me, I hadn?t defined anything.
I just wanted owncloud to work. I?m not a database specialist. As with sqlite, one sets up and it goes. So the owncloud team itself just states mysql is the better way for bigger (what this means) installations. Nothing more. A bit poor information for the masses.
What do you think? It's the Pi. Or specifically Linux running on the Pi deciding that some program or other needs more memory, so it (Linux) swaps stuff out to disk (SD card)
It's not going to happen. Only the most trivial of mysql systems on a Pi is going to work without any sort of tuning. You "get away" with it these days because servers have stupid amount of memory and fast processors. A Pi has neither, so you'll need to tune.
There are gigabytes of manuals, documents, how-to's, etc. online about MySQL tuning. Start reading.
mysql-workbench is available, as is mysqltuner which may help decide which parameters to set.
I don't run MySQL on a Pi, but I do have several (admittedly not too busy) MySQL databases and an Apache server running on an old PC which has 384MB RAM and a 500MHz Celeron CPU. It's a bit faster than a Pi.
Maybe it would be reasonable to expect that a MySQL package distributed in a Pi distribution is already tuned not to use more memory than a Pi usually has available.
OTOH, I know someone who runs an out-of-the-box VoIP exchange install on a Pi (Asterisk plus some web config frontend that I think uses MySQL as configuration storage), so either the tuning is better on that install or it is not so much of an issue until you really start to load it.