inn-2.2.1 on OpenBSD-2.5

Yutaka KAWASE yutaka at mailhost.net
Sat Apr 1 09:42:40 UTC 2000


Hello,

I checked the shell used in OpenBSD-2.5 and I think here is the answer.

KSH_VERSION='@(#)PD KSH v5.2.13.7 99/01/15'


-- 
Yutaka KAWASE <yutaka at oneill.co.jp>


-- Original Message --
From: Russ Allbery <rra at stanford.edu>
Subject: Re: inn-2.2.1 on OpenBSD-2.5
Date: 30 Mar 2000 01:04:17 -0800
Message-ID: <yl66u4omlq.fsf at windlord.stanford.edu>

> Yutaka KAWASE <yutaka at mailhost.net> writes:
> 
> > On slackware, it accepts control message of newgroup. However, OpenBSD
> > doesn't. Instead, it gives me a mail "Unparseable newgroup by
> > me at my.home".
> 
> > On the OpenBSD machine I edited the first line of ~/bin/control/newgroup
> > as
> 
> > #!/usr/local/bin/bash
> 
> > which was originally,
> 
> > #!/bin/sh
> 
> > Then the things are fine now. ;-)
> 
> > Is this a problem with porting?
> 
> It sounds to me like a bug in whatever OpenBSD uses as /bin/sh (I assume
> it isn't bash like it tends to be on Linux).  I've not seen this bug
> before, though, and I'm guessing it would require some work by someone to
> figure out what's going on that's not working right and narrowing it down
> to some specific shell expressions.
> 
> The error message points to this part of newgroup:
> 
> ##  Valid parameters and group name?
> case "$#" in
> 1|2)
>     ;;
> *)
>     ${SM} ${ARTICLE} | ${WRITELOG} ${LOGFILE} "Unparseable newgroup by ${FROM}"
>     exit
>     ;;
> esac
> 
> Maybe $# is getting set to the wrong thing somehow?
> 
> -- 
> Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>



More information about the inn-workers mailing list