Added configuration flag flag.

[gosa.git] / FAQ

diff --git a/FAQ b/FAQ
index 927b4c8431f6357a42c9e1fcd6e93f813f0675f6..89cdfd27a9211360130d04ae1d5d0c92945df77f 100644 (file)
--- a/FAQ
+++ b/FAQ
@@ -1,6 +1,5 @@
 This is the textual form of the GOsa FAQ. Online information with
-comments is set up at Wiki: http://wiki.subnet.at/gosa/, thanks to
-Markus Amersdorfer.
+comments is set up at Wiki: http://oss.gonicus.de/gosa/.
 
 Q: When creating many users for one department, I need to fill some
    fields again and again. Is there a shortcut for that?
@@ -90,7 +89,13 @@ A: Yes. Just go to the locale directory and copy the messages.po file somewhere
    You may need to restart apache, depending on your setup. On Debian, be sure
    to have your locale generated (dpkg-reconfigure locales) before.
 
+Q: The online help doesn't exist in my language, can i translate it to my language?
 
+A: Yes. Just go to the doc/guide/user/en directory and copy the lyx-source directory
+   to a new directory in doc/guide/user/<your language>. You have to use the lyx
+   program create the online help in your language. When you have finish just run
+   ./gen_online_help from the gosa root directory to generate the online docs.
+   
 Q: Can I specify some kind of password policies?
 
 A: You can place the keywords "pwminlen" and "pwdiffer" in the main section of your
@@ -284,3 +289,67 @@ A: Yes, add
 
    to the main section of GOsa and the folders are created in unix style.
 
+
+Q: I'd like to do special checks for several plugin parameters. How can I modify
+   GOsa to take care of these checks?
+
+A: No need to modify anything. Just add a hook the the plugin you'd like to
+   check:
+
+   check="/your/command/binary"
+
+   This binary will get an ldif to STDIN for analysis and may write an error message
+   to STDOUT. Note, that the supplied ldif may NOT be the original target ldif due
+   to technical reasons.
+   
+
+Q: Is there a way to use ACL independet filtering when using administrative units?
+
+A: Yes. Set STRICT_UNITS to "true" in your gosa.conf's location section.
+
+
+Q: How can i active the account expiration code for the gosa interface?
+
+A: Yes. Just set "account_expiration" to "true" in your gosa.conf's main section.
+
+
+Q: What is the correct connection string for a Kolab server in GOsa?
+
+A: Try {localhost:143/novalidate-cert}.
+
+
+Q: Sieve is not working from GOsa - there are authentication problems
+   with this service, IMAP/POP is working. What's wrong?
+
+A: Verify that the paramater sasl_auto_transition: no is not
+   present in your imap.conf
+
+
+Q: Slapd does not start with kolab2.schema included. It claims that the
+   definition of calFBURL is missing. What can I do?
+
+A: For Kolab to work correctly you have to include the rfc2739.schema
+   in your slapd.conf. Insert it before the kolab2.schema
+
+
+Q: Is there a way to let GOsa automatically fill missing fields in the network
+   configuration?
+
+A: Sure. You can specify the "auto_network_conf" option and provide the contributed
+   script "net-resolver.sh" in your gosa.conf. If this is configured, you're
+   getting an additional button in each network dialog.
+
+
+Q: New implementations of OpenLDAP seem to require {sasl} instead of {kerberos}
+   in password hashes. GOsa writes the wrong string. What can I do?
+
+A: You can set "krbsasl" to "true" in your gosa.conf's main section.
+
+
+Q: Is there a way to add the personalTitle attribute the the users dn?
+
+A: Just add this line into the location section of your gosa.conf.
+   <location name=...
+       include_personal_title="true"
+   ...>
+