It has been several years since I last run a Astlinux system even then
it was only a very, very small system that used an HP T5700 Thin
client. So that dates it.
I am looking to try another simple system, with basically a few sip
phones in the house and a Sip account with some provider again
David,
Yes, Tarsnap is a versioned backup by snapshot, like macOS's Time Machine, so
typically just let Tarsnap do its thing and no need to also keep multiple file
backups. The only drawback is if you wanted to revert to version z.y.x it may
take a little trial and error to find it by date.
A
Thanks Lonnie. I will investigate. While fossil is the single largest
file in my tarsnap backup, there is only one of them. The next largest is
my unifi controller backup at 25MB... for which the last 10 backups are
maintained, so 250MB. As tarsnap maintains its own history, am I right
that thi
Hi David,
I would find why it is growing and ignore them for the future.
By design, Fossil keeps everything forever, though there is a method to "shun"
artifacts but still takes some effort to get a reduction of the fossil database:
https://fossil-scm.org/home/doc/trunk/www/shunning.wiki
I hav
Michael,
Thanks, there could well be some file(s) in there that I don't need.
That is something I am trying to track down. Even if I find that, I'll
need to figure out how to delete from the history in the db.
Oh... and I misread the file size, I was off by a digit, so 100's MB not
over GB. Bu
> Am 18.01.2022 um 15:00 schrieb David Kerr :
>
> Is there a way I can manage my fossil db size? I think it is much larger
> than it could be, probably because it has years of changes... the db is 1.8GB
> which expands to 3.4GB when dumped for tarsnap backup... which is 75% of my
> total tar
Is there a way I can manage my fossil db size? I think it is much larger
than it could be, probably because it has years of changes... the db is
1.8GB which expands to 3.4GB when dumped for tarsnap backup... which is 75%
of my total tarsnap backup, driving up my tarsnap costs.
Is there a way I ca
AstLinux Team,
I'm delighted to see the ongoing progress of AstLinux. Thank you!
Although Asterisk 13SE is still working fine for me, the Pre-Release
recommendation (highlighted below) prompted me to start experimenting with
Asterisk 16 and pjsip/pjproject on a new droplet PBX, which is now 48 h
