Dear Davide,
Is this maybe something we can patch ourselves in the code? I would be
very much interested in starting to use this since updates to accounts
are very regular for us.
Thanks!
Sincerely,
Bart Mortelmans
Davide Libenzi schreef:
On Mon, 16 Jun 2008, Bart Mortelmans wrote:
Davide Libenzi wrote:
Yep, you're right. There's a common function to load the user info, and
this one fetches the user.tab file too.
I fixed it in the next version by adding a parameter to tell if the caller
wants user.tab info too, when loading it.
Thanks! Looking forward to this new
I did some testing with strace. Running it on CtrlClnt didn't tell me
much, so I started XMail in debug through strace.
As I understand the result correctly, then XMail forks to handle the
CTRL-request. The first files it opens in that fork seem reasonable:
ctrl.ipmap.tab, ctrlaccounts.tab,
On Mon, 16 Jun 2008, Bart Mortelmans wrote:
I did some testing with strace. Running it on CtrlClnt didn't tell me
much, so I started XMail in debug through strace.
As I understand the result correctly, then XMail forks to handle the
CTRL-request. The first files it opens in that fork seem
Dear Davide,
Thanks for your input! To check that I'm certainly not doing anything
else time-consuming and that it's not a faulty hard drive with a bad
cluster in mailusers.tab, I made this little shell script:
===
date
grep \test\.domain\.tld\ ../mailusers.tab
date
../CtrlClnt -s localhost
Delays do indeed make me think of some sort of timeout. But using
127.0.0.1 didn't make a difference...
Op 15-jun-08, om 19:04 heeft decker het volgende geschreven:
Hey,
../CtrlClnt -s localhost -u *** -p ** userlist
test.domain.tld
Just a shot in the dark, is it the same
On Fri, 13 Jun 2008, Bart Mortelmans wrote:
Hi all,
When I run the CTRL-command userlist requesting users for one domain,
it seems to take an unreasonable amount of time before it returns (20 to
30 seconds). In between, when I monitor the server with the Linux
command top, I notice that