installing a CSO server

[Thomas Foks]

Is there anybody out there who could tell me how to install a CSO server?
What I did so far is compiling the qi daemon (verison 2.2) on a SPARCstation 1
and installing the binaries (i hope in the correct places). The server itself
seemed to work fine and is started via inetd.
But now my troubles begin:
1.) How to build a initial database with only one entry (the superuser)?
2.) How do I get into hero/superruser mode?
2.) How do I assign aliases and passwords?
As a conclusion: how do I fill a database or set it up for filling?

Thanks in advance,
Thomas

---
Thomas Foks Phone: +49-209-1707-229 (Mon+Fri)
Institut Arbeit und Technik e-mail (Internet):
Florast.26-28 fo...@trick.iatge.de
D-45879 Gelsenkirchen Germany

[Noel Hunter]

Thomas Foks (fo...@iatge.de) wrote:
: Is there anybody out there who could tell me how to install a CSO server?

: What I did so far is compiling the qi daemon (verison 2.2) on a SPARCstation 1
: and installing the binaries (i hope in the correct places). The server itself
: seemed to work fine and is started via inetd.
: But now my troubles begin:
: 1.) How to build a initial database with only one entry (the superuser)?

Here's a script, compiled from various contributions to the list, to
build a qi database:

#!/bin/sh
echo "stop building new database" >prod.sta

# Delete old database
rm -f prod.bdx prod.dir prod.dov prod.idx prod.iov prod.lck prod.seq
ls -la
# Figure size for new database
prod* size=`./sizedb prod.cnf qi.input`

# Create new database
./credb $size prod
./maked prod <qi.input
./makei prod
./build -s prod
rm prod.sta

There's also a listserv for ph questions:

inf...@ux1.cso.uiuc.edu

Hope this helps.

* Noel Hunter, Academic Systems Administrator, Wake Forest University *
* no...@wfu.edu TEL:(919) 759-5812 MAIL:PO Box 7408 Winston-Salem, NC 27109 *

[Thomas Foks]

In article i...@quad.wfunet.wfu.edu, no...@ac.wfu.edu (Noel Hunter) writes:
>Here's a script, compiled from various contributions to the list, to
>build a qi database:
>
>#!/bin/sh
>echo "stop building new database" >prod.sta
>
># Delete old database
>rm -f prod.bdx prod.dir prod.dov prod.idx prod.iov prod.lck prod.seq
>ls -la

Why this. I guess this is senseless.

># Figure size for new database
>prod* size=`./sizedb prod.cnf qi.input`

I guess the correct line is:
size=`./sizedb prod.cnf qi.input`

>
># Create new database
>../credb $size prod
>../maked prod <qi.input
>../makei prod
>../build -s prod
>rm prod.sta

Ok. That sounds good but what about the file qi.input. I guess that file
should contain the initial information. But how is this file structured?

[Noel Hunter]

Thomas Foks (fo...@iatge.de) wrote:

: In article i...@quad.wfunet.wfu.edu, no...@ac.wfu.edu (Noel Hunter) writes:
: >Here's a script, compiled from various contributions to the list, to
: >build a qi database:
: >
: >#!/bin/sh
: >echo "stop building new database" >prod.sta
: >
: ># Delete old database
: >rm -f prod.bdx prod.dir prod.dov prod.idx prod.iov prod.lck prod.seq
: >ls -la

: Why this. I guess this is senseless.

I guess maybe for debugging? To show the files and persissions. It can
of course be taken out.

: ># Figure size for new database

: >prod* size=`./sizedb prod.cnf qi.input`

: I guess the correct line is:
: size=`./sizedb prod.cnf qi.input`

You are correct. This step can be omitted entirely if you want to figure out
the size yourself.

: >
: ># Create new database

: >../credb $size prod
: >../maked prod <qi.input
: >../makei prod
: >../build -s prod
: >rm prod.sta

: Ok. That sounds good but what about the file qi.input. I guess that file
: should contain the initial information. But how is this file structured?

It's a tab-delimited text file in the format:

fieldno:fielddata/t fieldno:fieldaata.../r

You might also want to add a chmod at the end, to fix file permissions,
something like:

chmod -R o-rwx,g-rwx *

Basically, you don't want people to be able to download the database for mailing
list use.

Anyway, this is just a sample to get you started. I didn't intend for you
to run it as is. You will still need to read up on the qi stuff a bit.

Regards,
Noel

--

* Noel Hunter, Academic Systems Administrator, Wake Forest University *

* no...@wfu.edu TEL:(910) 759-5812 MAIL:PO Box 7408 Winston-Salem, NC 27109 *

[Jennifer R. Amon]

>Anyway, this is just a sample to get you started. I didn't intend for you
>to run it as is. You will still need to read up on the qi stuff a bit.

I'm another neophyte looking for info. Please point me to the info that
could be classified as CSO/QI/PH 101 material.

Thanks,
_____________________________________________________________________
Jennifer R. Amon PHONE: (216) 775-6987
Houck Computing Center FAX: (216) 775-8573
Oberlin College
Oberlin, OH 44074 INTERNET: ba...@ocvaxc.cc.oberlin.edu
_____________________________________________________________________

[Noel Hunter]

Jennifer R. Amon (ba...@ocvaxc.cc.oberlin.edu) wrote:
: >Anyway, this is just a sample to get you started. I didn't intend for you

: >to run it as is. You will still need to read up on the qi stuff a bit.

: I'm another neophyte looking for info. Please point me to the info that
: could be classified as CSO/QI/PH 101 material.

I just posted a FAQ to this group. It should help.

--

* Noel Hunter, Academic Systems Administrator, Wake Forest University *

* no...@wfu.edu TEL:(910) 759-5812 MAIL:PO Box 7408 Winston-Salem, NC 27109 *