headers
ober | 1 Nov 2005 01:04

OpenAFS Server install script for 3.8 ( was Openafs or alra Support)

Attached is the latest version of the single server OpenAFS install 
script for OpenBSD 3.8/3.7.
This was built using OpenAFS 1.3.87 configured with
./configure --enable-transarc-paths --with-afs-sysname=i386_obsd37
I believe on 3.8 I had to copy over the /usr/include/ufs/extattr.h from 
a 3.7 box in order to get the lkm to compile.
My server start script is called start.afs and it contains what could 
merely appended to rc.securelevel and rc.

----snip start.afs------------------------
modload /usr/vice/etc/libafs.o
/usr/afs/bin/bosserver
/usr/afs/bin/afsd -stat 8000 -dcache 8000 -daemons 12 -volumes 256 
-files 50000
-----snip-------------------------------

Please feel free to send me any updates, as I hope to finish this out 
this week.

Thanks!
#!/bin/ksh

#
# Script to configure a single server OpenAFS Cell.
# This script assumes that you compiled OpenAFS with --enable-transarc-paths
# This will prompt you many times for the admin password.
#

#This is the BINDIR where afs installed it's items. 
# If you Choose --enable-transarc-paths then choose this one:
(Continue reading)

Permalink | Reply | 0 comments |
headers
John Brahy | 1 Nov 2005 01:14
Gravatar

Re: perl script for postfix logs to create spamd tables

> Does anyone have a script that parses postfix logs and adds servers to 
> the spamd tables?

I do use and love spamd, but what I want to accomplish is to add servers
that are attempting dictionary attacks and such into the spamd tables. 

Someone else emailed me directly and mentioned adding servers that I send
outgoing emails to, to a whitelist which I like also. 

-----Original Message-----
From: owner-misc <at> openbsd.org [mailto:owner-misc <at> openbsd.org] On Behalf Of
Chad M Stewart
Sent: Monday, October 31, 2005 2:56 PM
To: John N. Brahy
Cc: misc <at> openbsd.org
Subject: Re: perl script for postfix logs to create spamd tables

Why would you want to do that?  Put spamd in front of postfix and sit  
back and watch the spammers waste their time.  Sure the first few  
hours can be trying as legitimate mail trickles through.  Before I  
deployed spamd for the first time I lowered the passtime and tested.   
Once I was satisfied that things would work as they should I put  
spamd in production.  When I started getting my misc <at>  messages again  
I knew things were working. :)

Today I got my first indication that another site is having  
problems.  A credit card company told me when I logged into their  
website that my email address was no longer valid and to please  
update.  The funny thing is that some messages from them do make it  
to me.  I look at it this way, the problem is on their end.  spamd
(Continue reading)

Permalink | Reply | 1 comment |
headers
Diego Arimany | 1 Nov 2005 03:18

Re: UKC and VGA configuration

Stuart,

>>> Consoles on i386 involve vga(4) and wscons(4), you just have text
>>> modes to choose from which probably won't help you.
>>
>>
>> I4ve tried using 'wsconscfg' to set the screen, but the text modes
>> are not much better (unless there is a stretch option).
>
>
> Yes, they're all VGA text modes for a 640x480 screen - without 
> 'stretch' in the bios, you won't get very far.

I managed to play a bit with the linux distribution in order to 
determine the parameters it passes.  If it boots (linux) with 
'vga=normal' then the display behaves exactly as it does with OBSD.  
However, if 'vga=791' is passed to the linux kernel the text screen is 
streched.  If passed like so at the boot prompt it is an illegal argument.

>> I am running X, but the screen size doesn4t improve either.
>
>
> To give full-screen output on your machine, the X server needs to run 
> at the native resolution of your LCD panel. If a simple ctrl-alt-+ 
> doesn't help, you need to determine a suitable xorg.conf mode line for 
> the native resolution of the panel - gtf(1) might help.

I will try 'Ctrl Alt +' and also will check gtf(1), then tell you what 
happened.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Shane J Pearson | 1 Nov 2005 01:39
Picon

Re: a truly openbsd day

Howdy Gareth,

On 01/11/2005, at 3:41 AM, Gareth Nelson wrote:

> I tell people of the joy of puffy everywhere I go, at the busstop I  
> shout
> "THEY CALLED IT BSD AND OPEN BECAUSE IT'S ALWAYS FREE"

And here's to Puffy Hood!

> Seriously though, I now recommend OpenBSD to everyone as a firewall/ 
> server
> system for those migrating from that redmond thing. As a desktop  
> OS, it's
> unfortunately a bit difficult to setup with everything needed by  
> the average
> desktop user who doesn't care what their OS is.

