I'm getting started with 389 server. I have a data center where I want to
synch the UIDs across hundreds of Red Hat boxes. I'm starting my way
through the documentation right now. I'm assuming 389 has some kind of
utility/shell script/something to synch UIDs across unix systems for SSO.
A) Is my a
I have a master, hub, and 4 consumers. I want to initialize the consumers who have a replication agreement from the hub.Is it okay to export the replica from one replication agreement to a consumer and use the that same replica for the three other consumers?Paul
--
389 users mailing list
389-us
On 11/04/2013 11:33 AM, WangWentao wrote:
However, I failed to install nvidia driver. After I installed
NVIDIA-Linux-x86-319.60.run(no error), the X cannot be started until I restore
open source driver.
Using the binary blob from nVidia is probably the worst way to go. Not
only does it mang
I got a HP dv4 5306tx laptop with the UEFI+CSM mode enabled, and succeeded in
installation of fedora 18 i686.
However, I failed to install nvidia driver. After I installed
NVIDIA-Linux-x86-319.60.run(no error), the X cannot be started until I restore
open source driver.
I have no idea about
30 seems rather low - we had a problem (since fixed) with our Atlassian
Crowd server (which we use to gateway JIRA, Stash, etc authentication to
389DS via LDAP) where it wouldn't release connections and would have 900+
connections before the 389DS server would stop accepting connections and
we'd ha
Hi,
my question about PAM, libscript... come from my idea: I would like to
implement secondary passwords in very similar way like Google's
application specific passwords works. [1]
We are using LDAP for centralized user management. Systems providing
services to users are verified against this LDA
Morgan Gangwere wrote at 10:55 -0700 on Nov 4, 2013:
> I'm running into a strange problem during resume on a Dell mini 9
> (inspiron 910) when running F19. After coming from Debian and
> having a flawless suspend, this seems strange.
>
> I have removed the @gnome group and added @xfce
>
> P
I'm running into a strange problem during resume on a Dell mini 9 (inspiron
910) when running F19. After coming from Debian and having a flawless suspend,
this seems strange.
I have removed the @gnome group and added @xfce
Process:
* Suspend to RAM
* Resume from RAM
* Xscreensaver hangs for
On Mon, Nov 04, 2013 at 09:31:43 -0800,
Geoffrey Leach wrote:
Sigh! What a bummer. But thanks for the info.
Well, if that works, you could ask the Fedora kernel maintainers about
turning it on. If they know someone is using it and it doesn't cause issues
for others, I expect they'd be like
Sigh! What a bummer. But thanks for the info.
On 11/04/2013 08:18:31 AM, Carlos "casep" Sepulveda wrote:
> On 4 November 2013 01:20, Geoffrey Leach wrote:
> > Any thoughts on how to access the stick under Fedora?
>
> AFAIU, you need to recompile your kernel in order to get it
>
> http://cateee.
There is no output to /var/log/messages when I plug it in.
On 11/04/2013 07:50:57 AM, Mikkel L. Ellertson wrote:
> On 11/03/2013 10:20 PM, Geoffrey Leach wrote:
> > I have a Sony 128MB memory stick. When inserted, Fedora 19 does not
> recognize it -- lsblk does not show it, dmesg reports nothing.
On 11/04/2013 09:39 AM, Ezequiel Larrarte wrote:
On Mon, Nov 4, 2013 at 1:21 PM, Rich Megginson wrote:
On 11/04/2013 09:06 AM, Ezequiel Larrarte wrote:
No matter that they are different versions???
Yes. The replication protocol is the same.
The only problems you might have are schema and sy
On Mon, Nov 4, 2013 at 1:21 PM, Rich Megginson wrote:
> On 11/04/2013 09:06 AM, Ezequiel Larrarte wrote:
>>
>> No matter that they are different versions???
>
>
> Yes. The replication protocol is the same.
> The only problems you might have are schema and syntax incompatibility.
>
>
>>
>> I thoug
On 11/04/2013 09:06 AM, Ezequiel Larrarte wrote:
No matter that they are different versions???
Yes. The replication protocol is the same.
The only problems you might have are schema and syntax incompatibility.
I thought that EPEL would package the same version of 389DS for both
systems Cent
On 11/04/2013 09:08 AM, Jan Tomasek wrote:
On 11/04/2013 05:04 PM, Rich Megginson wrote:
Does the script open a connection to the same server it is being called
from?
Yes.
So this is a case of self-deadlock? I don't understand. What is it
exactly that you expect will happen?
--
389 use
On 4 November 2013 01:20, Geoffrey Leach wrote:
> Any thoughts on how to access the stick under Fedora?
AFAIU, you need to recompile your kernel in order to get it
http://cateee.net/lkddb/web-lkddb/MEMSTICK.html
Using PTP you should be able to read it while pluged-in onto the camera.
Kind rega
On 11/04/2013 05:04 PM, Rich Megginson wrote:
Does the script open a connection to the same server it is being called
from?
Yes.
--
---
Jan Tomasek aka Semik
http://www.tomasek.cz/
--
389 users mailing list
389-us...@lists.fedoraproject.org
https://admin.fedoraproject.org/m
No matter that they are different versions???
I thought that EPEL would package the same version of 389DS for both
systems CentOS 5 and 6 for compatibility reasons, but that 's not what
they have in their repositories.
The thing is ...
If I have 3 server with CentOS 5 and 389DS 1.2.1 replicating
On 11/04/2013 09:00 AM, Jan Tomasek wrote:
On 11/04/2013 04:12 PM, Rich Megginson wrote:
Looks like you do not have the right debuginfo packages installed. But
there may be enough information in the stack trace anyway.
Your pam script is waiting:
Thread 11 (Thread 0x7f60c97ea700 (LWP 10146)):
#
On 11/04/2013 04:12 PM, Rich Megginson wrote:
Looks like you do not have the right debuginfo packages installed. But
there may be enough information in the stack trace anyway.
Your pam script is waiting:
Thread 11 (Thread 0x7f60c97ea700 (LWP 10146)):
#0 0x7f60f0b4209d in waitpid () from /li
On 11/03/2013 10:20 PM, Geoffrey Leach wrote:
> I have a Sony 128MB memory stick. When inserted, Fedora 19 does not recognize
> it -- lsblk does not show it, dmesg reports nothing. It's writable by Windows
> 7, which reports the device as "JMCR MS SCSI Disk Device"
>
> Any thoughts on how to acce
On my Fedora boxes I still use yum-updateonboot.
started with a custom .service file.
Is there any method
I can get it to reboot if a critpath rpm is updated,
I have as yet found an easy method,
without typing all installed @critpath into
/etc/sysconfig/yum-updateonboot,
--
Regards,
Frank
www
22 matches
Mail list logo
