Displaying 5 results from an estimated 5 matches for "maibe".
Did you mean:
mabe
2008 Sep 30
0
dovecot quota messages problem
...number(10000).
I made the script which is called when quota_warning condition is met.
Then i made a rule to exclude that folder from quota,
quota_rule3:folder:ignore
The problem is that this folder is still counted in quota.
I don't know if this is a bug or this is how ignore is suposed to work(maibe
ignore works only for storage).
--
View this message in context: http://www.nabble.com/dovecot-quota-messages-problem-tp19738722p19738722.html
Sent from the Dovecot mailing list archive at Nabble.com.
2005 Jan 26
1
Asterisk with PSTN Help........needed!!!!!!!
hi all,
Im trying to configure a * server with FXO and FXS cards. Basically
what i want to do is be able to recieve calls from PSTN and dailout as
well...but im really very confused with how to handle the 30 channels coming
in on the PRI....what would be the best hardware to use n stuff.. if someone
can give me some hints or config examples that would be just great....
Thank's in
2004 Jul 05
0
winbind ldap idmap
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all
There's this situation:
W2k ADS (no changes are allowed to the schema, so no Posix Data to be saved
there) All users are managed via ADS and are only to be managed there (no
separate manualy managed Database for ID Mapping)
2 Un*x servers runing samba 3.x with winbind being used as Fileservers.
With the filebased winbind idmap the
2006 Oct 27
10
"received packet with own address as source address"
Hello again, folks!
I''m getting one strange problem with FC5 running on XEN 3.0.3 x64...
The MRTG point to my machine with XEN running one absurd volume of
output data sent (normal is around 6 MB/s) and when XEN is working we
get 80 MB/s until my DRAC is alive... after this, the machine crash,
DRAC stop do reply, swith stop do work together...
Anyone knows whats happening now? ;)
2003 Dec 01
0
No subject
...did not work. I've also search (quickly)
>the mailing list archive but did not find anything relevant...
Okay, I've found the problem; a misconfiguration in the firewall
caused it to block ports 137-139 on both sides of the firewall; it
should block them only on the Internet side. doh!
Maibe you should add this in DIAGNOSIS.txt: if everything fails, try
to think of the most stupid thing that could prevent samba to work;
chances are this is the problem... 8)
Thanks to Alain Toussaint who sent me a couple of tips on how to
discover the source of the problem,
GFK's
--
Guillaume Filio...