@database MPrefs.guide
@author Matt Francis
@(c) 1993 Matt Francis

@wordwrap



@node Main "Contents"

                                @{b}@{u}MPREFS V1.00@{uu}@{ub}


                          @{i}Created by Matt Francis @{ui}

               Send comments, suggestions and bug reports to
                        @{b}m.p.francis@newcastle.ac.uk@{ub}


                                @{" Introduction " link Introduction}

                @{"  Disclaimer  " link Disclaimer}                @{"  Copyright   " link Copyright}

                @{" Distribution " link Distribution}                @{" Requirements " link Requirements}

                @{" Installation " link Installation}                @{" Using MPrefs " link Usage}

                @{"For The Future" link ForTheFuture}                @{"   History    " link History}
@endnode



@node Disclaimer

This software comes with no warranty, either expressed or implied.  The author is in no way responsible for any damage or loss that may occur due to direct or indirect usage of this software.  Use this software entirely at your own risk.
@endnode



@node Copyright

This software is freely distributable, BUT all programs and documentation are copyright 1993 Matt Francis.  Permission is NOT given to re-release this package if it has been altered in any way, with the exception that it may be made part of the official @{b}MultiUser@{ub} distribution.
@endnode



@node Distribution

Permission is given to include this program in a public archive (such as a BBS, FTP site or PD library) providing that all parts of the original distribution are kept intact.  These are as follows:

	MPrefs/MPrefs
	MPrefs/MPrefs.info
	MPrefs/MPrefs020
	MPrefs/MPrefs020.info
	MPrefs/MPrefs.guide
	MPrefs/MPrefs.guide.info
	MPrefs.info

No charge may be made for this program, other than a @{i}reasonable@{ui} copying fee, and/or the price of the media.
@endnode



@node Requirements

To use @{b}MPrefs@{ub}, you need:

	Kickstart V37 or above
	MultiUser V39 (release 1.5) or above

If you don't have @{b}MultiUser@{ub} installed on your system, @{b}MPrefs@{ub} will be of absolutely no use to you.  @{b}MultiUser@{ub} is an excellent system, and I would recommend it to anyone (you can get it from any decent Amiga FTP site - e.g. AmiNet - and probably from any good PD BBS).
@endnode



@node Installation

Drag @{b}MPrefs@{ub} into the drawer where you keep your prefs editors (usually "SYS:Prefs" unless you have moved them elsewhere).  On my system, I rename "MPrefs" to "MultiUser", in keeping with the naming convention of Commodore's prefs editors.
@endnode



@node Introduction

@{b}MPrefs@{ub} is a prefs editor for changing the @{b}MultiUser@{ub} configuration options
(i.e.  those contained in the "MultiUser.config" file).  Er, and that's it really!
@endnode



@node Usage "Using MPrefs"

@{b}MPrefs@{ub} can be run from the Workbench or a Shell, but it can only be
used by root.

@{u}Shell arguments:@{uu}

	  @{i}Format: @{ui}MPREFS [PUBSCREEN <public screen name>]

	@{i}Template: @{ui}PUBSCREEN/K

PUBSCREEN is the name of the public screen you wish @{b}MPrefs@{ub}' window to open on.  If none is given, @{b}MPrefs@{ub} will open on the default public screen.

@{u}Workbench tool-types:@{uu}

Any keyword in the argument template can be used as a tool-type.

                                  *  *  *

When MPrefs is run, it first tries to read the current configuration file. If the file doesn't exist, the default settings will be used.

@{b}MPrefs@{ub} lets you change the following configuration options (the names below
correspond to the names of the gadgets in the window, and the information is copied almost verbatim from the @{b}MultiUser@{ub} documentation):

@{i}Limit DOS SetProtection @{ui}

	If this option is turned on, the protection bits for GROUP and OTHER
	can no longer be changed with the DOS library's SetProtection()
	call.  Of course you can still change the protection bits for GROUP
	and OTHER with the MProtect command (or with the library call
	muSetProtection()).  It's very useful because a lot of programs
	change the protection bits without knowing about bits for GROUP and
	OTHER.  See also the support command LimitDOSSetProtection.

@{i}Profile @{ui}

	If this option is turned on and there exists a script file
	".profile" in the configuration directory, it will be executed after
	each login prompt by the support command Logout.

@{i}Last Login Requester @{ui}

	If this option is turned on, there will appear a "last login"
	requester after each GUI login.

@{i}Log Startup @{ui}

	If this option is turned on, every startup or reinitialisation of
	the MultiUser.server will be recorded in the file "MultiUser.log" in
	the configuration directory.

@{i}Log Login @{ui}

	If this option is turned on, every successful login will be recorded
	in the file "MultiUser.log" in the configuration directory.

@{i}Log Login Fail @{ui}

	If this option is turned on, every unsuccessful login will be
	recorded in the file "MultiUser.log" in the configuration directory.

@{i}Log Passwd @{ui}

	If this option is turned on, every successful password change will
	be recorded in the file "MultiUser.log" in the configuration
	directory.

@{i}Log Passwd Fail @{ui}

	If this option is turned on, every unsuccessful password change will
	be recorded in the file "MultiUser.log" in the configuration
	directory.

@{i}Log CheckPasswd @{ui}

	If this option is turned on, every successful password check (for
	example, when using another program of mine called MLock) will be
	recorded in the file "MultiUser.log" in the configuration directory.

@{i}Log CheckPasswd Fail @{ui}

	If this option is turned on, every unsuccessful password check (for
	example, when using another program of mine called MLock) will be
	recorded in the file "MultiUser.log" in the configuration directory.

@{i}Passwd UID Level @{ui}

	Users with a user identifier greater or equal than the specified
	value are allowed to change their passwords.  Specify a value in the
	range 0 to 65535.  For example,if you specify a value of 2, a guest
	user with a user identifier of 1 cannot change his or her password,
	unless their primary group identifier is greater than the
	"Passwd GID Level".  See also the option "Passwd GID Level" below.

@{i}Passwd GID Level @{ui}

	Users with a primary group identifier greater or equal than the
	specified value are allowed to change their passwords.  Specify a
	value in the range 0 to 65535.  For example, if you specify a value
	of 1, all users in a guest group with a primary group identifier of
	0 cannot change their passwords, unless their user identifiers are
	greater than the value given for "Passwd UID Level".  See also the
	option "Passwd UID Level".

For more information, read the @{b}MultiUser@{ub} documentation.

To reset all options to their default values, use the @{i}Reset To Defaults @{ui}item in the @{i}Edit @{ui}menu. You can revert to the values that were last saved by using the @{i}Last Saved @{ui}item in the @{i}Edit @{ui}menu.

To save the options, use the @{i}Save @{ui}button, or the @{i}Save @{ui}item in the @{i}Project @{ui}menu.  If you decide you don't want to keep the options you have changed, use the @{i}Cancel @{ui}button or @{i}Quit @{ui}menu item.

When @{b}MPrefs@{ub} saves the configuration file, it also changes the file protection flags so that no-one but root can view or change the file (as recommended in the @{b}MultiUser@{ub} documentation).  The new settings will not have any effect until the next time MultiUser is initialised.
@endnode



@node ForTheFuture "For The Future"

This is what I hope to do for future versions of @{b}MPrefs@{ub}:

- Add a user manager window, which will allow the editing of users, their passwords, IDs etc.  Also, it will have an option to freeze a naughty user's account without actually deleting the user.

- Add a group manager window which will allow you to create and delete groups, and decide who manages each group and which users belong to which group.
@endnode



@node History

@{b}V1.00@{ub}

- First release.
@endnode