similar to: Regular point pattern on multi-segment line

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, ~ I am doing a test install for Samba 3.0.0 with ldap sam backend, when I try to delete a user, I get this output # smbpasswd -x administrator ldapsam_delete_entry: Could not delete attributes for uid=administrator,ou=Users,dc=my-domain,dc=com, error: Object class violation (object class 'account' requires attribute 'uid')

Hi, Hi I'm using redhat 9 I've got samba working and I have users onj the system accessing the shares, Can anyone recomend a programme that can tell me whch users have got files open on my samba box Thanks ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Iwan Davies Server Support and Development Technician Cyngor Sir Ceredigion County Council IT Section Finance iwandav@ceredigion.gov.uk

Hi all I am missing something on the the pop3 "leave messages" rationale. Although the UIDL feature solves for the MUA the problem "whch mails should be downloaded", how the duration that these mails should be kept on server, say 10 days for one MUA and 20 days for another MUA for the same account, is resolved on the server? thanks in advance -- ????????? ???????????

Hi, With this route... map.namespace :admin do |admin| admin.sort ''/:controller/sort/:sort_by/:sort_dir'', :action => ''sort'' end ...I get this message... Route segment ":controller" cannot be optional because it precedes a required segment. This segment will be required. The route works as expected, but the warning is worrying. Any ideas?

Hello. Can someone please help me read this error log located in the log folder? [ displays ''ESC'' in my editor, but did not display in this copy and paste. so i''m wondering what that means too.. Session ID: cefa85a414c483d345b4e2fd5ce9449c / ^ just the session id / Parameters: {"action"=>"index",

By randomization of functions I mean the manner in whch they are called , so that has to do with address.I wish to randomize the order of calls made to functions when a program is run. Reid Spencer <reid at x10sys.com> wrote:Can you explain a little bit more about what you mean by "randomize" functions or global variables? What aspect of them do you want to randomize? Their

Hi all, I''m using ferret and acts_as_ferret on Win XP. Trying to index a location table with over 2,5 Mio. rows in UTF-8 I''m getting the error: "IO Error: IO Error occured: Error reading the segment infos. Store listing was ..." The error occurs after some hours of running. The index file system looks like this after the abort: 11.08.2007 12:30 <DIR>

Move PnP BIOS segment definitions into segment.h; the segments are reserved here, so they might as well be defined here as well. Note I didn't do this for APM BIOS, as Macintosh and other systems use those values to emulate APM in some scary way I don't want to understand. Signed-off-by: Zachary Amsden <zach@vmware.com> Index: linux-2.6.14-zach-work/include/asm-i386/segment.h

It is impossible to have a zero length segment in descriptor tables using "normal" segments. One of many ways to properly protect segments to zero length is to map the base to an umapped page. Create a nicer way to do this, and stop subtracting 1 from the length passed to set_limit (note calling set limit with a zero limit does something very bad! - not anymore). Signed-off-by:

Use prepare_protected_segment macro to set up the 16-bit stack. Whee!! This code is almost readable now. Signed-off-by: Zachary Amsden <zach@vmware.com> Index: linux-2.6.14-zach-work/arch/i386/kernel/cpu/common.c =================================================================== --- linux-2.6.14-zach-work.orig/arch/i386/kernel/cpu/common.c 2005-11-04 16:54:45.000000000 -0800 +++

Hi, I found the aggregated IO speed is only about 100MB/s on 4 Giga-bit Brick. This test is done over 12 computing nodes with command dd if=/dev/zero of=bar bs=1048576 count=20480. Because our brick has very fast local IO speed, the problem could be network. Then I found computing nodes got too many retransmited segments during test according to netstat -st. The retransmission ratio is

I''ve seen this happen before, not sure why. I changed ''phy:'' to ''file:'' and it worked. I later rebooted and ''phy:'' worked again. So you might try ''file:'' rather than ''phy:''. -- Ray -----Original Message----- From: xen-users-bounces@lists.xensource.com

# HG changeset patch # User Paul Durrant <paul.durrant@citrix.com> # Date 1322574403 0 # Node ID 51692288a6e84c941f9e5049c73b7246bab97f70 # Parent e1e952982cf1d7a0c38a7822a8b5e78ba04b5ba5 Fix hvmloader xenbus segment array length. c/s acc408d667e1 had this one too short for handling a write. This incremental patch rectifies the problem. Signed-off-by: Paul Durrant

Hello, I need to draw a vertical line on my plot, the uncertainty segment (which is a vertical segment on every point of my plot so I can have an idea about the probability that a point is misclassified.... clustering problem.....) I remember I have done it a long time ago in Splus using a function called "segment" to which we give the extrem point of the segment , I didn't find

Move PnP BIOS segment definitions into segment.h; the segments are reserved here, so they might as well be defined here as well. Note I didn't do this for APM BIOS, as Macintosh and other systems use those values to emulate APM in some scary way I don't want to understand. Signed-off-by: Zachary Amsden <zach@vmware.com> Index: linux-2.6.14-zach-work/include/asm-i386/segment.h

It is impossible to have a zero length segment in descriptor tables using "normal" segments. One of many ways to properly protect segments to zero length is to map the base to an umapped page. Create a nicer way to do this, and stop subtracting 1 from the length passed to set_limit (note calling set limit with a zero limit does something very bad! - not anymore). Signed-off-by:

Use prepare_protected_segment macro to set up the 16-bit stack. Whee!! This code is almost readable now. Signed-off-by: Zachary Amsden <zach@vmware.com> Index: linux-2.6.14-zach-work/arch/i386/kernel/cpu/common.c =================================================================== --- linux-2.6.14-zach-work.orig/arch/i386/kernel/cpu/common.c 2005-11-04 16:54:45.000000000 -0800 +++

Hi, In this patch, I unify segment_32.h and segment_64.h into segment.h They have some common parts, but a considerable ammount of code still has to be around ifdefs. The only patch that is really important to paravirt is the first one, that moves a paravirt definition into the common header. The other two are just normal integration, and pretty much independent

Hi, In this patch, I unify segment_32.h and segment_64.h into segment.h They have some common parts, but a considerable ammount of code still has to be around ifdefs. The only patch that is really important to paravirt is the first one, that moves a paravirt definition into the common header. The other two are just normal integration, and pretty much independent

__set_tss_desc has a complex calculation of the TSS segment limit, duplicating the quirky details of the I/O bitmap array length, and requiring a complex comment to explain. Replace that calculation with a simpler one based on the offsetof the "stack" field that follows the array. That then removes the last use of IO_BITMAP_OFFSET, so delete it. Signed-off-by: Josh Triplett <josh