Re: Bumblebee and Fedora 19

Could you try to exec optirun with "-vv --debug" options to see verbose output? Try to uncomment BusID "PCI:01:00:0" string in /etc/bumblebee/xorg.conf.nvidia (Ubuntu bug with same error) Show bumblebee config files. 2013/7/21 Junayeed Ahnaf > I got that, but I'm seeing another kind of problem

Re: Bumblebee and Fedora 19

Check if package xorg-x11-drv-mouse is installed in your system. 2013/7/21 Junayeed Ahnaf > Hello, > > I'm trying to install bumblebee on my laptop. But when I'm trying "optirun > glxgears info" this error is showing: > > > [root@localhost nirjhor]# optirun glxgears info > [ 1691.769152] [ERROR

Re: disanle ssdp

Maybe it's a router-generated traffic. e.g. an Asus router has "Enable UPnP" option in "IP" settings. 2013/7/5 Kevin Wilson > Hello, > I see that from time to time I get in fedora 18 this traffic: > > SSDP - Simple Service Discovery Protocol > > every 2-3 minutes a couple of frames for address

[389-users] Extended control or extop

Hi, I remember reading somewhere on 389 DS site or in dev commits or in trac a request or a realisation of the an extended control/operation that returns the LDAP entries referenced by some attribute. Something like you make a search of a group with this extended control, the search takes all the

Re: [389-users] Named log pipe + normal access log

And/or you could use the "tee" command ("man tee") in the pipe... 2012/2/23 Rich Megginson > On 02/23/2012 08:34 AM, Daniel Fenert wrote: > >> Hi, >> >> I'd like to log to named pipe (just like said here: >> http://directory.**fedoraproject.org/wiki/Named_**Pipe_Log_Script

[389-users] Fwd: [389-announce] Please Help Test 389 Directory Server 1.2.7

Hi Rich, I have two issues with this new version (that i have compiled from the git sources) here is the first issue : there were some changes to the memberfo plugin (Bug 620927) that added a more rigorous verification of memberofgroupattr parameter of MemberOf plugin. We use the uniqueMember/me

Re: [389-users] GSSAPI authentication to Directory Server

Hi, Try kinit username klist -e /usr/bin/ldapsearch -Y GSSAPI -h station1.example.com -b "dc=example,dc=com" "(cn=*)" klist -e At least, that's how it works in our system 2010/10/4 Matt Carey > I'm trying to follow the Kerberos howto guide at > http://directory.fedoraproject.org/wiki/How

Re: [389-users] entryrdn-index error message in error log

html/xml escape? >> http://www.theukwebdesigncompany.com/articles/entity-escape-characters.php > > Thanks, Rich! You are right! And I don't think our DN normalizer supports it. > > Andrey, what you observe is ... > 389 v1.2.6.rc7 has no problem to handle cn=salon d'

Re: [389-users] entryrdn-index error message in error log

. I had no problem to add the entry and search it > using scope base or sub. Could you please give us the steps how to > reproduce your problem? > > Thanks! > --noriko > > > On 08/25/2010 10:49 AM, Andrey Ivanov wrote: > > 2010/8/25 Noriko Hosoi > >> Hi And

Re: [389-users] Incremental Replication over SSL ( and startTLS) with simple bind crashes the latest version

2010/8/25 Rich Megginson > Andrey Ivanov wrote: > >> I wanted to configure the replication over SSL (both with SSL >> mechanism which was available in previous versions) and by TLS using >> simple bind (both in multimaster or single master-dedicated consumer >>

Re: [389-users] entryrdn-index error message in error log

27;,honneur,ou=objets,dc=id,dc=polytechnique,dc=edu to Slapi_RDN > > Thanks, > --noriko > > > On 08/25/2010 08:35 AM, Andrey Ivanov wrote: > >> Hi, >> >> i'm continuing to test the latest version of 389. Here are the error >> messages that i'

[389-users] Incremental Replication over SSL ( and startTLS) with simple bind crashes the latest version

tried the 1.2.6.rc7 version, i've tried the latest code version (as of today). Don't know if it matters (there seem to be a lot of coverity defects that have been fixed between rc7 and a1). Andrey Ivanov tel +33-(0)1-69-33-99-24 fax +33-(0)1-69-33-99-55 Direction des Systemes

Re: [389-users] entryrdn-index error message in error log

10:18:34:31 +0200] - dn2entry: Failed to get id for astreinte,ou=objets,dc=id,dc=polytechnique,dc=edu from entryrdn index (34) ... Andrey Ivanov tel +33-(0)1-69-33-99-24 fax +33-(0)1-69-33-99-55 Direction des Systemes d'Information Ecole Polytechnique 91128 Palaiseau CEDEX France -- 38

[389-users] entryrdn-index error message in error log

d'honneur" C3106:ou=objets ID: 5370; RDN: "cn=SALON D'HONNEUR"; NRDN: "cn=salon d'honneur" P5370:cn=salon d'honneur ID: 3106; RDN: "ou=Objets"; NRDN: "ou=objets" I have not made any upgrades of the existing server. Instead,

Re: [389-users] Outlook VLV index and western europe diacritics

2010/8/25 Rich Megginson > Andrey Ivanov wrote: > >> Hi, >> >> I am testing the 389 latest git version. There is one thing i have >> noticed concerning Outlook browsing of LDAP and VLV indexes. Though i >> think the change has happened already some

[389-users] Outlook VLV index and western europe diacritics

4 file. **) then i thought that maybe i should change the cn index ordering and i have added "nsMatchingRule: 2.16.840.1.113730.3.3.2.18.1" to the cn indexes in dse.ldif. However reindexing does not actually change the order (even after reindexing by smth explicit like db2index -n

Re: [389-users] RHDS and Radius Certificate

. In order to generate them we use openssl, you can try tinyCA or some other web/gui manager of PKI. It's more of certificates/PKI question than LDAP one... > > Thanks for the useful responses. > N > 2010/3/23 Andrey Ivanov > > Hi, >> >> exactly the same fr

Re: [389-users] search on mail attribute no longer case insensative

I've just tested it. Yes, i confirm, the search for the "mail" attribute is case-sensitive. In our system it's not a problem because all the mails are lowercase... I think it is somehow connected to the syntax validation feature included recently... 2010/1/27 Terry Soucy : > Good morning Folks, >

Re: [389-users] require ssl/tls only for binding as user

You have also this (starting from version 1.2.1) : * Add require secure binds switch o This adds a new configuration attribute named nsslapd-require-secure-binds. When enabled, a simple bind will only be allowed over a secure transport (SSL/TLS or a SASL privacy layer). An attempt to