Displaying 9 results from an estimated 9 matches for "dozend".
Did you mean:
dozens
2005 May 04
1
Avoiding Sweave formula cut's?
...i could avoid less nicely cut's in
function calls with sweave like:
randomForest(x = RELSHIP ~ ., data = R_RELSHIP[splitR_RELSHIP == 1,
], importance = T, n(*here is the cut in the pdf*)
tree = 1000, na.action = na.omit)
Until now i add expost linebreaks in the *.tex file, but with dozend of
models it might be painfuel for my hands.
Many thanks & regards,
Christian
2006 Feb 17
1
index file vs. memory
Hello,
we have a large base of mailbox users and while pop3-connections are
usually closed after the download of all mails, I noticed hundrets of
imap-connections kept idle by the users. This is surely according to the
idea behind imap, but I'm a bit afraid of overwhelming memory
consumption if there are too many imap-connections opened at the same
time. Is the index file kept in memory
2016 May 02
0
Strange ID-Mapping behavior
In my case flushing the cache did not help. I had around an dozend of
user accounts with uidNumbers assigned and left over (dynamic winbind)
mappings in idmap.ldb. At first after an flush samba used the uidNumber
but after an logoff/logon of the userd getent passwd [user] showed the
mapping from idmap.ldb. After i deleted the mapping in idmap.ldb
everythiing...
2018 Jan 22
0
[Patches] AD Database corruption after upgrade from <= 4.6 to 4.7 (bug #13228)
...eck --fix. Till now no group corruption had happened.
I can think of restoring an backup from 11.01.2018 to an vm with 4.7.4
here to inspect the errors from dbcheck again and maybe recreate these
deleted links again. As far as i remember the errors where different on
the ad's of whom i run a dozend, so this may become complicated.
I assume the errors caused by the 4.6.8->4.7.3 update happened 30 days
later and I fixed these by recreating the affected groups. But i'm
unsure if the fixes i ran after the 4.7.3->4.7.4 update may cause
another corruption on 11.02.2018. dbcheck --cros...
2007 Aug 28
1
(slightly OT) syncing / migrating IMAP mailboxes
...looked like the only program
which worked, but seems to have "forgotten" the missing messages. Another
extremely suspicious thing is that mailsync reports "phantom changes" if
run again immediately after synching a folder and will start to delete
and copy / "sync" dozends of messages even if none of the folders
actually changed after synching.
I've read the name "imapsync" on this list several times, but I just tried
it and just tried version 1.219. It happily starts synching the mailboxes
and copying messages, but stops after partially synching t...
2016 May 02
4
Strange ID-Mapping behavior
Hey,
id mapping is accessible from net command:
net cache list
you can also clean that cache:
net cache flush
After flushing the cache your users and groups having uidNumber and/or
gidNumber should work as expected (ie using their AD declared uid/gid).
Cheers,
mathias
2016-05-02 15:18 GMT+02:00 Achim Gottinger <achim at ag-web.biz>:
> Sounds like there is an old entry in idmap.ldb.
2018 Jan 22
2
[Patches] AD Database corruption after upgrade from <= 4.6 to 4.7 (bug #13228)
On Mon, Jan 22, 2018 at 05:24:44PM +0100, Achim Gottinger via samba wrote:
> Am 22.01.2018 um 10:49 schrieb Stefan Metzmacher via samba:
> > Also DO NOT repair the following errors with samba-tool dbcheck!
> > "Remove duplicate links in attribute"
> > and
> > "ERROR: orphaned backlink"
> > as this removes the ability to repair the database
>
2014 Jan 03
7
[Bug 73267] New: Nouveau: corrupted laptop screen's EDID info
https://bugs.freedesktop.org/show_bug.cgi?id=73267
Priority: medium
Bug ID: 73267
Assignee: nouveau at lists.freedesktop.org
Summary: Nouveau: corrupted laptop screen's EDID info
QA Contact: xorg-team at lists.x.org
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: ezelspinguin at
2006 Oct 01
4
HEADS UP: FreeBSD 5.3, 5.4, 6.0 EoLs coming soon
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello Everyone,
On October 31st, FreeBSD 5.3 and FreeBSD 5.4 will have reached their
End of Life and will no longer be supported by the FreeBSD Security
Team. Users of either of those FreeBSD releases are strongly encouraged
to upgrade to FreeBSD 5.5 or FreeBSD 6.1 before that date.
In addition, the FreeBSD 6.0 End of Life is presently scheduled