>>>>> "CH" == Craig Hartnett <subs@niner.net> writes:
CH> No response to this on the users' list, so I thought I'd try here.
I don't know that any of the developers keep you with the users' list; this
is development software so it's best to reach us here or on the development
list at mj2-dev@csf.colorado.edu.
CH> I'm guessing that the answers to questions 1 and 2 are specific to my
CH> server, although if someone can tell me how I might arrive at answers
CH> myself that would be great.
Well, you should create a user (using whatever procedure you use on your
system) that Majordomo will run as. I use 'lists'. You could use anything
at all; your own login would work, or even root if you really didn't care
about security. The README file has this to say:
Majordomo must run as a specific user on your system. Generally an account
must be created (the installation process will not do this for you). Give
either the name of this account or its numeric ID here.
CH> There are some suggestions in the readme file for question 3, and I
CH> will probably follow those.
They aren't suggestions; they are the only values supported. (Well, there
are some others that give everybody read and write access, but I'm sure
that's not what you want.) Choose the amount of security you want. As a
developer I like to poke about in the files, so I put myself in the same
group as Majordomo ans use 007. You probably want 077.
CH> With respect to questions 4 and 5, any pointers (or pointers to where I
CH> can find the information) on the usual directory structure for a UNIX
CH> Web server running Apache would be appreciated
There is no "usual place". Choose a directory that is where you want it to
be and which has enough space to contain the lists. The README file has
this to say:
----
Where will the Majordomo libraries, executables and documentation be kept?
This could be something like "/usr/local/majordomo"; Majordomo will make
this directory and several directories under it to hold its various
components.
Note that this is not necessarily where your lists must be stored.
Majordomo just needs to know where to put its executables and libraries.
After installation, Majordomo will not write to this location. It can be
NFS mounted or on a partition mounted read-only (after installation is
complete, of course). If it is an NFS-mounted partition, however, that
partition must be mounted to as to allow setuid binaries. If this is not
the case, most of Majordomo will fail completely. Note that Majordomo does
not install its libraries into the normal perl installation directories.
----
Where will the Majordomo list data be kept?
Note that under this directory will be a directory for each domain your
site supports, and under that a directory for each list at your site.
Note also that this should _not_ be a directory containing lists
maintained by Majordomo 1.x, as Majordomo 2 stores its lists in a
different format.
This should _not_ be an NFS-mounted directory, as the locking mechanism
currently used by Majordomo will not function properly over NFS. This
doesn't have to be in the same location as the previous directory.
----
- J<
References:
|
|
