ADD ANOTHER GATEWAY TO SCO OPENSERVER 5

[Justino]

Hello:

I need to add another permanent gateway to my SCO Openserver 5. I added the
following line in the "/etc/inetd.conf":

route add 128.24.100.1 128.23.0.52

This line doesn´t work when i reboot the system. It works when I type it at
the command window (prompt), but at this way it isn´t permanent, when I
reboot the system this gateway isn´t in the system.

Thanks for all.

[Jean-Pierre Radley]

Justino propounded (on Mon, Nov 06, 2000 at 01:09:23PM +0100):

| Hello:
|
| I need to add another permanent gateway to my SCO Openserver 5. I added the
| following line in the "/etc/inetd.conf":
|
| route add 128.24.100.1 128.23.0.52
|

| This line doesn4t work when i reboot the system. It works when I type it at
| the command window (prompt), but at this way it isn4t permanent, when I
| reboot the system this gateway isn4t in the system.
|
| Thanks for all.

Leave /etc/inetd.conf alone, it's for configuring the actions of inetd,
not for adding routes.

Put your statement in whatever rc2.d script is already adding your
default route for you.

--
JP

[Tony Lawrence]

Justino wrote:
>
> Hello:
>
> I need to add another permanent gateway to my SCO Openserver 5. I added the
> following line in the "/etc/inetd.conf":
>
> route add 128.24.100.1 128.23.0.52
>

> This line doesn´t work when i reboot the system. It works when I type it at
> the command window (prompt), but at this way it isn´t permanent, when I
> reboot the system this gateway isn´t in the system.

See http://aplawrence.com/SCOFAQ/scotec4.html#defaultroute for
the various possibilities..

--
Tony Lawrence (to...@aplawrence.com)
SCO/Linux articles, help, book reviews, tests,
job listings and more : http://www.pcunix.com

[Rob Servis]

If I were a sendmail guru, I wouldn't have to ask this ... since I'm not,
maybe someone out there can answer.

2 things I've noticed about aliases for virtual domains on SCO5.0.x:

1. Unlike normal aliases - you cannot specify multiple recipients on the
alias.
2. Unlike other sendmail implementations on Linux, FreeBSD, etc. that use
/etc/mail/domainalias to do aliases, you cannot specify a wildcard forward
for all names at a particular domain.

The sendmail.cf code as it exists for virtual domains on 5.0.5 looks like
this:

# handle virtual aliases
R$+ < @ $+ . > $: $1 < @ $2 > .
R$+ < @ $+ > $* $: $(valiases $1@$2 $: $1 < @ $2 > $3 $)
R$+ < @ $+ > $* $: $(valiases $2 $: $1 < @ $2 > $3 $)
R$+ < @ $+ > . $: $1 < @ $2 . >

What would have to change support 1 & 2.

[David Mabo]

Rob Servis wrote:
>
> If I were a sendmail guru, I wouldn't have to ask this ... since I'm not,
> maybe someone out there can answer.
>
> 2 things I've noticed about aliases for virtual domains on SCO5.0.x:
>
> 1. Unlike normal aliases - you cannot specify multiple recipients on the
> alias.

I can answer this - it takes 2 forwards - one to a machine name, and
then that can do the multiple forwards:

virtual entry:

x...@domain1.com li...@domain2.com

aliases

list: user1,user2,user3

> 2. Unlike other sendmail implementations on Linux, FreeBSD, etc. that use
> /etc/mail/domainalias to do aliases, you cannot specify a wildcard forward
> for all names at a particular domain.
>
> The sendmail.cf code as it exists for virtual domains on 5.0.5 looks like
> this:
>
> # handle virtual aliases
> R$+ < @ $+ . > $: $1 < @ $2 > .
> R$+ < @ $+ > $* $: $(valiases $1@$2 $: $1 < @ $2 > $3 $)
> R$+ < @ $+ > $* $: $(valiases $2 $: $1 < @ $2 > $3 $)
> R$+ < @ $+ > . $: $1 < @ $2 . >
>
> What would have to change support 1 & 2.

--
David H. Mabo, CPCM
Adaptix Corp. - Cincinnati, Ohio

[Bill Vermillion]

In article <3A0A329E...@adptx.com>, David Mabo <dm...@adptx.com> wrote:
>
>
>Rob Servis wrote:

>> If I were a sendmail guru, I wouldn't have to ask this ... since
>> I'm not, maybe someone out there can answer.

>> 2 things I've noticed about aliases for virtual domains on
>> SCO5.0.x:

>> 1. Unlike normal aliases - you cannot specify multiple recipients
>> on the alias.

>I can answer this - it takes 2 forwards - one to a machine name, and
>then that can do the multiple forwards:

>virtual entry:

>x...@domain1.com li...@domain2.com

>aliases

>list: user1,user2,user3

Of course there are so many ways to do thing in Unix, you can use
the virtualuserable with the x...@domain.com and make
that a virtual user on the machine where this resides and
then in a real user entry put in the forward file:

\us...@domain2.com
\someo...@anotherdomain.com
...

Using the latter you could allow the person responsible for the
other domain to login as the user on you system and edit their
forward files so you wouldn't have to be bothered if changes were
made. I only use aliases anymore for the standard postmaster,
abuse, system, etc.

--
Bill Vermillion - bv @ wjv . com