Hi all,
RedHat DS's doc states that the nsAccountLock attribute is multi-valued [1].
Some tests with 389ds led me to think it's also true for 389ds.
I cannot think of any reason explaining why it would have to be multi-valued.
Do you have any idea?
Thank you.
[1]
Hi,
yes, aci processing can become very expensive if you have a lot of acis
are used, the code tries to do soem optimizations to cache evaluation,
but a small change in acis could prevent the use of cached results. So
if you do not have a full set of acis from the better times it will be
Hello,
DS base: 1.3.0.4
DS admin: 1.3.1.31
I´m trying to setup a new version of 389 DS multi master replication with
active directory(win 2008) and I´m getting the following erros:
[04/Jul/2013:16:57:32 -0300] NSMMReplicationPlugin - agmt=cn=AD-HMG1
(hmg1:636): binddn = CN=Conta de
Hello,
I'm experiencing system hangs and kernel oops on Fedora 19. Everything
happens when I restart guest system inside qemu/kvm container. My system
becomes unstable on kernel 3.9.5 and totally hangs on 3.9.6 and later.
It happens just after guest OS (latest stable Debian Linux) shows grub
boot
Hello everybody,
I've recently upgraded to f19, and with gnome 3.8, i've seen a bug
appearing,Sometimes, when I want to switch between users, the user list isn't
shown. I mean, there are the dropdowns (Calendar, shutdown, etc), the mouse is
also here and is functionnal, but the user list isn't
On 04.07.2013 10:12, Mateusz Marzantowicz wrote:
Hello,
I'm experiencing system hangs and kernel oops on Fedora 19. Everything
happens when I restart guest system inside qemu/kvm container. My system
becomes unstable on kernel 3.9.5 and totally hangs on 3.9.6 and later.
It happens just
On 04.07.2013 10:32, poma wrote:
On 04.07.2013 10:12, Mateusz Marzantowicz wrote:
Hello,
I'm experiencing system hangs and kernel oops on Fedora 19. Everything
happens when I restart guest system inside qemu/kvm container. My system
becomes unstable on kernel 3.9.5 and totally hangs on 3.9.6
On 04.07.2013 10:42, Mateusz Marzantowicz wrote:
On 04.07.2013 10:32, poma wrote:
On 04.07.2013 10:12, Mateusz Marzantowicz wrote:
Hello,
I'm experiencing system hangs and kernel oops on Fedora 19. Everything
happens when I restart guest system inside qemu/kvm container. My system
becomes
On 04.07.2013 11:17, poma wrote:
On 04.07.2013 10:42, Mateusz Marzantowicz wrote:
On 04.07.2013 10:32, poma wrote:
On 04.07.2013 10:12, Mateusz Marzantowicz wrote:
Hello,
I'm experiencing system hangs and kernel oops on Fedora 19. Everything
happens when I restart guest system inside
On Wed, 2013-07-03 at 18:33 -0400, Tom Horsley wrote:
I can assure you, I am not manually modifying anything installed by
those packages to cause this mismatch. I do notice they are all
32 bit packages, but I'm running 64 bit. Is yum trying to apply
a 64 bit delta to a 32 bit package or
El 2013-07-04 02:04, T.C. Hollingsworth escribió:
On Jul 3, 2013 1:12 PM, Richard Vickery richard.vicker...@gmail.com
wrote:
Is there a way to reboot the computer while its stuck on Starting
GNOME Desktop Manager?
Usually by this point in the boot process you can press CTRL+ALT+F2 to
get a
On Thu, 04 Jul 2013 12:36:25 +0300
Jonathan Dieter wrote:
I believe that's exactly what yum is doing. Now that yum-presto has
been merged into yum for Fedora 19, your best bet would be to file a bug
against yum itself.
Yea, I might as well. At least I might get a reason why it isn't
a bug
On Thu, 2013-07-04 at 08:55 -0400, Tom Horsley wrote:
On Thu, 04 Jul 2013 12:36:25 +0300
Jonathan Dieter wrote:
I believe that's exactly what yum is doing. Now that yum-presto has
been merged into yum for Fedora 19, your best bet would be to file a bug
against yum itself.
Yea, I
On Thu, 04 Jul 2013 16:48:30 +0300
Jonathan Dieter wrote:
I found the mistake and I've posted a patch to that bug that should fix
it.
Cool! So it really is a bug. Thanks for the patch!
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
systemctl start named-chroot.service hangs for a minute, or so.
ps shows that named is running, but systemctl is trying to execute the
following:
root 2036 2035 0 09:53 pts/000:00:00
/usr/bin/systemd-tty-ask-password-agent --watch
After a minute or so, this timesout, and named
Dear Fedora-fans,
I reported unstable results with dual head and F18.
I now
fedup'ed to F19 and things got worse. The login screen appears but
login attempts hang. By ssh from another machine I see:
[ 496.050] (EE) intel(0): [drm] failed to set drm interface version.
I
Yesterday I installed Fedora 19 on my workstation. I skipped Fedora 18
entirely as the installation GUI didn't give me any confidence I could do my
usual thing.
My usual thing is to install each new version into different logical volumes
than the current OS. In this case the current OS was
Emmett Culley lst_manage at webengineer.com writes:
I can say for sure that this time I found the installation UI (anaconda?)
not only easy to use, but pretty darn
good looking as well. Of course, like many on this list I also found it
to be less flexible when selecting
what I want installed.
This is something that happened during F18 and seems to have been fixed.
Has there been a regression to the current F19 kernel?
Description of problem:
After some time in operation, the WiFi network is dropped. Network
Manager attempts to connect, but reconnection is unsuccessful. Reboot
is
On 07/04/2013 05:55 AM, Tom Horsley wrote:
Yea, I might as well. At least I might get a reason why it isn't
a bug when they close it :-).
Judging by my own recent experience, the next time you hear anything
about it is when they close it as WONTFIX when F 19 reaches EOL.
--
users mailing
Do you use tracker? Can you give examples of how you've used it
and if you find it useful?
Is there a useful guide to exploiting tracker?
background / war story
I've been oblivious to tracker. I must have had it for some time, but
it hasn't crashed so it didn't come to my attention.
It
On Wednesday, July 3, 2013, 4:08:14 AM, Andew Robatino wrote:
antonio montagnani antonio.montagnani at alice.it writes:
After fedup'ing I have a fully updated system but surprise I cannot
login, after the password insertion of any user I get a blank screen
with the fedora log on the
greetings hugh,
On 07/04/2013 02:04 PM, D. Hugh Redelmeier wrote:
Do you use tracker?
no. see below.
I've been oblivious to tracker.
me too. :=)
Anxious to throw stuff overboard from my 0-bytes-free /home, I deleted
the Firefox cache (politely via Firecox Edit: Preferences: Advanced:
hello juan,
On 07/04/2013 04:49 AM, Juan Orti Alcaine wrote:
Another good option if everything else fails (and you have configured
previously kernel.sysrq=1 with sysctl) is:
Alt+SysRq+ {R, E, I, S, U, B}
See: https://en.wikipedia.org/wiki/Magic_SysRq_key#Uses
very good read. thanks for
How do I fix these messages:
/usr/bin/curl: /lib64/libcrypto.so.10: no version information available
(required
by /usr/lib64/libssh2.so.1) /usr/bin/curl: /lib64/libcrypto.so.10: no
version information available (required
by /usr/lib64/libssl.so.10) /usr/bin/curl: relocation
error:
Sam Varshavchik writes:
systemctl start named-chroot.service hangs for a minute, or so.
ps shows that named is running, but systemctl is trying to execute the
following:
root 2036 2035 0 09:53 pts/000:00:00 /usr/bin/systemd-tty-ask-
password-agent --watch
Follow-up, I don't
Allegedly, on or about 04 July 2013, Juan Orti Alcaine sent:
Another good option if everything else fails (and you have configured
previously kernel.sysrq=1 with sysctl) is:
Alt+SysRq+ {R, E, I, S, U, B}
See: https://en.wikipedia.org/wiki/Magic_SysRq_key#Uses
Would you expect this to
27 matches
Mail list logo
