search for: heinous

Displaying 20 results from an estimated 48 matches for "heinous".

2006 May 05
2
dovecot LDA w/virtual domains and postfix
..._maps = ldap:/etc/postfix/ldap-mailbox.cf virtual_mailbox_domains = ldap:/etc/postfix/ldap-vdoms.cf virtual_uid_maps = static:1015 virtual_gid_maps = static:12 home_mailbox = Maildir/ and in dovecot.conf: protocols = imap imaps pop3 pop3s ssl_disable = no ssl_cert_file = /etc/ssl/certs/sauerkraut.heinous.org.crt ssl_key_file = /etc/ssl/private/sauerkraut.heinous.org.key mail_extra_groups = mail valid_chroot_dirs = /var/vmail/domains default_mail_env = maildir:/var/vmail/domains/%d/%n/mail protocol lda { postmaster_address = postmaster at frauerpower.com } protocol imap { } protocol pop3 { } auth...
2006 Jan 17
2
money data types
...ce, I''m not so sure that using two integer fields for each amount would qualify as uncomplicated. I''d like to be able to use database functions like SUM to retrieve totals, so I don''t want to have to split this information off or make it so normalized that queries become heinous. Sorry if this issue has been discussed on the rails forum before but I couldn''t find much when I searched the archives. Carl
2010 Oct 13
1
[PATCH]: pyxl: fix build of python xl binding for python < 2.5
The python C API introduced Py_ssize_t in version 2.5. Prior to this int''s were used instead. Fix the build by way of a heinous preprocessor macro. diff -r 38ad3633ecaf tools/python/xen/lowlevel/xl/xl.c --- a/tools/python/xen/lowlevel/xl/xl.c Wed Oct 13 12:01:30 2010 +0100 +++ b/tools/python/xen/lowlevel/xl/xl.c Wed Oct 13 17:51:44 2010 +0100 @@ -51,6 +51,10 @@ #define CLS "ctx" +#if PY_MAJOR_VERSION < 2...
2001 Aug 09
2
tag specifications
Hello all, I'm committing the heinous crime of posting before I've been on a list for very long, and I apologize in advance. I don't know how often this comes up and if it has recently if someone will just point me to an archive where this discussion has already happened, I'll shut up. I've got an MP3 tagger (QTa...
2013 Dec 05
3
[LLVMdev] Loads moving across barriers
...it makes more sense for it to be a memfence attribute rather than a nomemfence. You would then have an arbitrary number of memfence(N) attributes for each required address space. > So for correctness, would we need to tag all functions with memfence(0..M) until we can prove otherwise? That seem heinous. I was thinking the absence of it would mean no memfence in any address space, which is the current behavior. This adds the option of fencing. > Better to have an optional attribute that can be added to expose optimization. Is it important in practice to optimize the case of memfence(I) + nomem...
2013 Dec 05
0
[LLVMdev] Loads moving across barriers
..., so it makes more sense for it to be a memfence attribute rather than a nomemfence. You would then have an arbitrary number of memfence(N) attributes for each required address space. So for correctness, would we need to tag all functions with memfence(0..M) until we can prove otherwise? That seem heinous. Better to have an optional attribute that can be added to expose optimization. Is it important in practice to optimize the case of memfence(I) + nomemfence(J)? If so, is there a problem with nomemfence(N)? -Andy
2005 Sep 29
2
[BUG] Quick Fix for SCGI leaked DB connections
...m by telling AR to store it''s DB connections in a different place. Normally it stores them in Thread.current[''active_connections''] which means that, in single threaded operation you don''t really get threaded_connections, and in multi-threaded operation you get a heinous number of connections. === Implications === Since scgi_rails runs Rails inside a Synchronize block, you are *sort of* getting sequential operation. The way AR uses Thread.current though means that if you want multiple threads to do your work, then AR is actually going to cause this exact leak pro...
2013 Dec 05
0
[LLVMdev] Loads moving across barriers
...makes more sense for it to be a memfence attribute rather than a nomemfence. You would then have an arbitrary number of memfence(N) attributes for each required address space. >> So for correctness, would we need to tag all functions with memfence(0..M) until we can prove otherwise? That seem heinous. > I was thinking the absence of it would mean no memfence in any address space, which is the current behavior. This adds the option of fencing. >> Better to have an optional attribute that can be added to expose optimization. Is it important in practice to optimize the case of memfence(I)...
2013 Dec 04
2
[LLVMdev] Loads moving across barriers
On 11/11/2013 03:13 PM, Andrew Trick wrote: > On Nov 9, 2013, at 1:39 PM, Matt Arsenault <arsenm2 at gmail.com> wrote: > >> On Nov 9, 2013, at 3:14 AM, Chandler Carruth <chandlerc at google.com> wrote: >> >>> Perhaps you're instead trying to say that with certain address spaces "noalias" (and by inference, "restrict" at the language
2013 Nov 18
2
[LLVMdev] bit code file incompatibility due to debug info changes
...t; correctness) due to compile time costs, but if the verification is fast > enough to be "always on", then cool. Agreed, it's not really that fast either. The problem with versions is that it makes small changes that only require a bit of modification to the testcase to be pretty heinous upgrade paths and a lot of work - you can see that from the work any of us have had to do when changing the format. We'd like to keep the testcases and upgrade those as well because otherwise we're just dropping testcases like mad constantly. It's a lot of work, but the format has been...
2006 Jan 18
4
Ruby "htmlentities" replacement: code review please!
...command should be at least as good as PHP''s htmlentities command for most Western alphabet users... I hope! :-) So, any comments? Feel free to use the code anywhere you like, but possibly just wait until a few other folks have looked it over, just in case there''s something heinously wrong with it! It comes with no guarantee of suitability for any purpose whatsoever, and you use it entirely at your own risk. Regardless, if folks think it''s useful, I''ll put it online somewhere more permanent than RAFB NoPaste! Cheers, ~Dave -- Dave Silvester Rent-A-M...
2013 Dec 21
2
[LLVMdev] Loads moving across barriers
...s more sense for it to be a memfence attribute rather than a nomemfence. You would then have an arbitrary number of memfence(N) attributes for each required address space. >>> So for correctness, would we need to tag all functions with memfence(0..M) until we can prove otherwise? That seem heinous. >> I was thinking the absence of it would mean no memfence in any address space, which is the current behavior. This adds the option of fencing. >>> Better to have an optional attribute that can be added to expose optimization. Is it important in practice to optimize the case of mem...
2008 Feb 22
0
Postfix on one host/Dovecot (mailboxes) on another - How?
Hi, I'm using Dovecot 1.0.5 on OpenSUSE 10.3. I run postfix/amavis/clamav on one host, postfix uses LDAP to identify whether or not users exist. On this same machine I was running dovecot, so I used dovecot LDA on Postfix master.cf (as mentioned on http://heinous.org/wiki/Virtual_Domains,_Postfix,_Dovecot_LDA,_and_LDAP#Postfix). Now I want to run Dovecot on another machine, how should I configure postfix on that first machine? first machine: the domain my users know/use; webmail; postfix/amavis/clamav; mx record for domain all users have mail addresses;...
2005 Jul 13
2
RPM Autorollback
Hi, any idea if (when?) a new version of those RPMs with rollback included will become available for CentOS 4? Thanks, MaZe.
2012 Sep 17
1
dovecot 1.x: problem with quota
...as being delivered like normal to my mailbox, but doesn't show up there. After poking around, I decided to simply delete the maildirsize file and have the client send that email again, and voila, it shows up in my mailbox. At the same time, however, other emails get delivered just fine, so the heinous thing is that you don't immediately notice that something fishy is going on - only when the client actually calls you (sort of defeats some uses of email)... The problem is worsened by the fact that you can't tell *which* emails get lost - you only end up with a random subset of "your&...
2004 Apr 21
10
mythical 1.0
Any chance of incrementing the ol'' version number a bit more aggressively? Doing so could really help wxRuby adoption if done right: http://fishbowl.pastiche.org/2003/07/28/version_numbers_and_you -- Ryan "John" Platte Custom services, NIKA Consulting http://nikaconsulting.com/
2004 Jan 23
2
echo problems
New complile causing trouble... How do you enable MARK2 echo can with DAGGRESSIVE_ SUPPRESSION? looks like zconfig.h ..but I have quite a bit of echo on a bridgeded call and echocancelwhenbridged=no John ------------------------------------------------------ This message was sent using Monroe-Woodbury's WebMail. http://webmail.mw.k12.ny.us/ This e-mail was scanned and found clean by
2013 Nov 18
0
[LLVMdev] bit code file incompatibility due to debug info changes
On Mon, Nov 18, 2013 at 10:35 AM, Eric Christopher <echristo at gmail.com>wrote: > >> At a minimum, it seems like we need a version number in the debug info > >> metadata so we can detect this situation and avoid crashing. > > > > > > Or to put it in the terms of the IR: we need to autoupgrade the debug > info > > metadata just like we do
2006 Jun 07
10
habtm "AND" find conditions
I have two tables and a join table for them e.g. books, authors in a many to many relationship (habtm) and a join table books_authors. I can successfully search for a book that has "author.id = 2 OR author.id = 4" but I am unable to search for "author.id = 2 AND author.id = 4" This is because the result of all the joins only has one author.id column so no single row has
2013 Nov 18
2
[LLVMdev] bit code file incompatibility due to debug info changes
>> >> At a minimum, it seems like we need a version number in the debug info >> metadata so we can detect this situation and avoid crashing. > > > Or to put it in the terms of the IR: we need to autoupgrade the debug info > metadata just like we do intrinsics. With debug info this might (at the > worst) involve dropping old metadata. > The verifier is probably