What is so difficult? Install a pkg or port, read the pkg_info for it,
do what it says. If you come across a problem: apropos, Google, MARC...
If you mean difficult as in "a little more effort" then ok, but it seems
like a small price to pay. Months ago a had to install Red Hat 9 on an
AMD XP 2800+ with 1GB RAM and a 7200RPM PATA disk, it took BLOODY AGES!
I felt like I was installing Windows XP on an old machine. OpenBSD takes
_minutes_, including getting X going. Then a little more to install the
packages I like.

> This makes me wonder - a desktop OpenBSD fork, similar to pc-bsd but
> based on FreeBSD might be a good idea.
(Continue reading)

Permalink | Reply | 12 comments |
headers
Stuart Henderson | 1 Nov 2005 02:29
Favicon
Gravatar

Re: perl script for postfix logs to create spamd tables

--On 31 October 2005 16:14 -0800, John Brahy wrote:

>> Does anyone have a script that parses postfix logs and adds servers
>> to  the spamd tables?
>
> I do use and love spamd, but what I want to accomplish is to add
> servers that are attempting dictionary attacks and such into the
> spamd tables.

See spamd(8), search for GREYTRAP (you might need 3.8, I don't 
remember, it's been a while since 3.7..) This works very very well.

> Someone else emailed me directly and mentioned adding servers that I
> send outgoing emails to, to a whitelist which I like also.

See spamlogd(8), as ref'd by spamd(8). that's definitely been in for a 
while, and the commented-out entry in rc.conf should give clues about 
it's use...
Permalink | Reply | 0 comments |
headers
Ted Unangst | 1 Nov 2005 02:30
Picon

Re: Enhanced Speed Step Technology

On 10/31/05, Per-Olov Sjvholm <pos <at> incedo.org> wrote:
> Hi
>
> Can OpenBSD handle "Enhanced Speed Step Technology" of the processor if it's
> set to "enabled" in the computer bios?

on the earlier chips yes.  some of the newer chips aren't supported
because of the way the tables are currently laid out.

> This is what Dell says in the server manuals about enabling this feature in
> bios:
> --snip--
> NOTICE: Before enabling the Speed Step option, ensure that the operating
> system also supports Enhanced Speed Step Technology. Enabling the feature on
> operating systems that do not support it may cause unpredictable results. See
> the operating system's documentation for its supported features.
> --snip--

that seems strange to me, i can't imagine any problem enabling it.
Permalink | Reply | 1 comment |
headers
Joe Barnett | 1 Nov 2005 01:54
Favicon

log file for OpenNTPD (on FreeBSD)

To which file does OpenNTPD log on a FreeBSD machine?

Specifically, I am referring to (i386) machines running both FreeBSD 
versions 4.7 and 5.4.  OpenNTPD is version 3.7p1 (I have tried both 
installing directly from source, and from [FreeBSD] ports).

On my OpenBSD machines OpenNTPD logs to /var/log/daemon.  And on my 
Linux machines OpenNTPD logs to /var/log/messages.  But I cannot 
find the file to which it logs on the above mentioned FreeBSD 
machines.  Bear in mind that all indicators are that it is working 
very well on FreeBSD, I simply am not able to find the logs.

I have checked the archives and have not found much about this...

Thanks,

Joe
Permalink | Reply | 2 comments |
headers
Darren Tucker | 1 Nov 2005 03:15
Picon
Picon

Re: log file for OpenNTPD (on FreeBSD)

On Mon, Oct 31, 2005 at 05:54:18PM -0700, Joe Barnett wrote:
> To which file does OpenNTPD log on a FreeBSD machine?

It logs to the syslog "daemon" facility, so it will end up in whichever
log file your syslogd is configured to put them.  (This may be "nowhere"
if that's how your syslogd is configured.)

Should probably mention that in the man page...

--

-- 
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
    Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.
Permalink | Reply | 0 comments |
headers
Darren Tucker | 1 Nov 2005 03:16
Picon
Picon

Re: OpenNTP and leap seconds

On Mon, Oct 31, 2005 at 03:21:13PM -0500, Will H. Backman wrote:
> Just curious if OpenNTP supports leap seconds.
> I have read that Jan 2006 will include one.

3.8 recognises leap second flags from its servers and will propogate them
to its clients.  It currently doesn't do anything special on the kernel
side, though.

--

-- 
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
    Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.
Permalink | Reply | 0 comments |
headers
Stuart Henderson | 1 Nov 2005 03:20
Favicon
Gravatar

Re: log file for OpenNTPD (on FreeBSD)

--On 31 October 2005 17:54 -0700, Joe Barnett wrote:

> To which file does OpenNTPD log on a FreeBSD machine?

check your syslog.conf to see where daemon.info is sent.
Permalink | Reply | 0 comments |

Gmane