Is it possible to set a quota for space used per user? Want to be sure one user doesn't chew up all the space...
Is it possible to set a quota for space used per user? Want to
be sure one user doesn't chew up all the space...
Unfortunately there are no per-user quotas available in Citadel Server.
What we do have is a system-wide safety check, if available disk space goes below 100 MB it will refuse to accept new messages, so the system doesn't get corrupted by a disk full condition.
There is a problem with BCC recieptiens.
They will all appear in Mail header as > Envelope-to:
Is there a option to hide recieptens in header ?
Dear All,
I want to shrink my databases. I tried with the shell script "database_cleanup.sh" and it gives a error even with citadel shutdown and with plenty of disk space (I renamed /tmp in the script).
How to set the "c_shrink_db_files" variable (before compilation)?
I want only an one time shrink.
Thank you,
Luís Gonçalves.
There is a problem with BCC recieptiens.
They will all appear in Mail header as > Envelope-to:
Is there a option to hide recieptens in header ?
Can you clarify please, is this on outbound or inbound email?
I want to shrink my databases. I tried with the shell script "database_cleanup.sh" and it gives a error even with citadel shutdown and with plenty of disk space (I renamed /tmp in the script).
How to set the "c_shrink_db_files" variable (before compilation)?
I want only an one time shrink.
c_shrink_db_files is not a compile-time option. We've worked hard to have as few of those as possible.
If you set the c_shrink_db_files configuration option, the database will be compacted at shutdown time.
If you're not satisfied with the results, I would suggest using ctdldump and ctdlload, not database_cleanup.sh. But really, Citadel is good with disk space -- it will reuse the "holes" in those files to write new data. At some point your disk utilization will stabilize if you have both new data coming in and old data being purged. If you have plenty of disk space and your system is running cleanly I would advise leaving it alone.
Dear Foobar,
I have not so much space.
Do not see this as I putting bad reputation on the software.
Could you please explain how to set "c_shrink_db_files"?
Thank you,
Luís Gonçalves.
I want to shrink my databases. I tried with the shell script "database_cleanup.sh" and it gives a error even with citadel shutdown and with plenty of disk space (I renamed /tmp in the script).
How to set the "c_shrink_db_files" variable (before compilation)?
I want only an one time shrink.
c_shrink_db_files is not a compile-time option. We've worked hard to have as few of those as possible.
If you set the c_shrink_db_files configuration option, the database will be compacted at shutdown time.
If you're not satisfied with the results, I would suggest using ctdldump and ctdlload, not database_cleanup.sh. But really, Citadel is good with disk space -- it will reuse the "holes" in those files to write new data. At some point your disk utilization will stabilize if you have both new data coming in and old data being purged. If you have plenty of disk space and your system is running cleanly I would advise leaving it alone.
There is a problem with BCC recieptiens.
They will all appear in Mail header as > Envelope-to:
Is there a option to hide recieptens in header ?
Can you clarify please, is this on outbound or inbound email?
Hi Ignatius,
this happens on Outbound Mails. It doesnt matter wich Client you use. All BCC mails will show up for everybody who receive the mail. Not in client, but if you look in header from the mail... all will show up @envelopeto
Greetings
Mike
Dear all,
I updated my Centos 9 and the citadel simply stops with Core Dump.
When I do the easy install gives the following:
Error
D▒s▒
I downgraded glibc and it did not worked.
A recompilation did not worked also.
Dear all,
I updated my Centos 9 and the citadel simply stops with Core Dump.
When I do the easy install gives the following:
Error
D▒s▒
I suppose that was the "yum update". Some of the libraries used by citadel were updated. I suppose some incompatibility.How I force a new compile of citadel?Thanks,Luís Gonçaçalves.
With Webcit seems be stable. Some problem with external comunication to Thunderbird.
I downgraded glibc and it did not worked.
A recompilation did not worked also.
Dear all,
I updated my Centos 9 and the citadel simply stops with Core Dump.
When I do the easy install gives the following:
Error
D▒s▒
I suppose that was the "yum update". Some of the libraries used by citadel were updated. I suppose some incompatibility.How I force a new compile of citadel?Thanks,Luís Gonçaçalves.
https://luisgo.pro/down/coredumps.zip
With Webcit seems be stable. Some problem with external comunication to Thunderbird.
I downgraded glibc and it did not worked.
A recompilation did not worked also.
Dear all,
I updated my Centos 9 and the citadel simply stops with Core Dump.
When I do the easy install gives the following:
Error
D▒s▒
I suppose that was the "yum update". Some of the libraries used by citadel were updated. I suppose some incompatibility.How I force a new compile of citadel?Thanks,Luís Gonçaçalves.
I perhaps solved.
In my server I have ports switched between services. And the services in firewalld were not well configured.
Until now is working.
Sorry about all.
https://luisgo.pro/down/coredumps.zip
With Webcit seems be stable. Some problem with external comunication to Thunderbird.
I downgraded glibc and it did not worked.
A recompilation did not worked also.
Dear all,
I updated my Centos 9 and the citadel simply stops with Core Dump.
When I do the easy install gives the following:
Error
D▒s▒
I suppose that was the "yum update". Some of the libraries used by citadel were updated. I suppose some incompatibility.How I force a new compile of citadel?Thanks,Luís Gonçaçalves.
Hi there,
after a while I wanted to upgrade my citadel installation on a raspberrypi with bookworm 32 bit official raspberrypi os
with easy install
My previous version is: Citadel Server 996 mit WebCit #define CLIENT_VERSION 996 /* This version of WebCit */
Server Build: 996
compiling leads to this error:
gcc -I/usr/local/ctdlsupport/include -g -DBUILD_ID=\"25254\" -DCTDLDIR=\"/usr/local/citadel\" -I/usr/local/ctdlsupport/include -g -L/usr/local/ctdlsupport/lib -Wl,--rpath -Wl,/usr/local/ctdlsupport/lib -lssl -lcrypto -lz utils/ctdldump.c server/visit.c -DVISIT_DUMP_LOAD server/backends/berkeley_db/berkeley_db.o server/backends/common/database.o -lcitadel -lz -ldb -lpthread -o ctdldump
/usr/bin/ld: /usr/local/ctdlsupport/lib/libdb.a(os_yield.o): in function `__os_yield_ctdl':
os_yield.c:(.text+0x94): undefined reference to `pthread_yield'
collect2: error: ld returned 1 exit status
gmake: *** [Makefile:59: ctdldump] Fehler 1
Citadel Easy Install is aborting.
The last few lines above this message may indicate what went wrong.
Any idea what this mean?
maybe there is no longer support for a 32 bit OS?
Subject: Re: upgrade with easy install on raspberry pi os
Any idea what this mean?
maybe there is no longer support for a 32 bit OS?
32-bit support is ending soon, but it hasn't ended yet.
Try removing the file /usr/local/ctdlsupport/db-easyinstall.sum (or stash it somewhere safe) and attempt the build again. This will force it to rebuild Berkeley DB.
Dear All,
Second time in a day that I have to delete the database and put back the backup.
Despite I said in a past post that I have not such much disk space I still have 18GBytes.
Every month I make a bakup of my Thunderbird and I delete one month of my older emails. (in a time range of 4 months). But as is normal the database does not reduce. The database is increasing despite it is said that the new emails will occupy the old ones.
My intuition is that this email replacement is not such solid procedure. Sorry to say.
See please the coredump files below:
https://luisgo.pro/down/coredumps2.zip
Thank you,
Luís Gonçalves.
Dear All,
I am still waiting about the procedure to shrink the Database. How to configure the hidden configuration variable?
Luís Gonçalves.
Subject: Concerning tha last two posts in Support Room.
Dear All,
Due to problems reported in the last two posts in this room I am loosing emails. Perhaps due to Citadel misses to write to the database.
Thank you,
Luís Gonçalves.
Subject: Re: Concerning tha last two posts in Support Room.
Hi Luis,
i shrink database with the database script inside the program dir. That works fine for me. my database i now round about 90GB and i dont have any problems.
Greetings
Mike
Subject: Re: Concerning tha last two posts in Support Room.
Dear All,
Due to problems reported in the last two posts in this room I am loosing emails. Perhaps due to Citadel misses to write to the database.
Thank you,
Luís Gonçalves.
What system you are using ? This dont looks like a general citadel problem for me.