On 2013-06-22, William Orr wrote:
> I currently have an untested (I'm going to spin up some EC2 instances to
> do testing this weekend) start on a port to linux on GitHub:
> https://github.com/worr/spamd
>
> So my questions:
> Is there anything else I need to do to make sure that I'm kosher with
On 2013-06-22, Kenneth R Westerback wrote:
> On Sat, Jun 22, 2013 at 10:21:10AM +1000, John Tate wrote:
>> I have an Atheros AR9227, there is at the moment no support for
>> 802.11n in the patch branch. Is there support in current or some
>> unoffical patch I can apply to the source code? Support
Btw, if anyone feels the need to reply, don't include misc@. We are not
interested.
On Sat, Jun 22, 2013 at 7:08 AM, Peter J. Philipp wrote:
> It's all over the news (BBC, ARD) that there is floods in Calgary. And I'm
> wondering if the OpenBSD servers are affected since they are in a basement
> afaik. Is the physical location secure from these floods?
Yes, it's secure from th
Hello,
I'm a mail administrator for a student group at my alma mater, RIT.
We're not particularly satisfied with our current greylisting software
(gld), and the best alternative (hell, the best greylisting software,
hands down) is spamd.
Unfortunately, none of the other sysadmins want to mai
GCC 4.3: sched.c line 572: Error: PC Load Letter.
Theo De Raadt stared at his screen. Another glitch, another delay. The next
version of OpenBSD, 4.4, was due for release a week ago, and he was still
not ready. Just another reason for a jerkoff with a DSL connection and an
IRC
client to think tha
It's all over the news (BBC, ARD) that there is floods in Calgary. And I'm
wondering if the OpenBSD servers are affected since they are in a basement
afaik. Is the physical location secure from these floods?
Regards,
-peter
On 31/01/12 16:39, Kapetanakis Giannis wrote:
Ok I'll try dmesg from ddb if that happens again.
Bad luck my dmesg is not saved through reboots, otherwise I would give
this info now...
thanx
Giannis
Hi,
I got this again after upgrading to 5.3 (two weeks ago) although I don't
think it's
Josh Hoppes wrote:
> I've run into this issue as well in past versions. Set this in
> /etc/sysctl.conf
> kern.timecounter.hardware=acpitimer0
Yes, that's the sysctl I've adjusted, too.
The one I mentioned earlier is not correct. I think I only used it to get valid
values to set for "kern.timecoun
9 matches
Mail list logo