Claus
--
--
Ph.D. Studerende Claus Hindsgaul
# # Translators, if you are not familiar with the PO format, gettext # documentation is worth reading, especially sections dedicated to # this format, e.g. by running: # info -n '(gettext)PO Files' # info -n '(gettext)Header Entry' # Some information specific to po-debconf are available at # /usr/share/doc/po-debconf/README-trans # or http://www.debian.org/intl/l10n/po-debconf/README-trans# # Developers do not need to manually edit POT or PO files. # # Claus Hindsgaul <[EMAIL PROTECTED]>, 2005. # Claus Hindsgaul <[EMAIL PROTECTED]>, 2006. msgid "" msgstr "" "Project-Id-Version: openldap2 debconf\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2006-10-12 22:23+0200\n" "PO-Revision-Date: 2006-10-20 12:36+0200\n" "Last-Translator: Claus Hindsgaul <[EMAIL PROTECTED]>\n" "Language-Team: Danish\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Generator: KBabel 1.11.4\n"
#. Type: boolean #. Description #: ../slapd.templates:1001 msgid "Do you want to omit the configuration of slapd?" msgstr "Ãnsker du at undlade opsætning af slapd?" #. Type: boolean #. Description #: ../slapd.templates:1001 msgid "If you choose yes here, no default configuration or database will be created." msgstr "Hvis du vælger denne indstilling, vil der ikke blive oprettet en standardopsætning eller -database." #. Type: boolean #. Description #: ../slapd.templates:2001 msgid "Move old database" msgstr "Flyt gammel database" #. Type: boolean #. Description #: ../slapd.templates:2001 msgid "" "There are still files in /var/lib/ldap which will probably break the " "configuration process. With this option enabled the maintainer scripts will " "move the old database files out of the way before creating a new database." msgstr "" "Der er stadig filer i /var/lib/ldap, som sikkert vil lave knaster for " "opsætningsprocessen. Med denne indstilling aktiveret, vil udviklerens scripter " "flytte de gamle databasefiler væk, før der oprettes nye databaser." #. Type: boolean #. Description #: ../slapd.templates:3001 msgid "Retry configuration" msgstr "Prøv opsætning igen" #. Type: boolean #. Description #: ../slapd.templates:3001 msgid "" "The configuration you entered is invalid. Make sure that the DNS domain name " "has a valid syntax, the organization is not left empty and that the admin " "passwords match. If you decide not to retry the configuration the LDAP " "server will not be set up. Run dpkg-reconfigure if you want to retry later." msgstr "" "Den opsætning, du angav, er ugyldig. Sørg for at DNS-domænenavnets syntaks " "er korrekt, at organisationsfeltet ikke er tomt, og at administratorens adgangskoder " "er ens. Hvis du vælger ikke at forsøge opsætningen af LDAP-serveren igen, vil den " "ikke blive sat op. Kør dpkg-reconfigure, hvis du vil forsøge igen senere." #. Type: string #. Description #: ../slapd.templates:4001 msgid "Enter your DNS domain name" msgstr "Angiv dit DNS-domænenavn" #. Type: string #. Description #: ../slapd.templates:4001 msgid "" "The DNS domain name is used to construct the base DN of your LDAP directory. " "Entering foo.bar.org will give you the base DN dc=foo, dc=bar, dc=org." msgstr "" "DNS-domænenavnet bruges til at opbygge basis-DN for din LDAP-bog. Hvis du f.eks. " "skriver foo.bar.dk, vil basis-DN blive dc=foo, dc=bar, dc=dk." #. Type: string #. Description #: ../slapd.templates:5001 msgid "Enter the name of your organization" msgstr "Angiv navnet pÃ¥ din organisation" #. Type: string #. Description #: ../slapd.templates:5001 msgid "" "Whatever you enter here will be stored as the name of your organization in " "the base DN of your LDAP directory." msgstr "" "Det, du skriver her, vil blive gemt som navnet pÃ¥ din organisation i din " "LDAP-bogs basis-DN." #. Type: string #. Description #: ../slapd.templates:6001 msgid "Admin entry" msgstr "Administratoropslaget" #. Type: string #. Description #: ../slapd.templates:6001 msgid "" "The admin entry is the entry in the directory which has full read and write " "access." msgstr "" "Administratoropslaget er det opslag i bogen, som har fuld læse- og " "skriveadgang." #. Type: password #. Description #: ../slapd.templates:7001 msgid "Admin password" msgstr "Administratoradgangskode" #. Type: password #. Description #: ../slapd.templates:7001 msgid " Please enter the password for the admin entry in your LDAP directory." msgstr " Angiv administratoropslagets adgangskode i din LDAP-bog." #. Type: password #. Description #: ../slapd.templates:8001 msgid "Verify password" msgstr "Gentag adgangskode" #. Type: password #. Description #: ../slapd.templates:8001 msgid "Please reenter the admin password for your LDAP directory for verification." msgstr "Gentag administratoradgangskoden til din LDAP-bog." #. Type: note #. Description #: ../slapd.templates:9001 msgid "passwords do not match" msgstr "adgangskoderne var ikke ens" #. Type: note #. Description #: ../slapd.templates:9001 msgid "" "You need to enter the admin password twice. Please note that differences " "such as uppercase/lowercase and added whitespace matter." msgstr "" "Du skal skrive administratoradgangskoden to gange. Bemærk at forskelle i f." "eks. valg af store eller smÃ¥ bogstaver har betydning." #. Type: boolean #. Description #: ../slapd.templates:10001 msgid "Do you want your database to be removed when slapd is purged?" msgstr "Ãnsker du at databasen bliver fjernet, nÃ¥r slapd bliver udrenset?" #. Type: password #. Description #: ../slapd.templates:11001 msgid "encrypted admin password" msgstr "krypteret administratoradgangskode" #. Type: boolean #. Description #: ../slapd.templates:12001 msgid "Change configuration to load backend modules" msgstr "Ret opsætningen og indlæs bagvedliggende moduler" #. Type: boolean #. Description #: ../slapd.templates:12001 msgid "" "With OpenLDAP 2.1 backends are not longer built into the server but are " "instead dynamically loaded at startup. This means that the slapd " "configuration has to be changed to load the modules for the backends you are " "using. If you select this option I'll try to fix the configuration for you. " "If you don't select this then you *must* fix your configuration file " "yourself or slapd (and slapcat if you are upgrading from an older version) " "will fail and the package will not be installed. For more information " "read /usr/share/doc/slapd/README.Debian." msgstr "" "Fra og med OpenLDAP 2.1, er de bagvedliggende moduler ikke længere indbygget " "i serveren, men indlæses i stedet dynamisk under opstarten. Det betyder at " "slapd's opsætning skal ændres, sÃ¥ den indlæser de moduler, du benytter. Hvis " "du vælger denne indstilling, vil jeg forsøge at korrigere opsætningen for " "dig. Hvis du ikke vælger den, mÃ¥ du selv rette din opsætningsfil, da slapd " "(eller slapcat, hvis du opgraderer fra en tidligere version) ellers vil fejle, " "og pakken ikke blive installeret. Du kan læse flere oplysninger om dette " "i /usr/share/doc/slapd/README.Debian." #. Type: boolean #. Description #: ../slapd.templates:13001 msgid "Allow LDAPv2 protocol" msgstr "Tillad LDAPv2-protokollen" #. Type: boolean #. Description #: ../slapd.templates:13001 msgid "" "slapd now defaults to having the old LDAPv2 protocol not allowed. Programs " "and users are generally expected to be upgraded to LDAPv3. If you have old " "programs which have not been moved to use LDAPv3 and you still need LDAPv2 " "support then select this option and 'allow bind_v2' will be added to your " "slapd.conf to tell slapd to accept LDAPv2 connections." msgstr "" "slapd tillader nu som udgangspunkt ikke den gamle LDAPv2-protokol. Det forventes " "generelt at programmer og brugere er opgraderet til LDAPv3. Hvis du har gamle " "programmer, der ikke er overgÃ¥et til LDAPv3, og stadig har brug for " "LDAPv2-understøttelse, sÃ¥ vælg denne indstilling for at tillade at bind_v2 bliver " "føjet til din slapd.conf, sÃ¥ledes at slapd accepterer LDAPv2-forbindelser." #. Type: boolean #. Description #: ../slapd.templates:14001 msgid "Fix LDAP directory on upgrade" msgstr "Korrigér LDAP-bog ved opgradering" #. Type: boolean #. Description #: ../slapd.templates:14001 msgid "" "The installation scripts of the old OpenLDAP 2.0 packages create a directory " "that does not conform to the ldap schema. The new version is more strict " "about this and you won't be able to access your directory after the upgrade " "without fixing it. If you select this option I'll try to fix it for you " "automagically." msgstr "" "Den gamle OpenLDAP 2.0 pakkes installationsskripter opretter en bog, der " "ikke svarer til ldap-skemaet. Den nye version er mere stringent med hensyn " "til dette, og du vil ikke kunne bruge bogen efter opgradering uden at rette " "den. Hvis du vælger denne indstilling, vil jeg forsøge at korrigere den for " "dig automatisk." #. Type: boolean #. Description #: ../slapd.templates:15001 msgid "Move aside current database and create a new one?" msgstr "Flyt den nuværende database væk, og opret en ny?" #. Type: boolean #. Description #: ../slapd.templates:15001 msgid "" "You have specified a directory suffix (domain) that doesn't match the one " "currently in /etc/ldap/slapd.conf. Changing the directory suffix requires " "moving aside the current LDAP database and creating a new one. Are you sure " "you want to abandon the current database? (A backup will be made.)" msgstr "" "Du har angivet en bog-endelse (domæne), der ikke svarer til den, du nu har " "i /etc/ldap/slapd.conf. For at ændre bogens endelse, skal du flytte den " "nuværende database væk, og oprette en ny. Er du sikker pÃ¥, at du vil opgive " "den nuværende database? (Det vil blive lavet en sikkerhedskopi.)" #. Type: note #. Description #: ../slapd.templates:16001 msgid "slapcat failed during upgrade" msgstr "slapcat fejlede under opgraderingen" #. Type: note #. Description #: ../slapd.templates:16001 msgid "" "When attempting to upgrade your LDAP directory there was an error. This " "error occured when performing the 'slapcat' which attempts to extract your " "LDAP directory. This failure could be because of an incorrect config file. " "For example, if the appropriate moduleload lines for your backend database " "type are missing. This failure will cause 'slapadd' later to fail too. The " "old database files are about to be moved to /var/backups. If you want to " "try this upgrade again then move the old database files back into place, fix " "whatever caused slapcat to fail, and run: slapcat | /usr/share/slapd/" "fix_ldif -w -o \"$organization\" > $location Move the database files back to " "a backup area and then try and slapadd from $location." msgstr "" "Der opstod en fejl under forsøget pÃ¥ at opgradere din LDAP-bog. Denne fejl " "opstod under kørslen af 'slapcat', som forsøger at uddrage din LDAP-bog. " "Denne fejl kan skyldes en fejlbehæftet opsætningsfil. F.eks. kan de relevante " "moduleload-linjer mangle. Denne fejl vil senere ogsÃ¥ fÃ¥ 'slapadd' til at fejle. " "De gamle databasefiler skal til at blive flyttet til /var/backups. Hvis du ønsker " "at forsøge denne opgradering igen, sÃ¥ flyt de gamle databasefiler tilbage pÃ¥ plads, " "ret den fejl, der fik slapcat til at fejle, og kør: slapcat | /usr/share/slapd/" "fix_ldif -w -o \"$organization\" > $location . Flyt databsefilerne tilbage til " "et sikkerhedskopi-omrÃ¥de, og prøv at køre slapadd igen fra $location." #. Type: note #. Description #: ../slapd.templates:17001 msgid "slapadd failed during upgrade" msgstr "slapadd fejlede under opgraderingen" #. Type: note #. Description #: ../slapd.templates:17001 msgid "" "When attempting to upgrade your LDAP directory there was an error. This " "error occured when performing the 'slapadd' which attempts to populate an " "empty new LDAP directory using the information from your original LDAP " "directory. Your original LDAP directory files have been saved in /var/" "backups. The results of the attempted upgrade is the ldif file in /var/" "backups. slapadd may have failed due to a configuration problem (in which " "case slapcat would have failed too) or due to a problem in the ldif. If the " "problem was with the ldif then you may be able to fix it and attempt the " "slapadd again." msgstr "" "Der opstod en fejl under forsøget pÃ¥ at opgradere din LDAP-bog. Denne fejl " "opstod under kørslen af 'slapadd', som forsøger at fylde en ny, tom LDAP-bog " "med oplysningerne fra din oprindelige LDAP-bog. Dine gamle databasefiler er " "blevet gemt i /var/backups. Resultatet af den forsøgte opgradering er ldif-filen " "i /var/backups. slapadd kan have fejlet pÃ¥ grund af et opsætningsproblem (i sÃ¥ " "fald vil slapcat ogsÃ¥ have fejlet) eller pÃ¥ grund af et problem med opsætningen " "(ogsÃ¥ i dette tilfælde vil slapcat have fejlet) eller pÃ¥ grund af et problem i ldif. " "Hvis problemet ligger i ldif, kan du muligvis rette denne og prøve at køre slapadd " "igen." #. Type: note #. Description #: ../slapd.templates:18001 msgid "Slave databases require updateref option" msgstr "Slavedatabasen kræver indstillingen \"updateref\"" #. Type: note #. Description #: ../slapd.templates:18001 msgid "" "In your slapd configuration file at least one database is configured as " "slave, and the updateref option is not set. The updateref option specifies " "the referral(s) to pass back when slapd is asked to modify a replicated " "local database. See slapd.conf(5) for more details." msgstr "" "I din slapd-opsætningsfil er mindst en af databaserne sat op som slave, " "og indstillingen 'updateref' er ikke angivet. 'updateref'-indstillingen " "angiver de henvisninger, der skal returneres, nÃ¥r slapd bliver bedt om at ændre " "en replikeret lokal database. Se slapd.conf(5) for yderligere detaljer." #. Type: note #. Description #: ../slapd.templates:18001 msgid "" "Starting with version 2.1.23, slapd requires the updateref option to be set " "on slaves. You should make sure to fix your slapd.conf configuration file." msgstr "" "Fra og med version 2.1.23 kræver slapd at indstillingen \"updateref\" er " "angivet hos slaverne. Sørg for at rette din slapd.conf-opsætningsfil." #. Type: select #. Description #: ../slapd.templates:19001 msgid "Which database backend would you like to use?" msgstr "Hvilken database-bagende vil du benytte?" #. Type: select #. Description #: ../slapd.templates:19001 msgid "" "While the BDB backend is the recommended choice of the OpenLDAP developers, " "the LDBM backend has proven to be more reliable for some Debian users, " "especially when the BDB database wasn't properly configured. When using the " "BDB backend, make sure to do so. For information on how to tune BDB, see " "http://www.openldap.org/faq/data/cache/893.html."; msgstr "" "Mens BDB-bagenden anbefales af OpenLDAP-udviklerne, har LDBM-bagenden " "vist sig at være mere stabil for visse Debianbrugere, især nÃ¥r BDB-databasen " "ikke var sat ordentlig op. NÃ¥r du bruger BDB-bagenden, sÃ¥ sørg for, at den " "er sat ordentligt op. Yderligere oplysninger om, hvordan du bruger BDB finder " "du pÃ¥ http://www.openldap.org/faq/data/cache/893.html."; #. Type: select #. Description #: ../slapd.templates:19001 msgid "" "The BDB backend (back-bdb) and LDBM backend (back-ldbm) are comparable in " "purpose and back-bdb evolved from experience gained from back-ldbm, but the " "two are quite distinct today. They both store entries based on a 32-bit " "entry ID key, and they use a dn2id table to map from DNs to entry IDs. They " "both perform attribute indexing using the same code, and store index data as " "lists of entry IDs. As such, the LDAP-specific features they offer are " "nearly identical. The differences are in the APIs used to implement the " "databases. back-ldbm uses a generic database API that can plug into several " "different database packages. In Debian, it's built against BerkeleyDB (BDB). " "While BerkeleyDB supports this generic interface, it also offers a much " "richer API that has a lot more power and a lot more complexity. back-bdb is " "written specifically for the full BDB API, and uses some of BDB's more " "advanced features to offer transaction processing, fine grained locking, and " "other features that offer improved concurrency and reliability. For more " "information, see http://www.openldap.org/faq/data/cache/756.html."; msgstr "" "Bagenderne BDB (back-bdb) og LDBM (back-ldbm) tjener næsten samme formÃ¥l, og " "back-bdb udsprang af erfaringer, der blev opnÃ¥et med back-ldbm, men de to " "er i dag ret forskellige. Begge gemmer indholdet med 32-bit post-ID-nøgler, " "og begge benytter en dn2id-tabel til at omsætte fra DN'er til post-ID'er. " "De benytter samme kode til attribut-indeksering, og gemmer indeksdata som " "lister over post-ID'er. Som sÃ¥dan er de LDAP-specifikke funktioner, de tilbyder, " "næsten identiske. Forskellen ligger i de API'er, der benyttes til at " "implementere databaserne. back-ldbm benytter en generel database-API, der kan " "tilsluttes flere forskellige databasepakker. I Debian er den lavet med " "BerkeleyDB (BDB). Mens BerkeleyDB understøtter denne generelle grænseflade, " "har den ogsÃ¥ en langt mere omfattende API med flere kræfter og langt større " "kompleksitet. back-bdb er skrevet specifikt til den komplette BDB-API, og " "benytter nogle af BDB's mere avancerede funktioner for at tilbyde " "transaktionshÃ¥ndtering, finkornet lÃ¥sning og andre funktioner, der resulterer " "i forbedret samtidighed og stabilitet. Se" "http://www.openldap.org/faq/data/cache/756.html for yderligere oplysninger."
