[Mldonkey-commits] mldonkey distrib/ChangeLog distrib/multiuser.tx...

[mldonkey-commits]

CVSROOT:        /sources/mldonkey
Module name:    mldonkey
Changes by:     spiralvoice <spiralvoice>       07/06/26 21:22:48

Modified files:
        distrib        : ChangeLog 
Added files:
        distrib        : multiuser.txt 
Removed files:
        docs           : multiuser.txt 

Log message:
        -

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/mldonkey/distrib/ChangeLog?cvsroot=mldonkey&r1=1.1290&r2=1.1291
http://cvs.savannah.gnu.org/viewcvs/mldonkey/distrib/multiuser.txt?cvsroot=mldonkey&rev=1.1
http://cvs.savannah.gnu.org/viewcvs/mldonkey/docs/multiuser.txt?cvsroot=mldonkey&r1=1.2&r2=0

Patches:
Index: distrib/ChangeLog
===================================================================
RCS file: /sources/mldonkey/mldonkey/distrib/ChangeLog,v
retrieving revision 1.1290
retrieving revision 1.1291
diff -u -b -r1.1290 -r1.1291
--- distrib/ChangeLog   26 Jun 2007 21:21:07 -0000      1.1290
+++ distrib/ChangeLog   26 Jun 2007 21:22:48 -0000      1.1291
@@ -15,6 +15,7 @@
 =========
 
 2007/06/26
+Move docs/multiuser.txt to distrib/multiuser.txt
 6048: Make Ocaml 3.10.0 the default compiler
 - MLDonkey can still be compiled with Ocaml 3.08.3/4 & 3.09.*
 - if you need GTK1 oldgui you must use Ocaml < 3.10.0 to compile

Index: distrib/multiuser.txt
===================================================================
RCS file: distrib/multiuser.txt
diff -N distrib/multiuser.txt
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ distrib/multiuser.txt       26 Jun 2007 21:22:48 -0000      1.1
@@ -0,0 +1,158 @@
+Description of multiuser patch
+==============================
+This file provides some HowTos and internals about the new multiuser
+functionality of MLDonkey. The goal is to provide a p2p-service to be
+used by more than user and where each user has its own environment
+provided by the daemon.
+
+Some basics and definitions
+===========================
+User "admin" and all users belonging to a group where group_admin = true can
+see all files in any case and can use all functions of MLDonkey.
+
+file_owner in this text means the user which owns a downloading file,
+file_group means the group the file belongs to, file_owner must be a member of
+this group, both values are saved in files.ini.
+
+New options (displayed options are default values)
+==================================================
+users.ini
+---------
+- "users" is kept unchanged for compatibility, all users from "users2"
+  are saved in "users" as well, so password are updated.
+- "users2" is extended with these settings:
+
+A list of groups the user belongs to, this user can view all files
+which belong to one of the groups
+     user_groups = []
+
+The default group of the user, the user must also be a member of this
+group. File_group of new downloads started by the user are automatically
+assigned to this value. This value can be None, this means the file is a
+private one only visible to the file_owner (and admins, of course).
+     user_default_group = mldonkey
+
+E-mail address to sent commit notifications to. Global option "mail"
+can still be used for admins, if both addresses match only one mail is sent.
+     user_mail = ""
+
+Commit files to <incoming>/<user_commit_dir>
+The current incoming directory is appended with user_commit_dir.
+All incoming dirs are shared recursively now to share these files
+committed into user specific dirs.
+     user_commit_dir = ""
+
+Like global option max_concurrent_downloads this implements a user-specific
+limit of the maximum number of concurrent files a user can download. Other
+downloads are queued, this is done by round-robin. If the sum of
+user_max_concurrent_downloads from all users is bigger than
+max_concurrent_downloads less downloads than user_max_concurrent_downloads
+are in downloading state. 0 means no user-specific limit.
+Users can change file priorities the control which files are not queued.
+     user_max_concurrent_downloads = 0
+
+- groups, new option
+At least one group named "mldonkey" with group_admin = true must exist
+and will be re-created on startup if missing.
+
+Option to control if the group has admin rights. All users belonging to such a
+group have the same rights as user "admin".
+     group_admin = true
+
+
+files.ini
+---------
+- each file has two new options in files.ini
+file_owner: the incoming directory of the owner is used for commit,
+            if the user does not exist "admin" is used. If this data
+           field does not exist, the file will belong to user "admin".
+file_group: default value for a new download is user_default_group 
+            if file_owner is not member of file_group or the group does not
+            exist, the user_default_group of file_owner is used.
+
+downloads.ini
+-------------
+These two options control the display of user/group column in HTML, vd
+  html_mods_vd_user false
+  html_mods_vd_group false
+
+
+Commands to control multiuser features/data
+===========================================
+chgrp <group> <num>
+change group of download <num> to <group>, group = none for private file
+
+chown <user> <num>
+change owner of download <num> to <user>
+
+dgroup
+print default group of logged-in user
+
+groupadd <group> <admin: true | false>
+add new mldonkey group, only admin users can use this command
+
+groupadmin <group> <admin: true | false>
+change group admin status, only admin users can use this command
+
+groupdel <group>
+remove an unused mldonkey group, only admin users can use this command
+only possible if group has no members
+
+groups
+print groups of logged-in user
+
+passwd <passwd>
+change own password
+
+useradd <user> <passwd>
+add new mldonkey user/change user password, only admin users can use this 
command
+
+usercommit <user> <dir>
+change user specific commit directory
+
+userdel <user>
+remove a mldonkey user, only admin users can use this command, user "admin" 
can not be removed
+deleting a user is only possible if the user does not own any downloads
+
+userdgroup <user> <group|None>
+change user default group
+
+userdls <user> <num>
+change number of allowed concurrent downloads, only admin users can use this 
command
+
+usergroupadd <user> <group>
+add a group to a mldonkey user, only admin users can use this command
+
+usergroupdel <user> <group>
+remove a group from a mldonkey user
+
+usermail <user> <mail>
+change user mail address
+
+users
+use this command in HTML interface for a small GUI to control users
+
+whoami
+print logged-in user name
+
+
+Updating from a non-multiuser MLDonkey
+======================================
+When updating all files will have file_owner "admin" and file_group "mldonkey".
+All existing users will have user_default_group = "mldonkey" and
+user_groups = ["mldonkey"]. This means all users can use all features of
+MLDonkey and see all files in use by MLDonkey core, just like before.
+
+To hide user downloads from each other, create a new group with
+group_admin = false and assign all users to this group and remove them
+from all admin groups
+
+
+Additional features
+===================
+- file_completed_cmd has new environment variables $FILE_OWNER and $FILE_GROUP
+- remove option enable_user_config, replaced by membership of admin groups
+
+To-Do
+======
+- Suggestions ?

Index: docs/multiuser.txt
===================================================================
RCS file: docs/multiuser.txt
diff -N docs/multiuser.txt
--- docs/multiuser.txt  9 Nov 2006 21:32:25 -0000       1.2
+++ /dev/null   1 Jan 1970 00:00:00 -0000
@@ -1,158 +0,0 @@
-Description of multiuser patch
-==============================
-This file provides some HowTos and internals about the new multiuser
-functionality of MLDonkey. The goal is to provide a p2p-service to be
-used by more than user and where each user has its own environment
-provided by the daemon.
-
-Some basics and definitions
-===========================
-User "admin" and all users belonging to a group where group_admin = true can
-see all files in any case and can use all functions of MLDonkey.
-
-file_owner in this text means the user which owns a downloading file,
-file_group means the group the file belongs to, file_owner must be a member of
-this group, both values are saved in files.ini.
-
-New options (displayed options are default values)
-==================================================
-users.ini
----------
-- "users" is kept unchanged for compatibility, all users from "users2"
-  are saved in "users" as well, so password are updated.
-- "users2" is extended with these settings:
-
-A list of groups the user belongs to, this user can view all files
-which belong to one of the groups
-     user_groups = []
-
-The default group of the user, the user must also be a member of this
-group. File_group of new downloads started by the user are automatically
-assigned to this value. This value can be None, this means the file is a
-private one only visible to the file_owner (and admins, of course).
-     user_default_group = mldonkey
-
-E-mail address to sent commit notifications to. Global option "mail"
-can still be used for admins, if both addresses match only one mail is sent.
-     user_mail = ""
-
-Commit files to <incoming>/<user_commit_dir>
-The current incoming directory is appended with user_commit_dir.
-All incoming dirs are shared recursively now to share these files
-committed into user specific dirs.
-     user_commit_dir = ""
-
-Like global option max_concurrent_downloads this implements a user-specific
-limit of the maximum number of concurrent files a user can download. Other
-downloads are queued, this is done by round-robin. If the sum of
-user_max_concurrent_downloads from all users is bigger than
-max_concurrent_downloads less downloads than user_max_concurrent_downloads
-are in downloading state. 0 means no user-specific limit.
-Users can change file priorities the control which files are not queued.
-     user_max_concurrent_downloads = 0
-
-- groups, new option
-At least one group named "mldonkey" with group_admin = true must exist
-and will be re-created on startup if missing.
-
-Option to control if the group has admin rights. All users belonging to such a
-group have the same rights as user "admin".
-     group_admin = true
-
-
-files.ini
----------
-- each file has two new options in files.ini
-file_owner: the incoming directory of the owner is used for commit,
-            if the user does not exist "admin" is used. If this data
-           field does not exist, the file will belong to user "admin".
-file_group: default value for a new download is user_default_group 
-            if file_owner is not member of file_group or the group does not
-            exist, the user_default_group of file_owner is used.
-
-downloads.ini
--------------
-These two options control the display of user/group column in HTML, vd
-  html_mods_vd_user false
-  html_mods_vd_group false
-
-
-Commands to control multiuser features/data
-===========================================
-chgrp <group> <num>
-change group of download <num> to <group>, group = none for private file
-
-chown <user> <num>
-change owner of download <num> to <user>
-
-dgroup
-print default group of logged-in user
-
-groupadd <group> <admin: true | false>
-add new mldonkey group, only admin users can use this command
-
-groupadmin <group> <admin: true | false>
-change group admin status, only admin users can use this command
-
-groupdel <group>
-remove an unused mldonkey group, only admin users can use this command
-only possible if group has no members
-
-groups
-print groups of logged-in user
-
-passwd <passwd>
-change own password
-
-useradd <user> <passwd>
-add new mldonkey user/change user password, only admin users can use this 
command
-
-usercommit <user> <dir>
-change user specific commit directory
-
-userdel <user>
-remove a mldonkey user, only admin users can use this command, user "admin" 
can not be removed
-deleting a user is only possible if the user does not own any downloads
-
-userdgroup <user> <group|None>
-change user default group
-
-userdls <user> <num>
-change number of allowed concurrent downloads, only admin users can use this 
command
-
-usergroupadd <user> <group>
-add a group to a mldonkey user, only admin users can use this command
-
-usergroupdel <user> <group>
-remove a group from a mldonkey user
-
-usermail <user> <mail>
-change user mail address
-
-users
-use this command in HTML interface for a small GUI to control users
-
-whoami
-print logged-in user name
-
-
-Updating from a non-multiuser MLDonkey
-======================================
-When updating all files will have file_owner "admin" and file_group "mldonkey".
-All existing users will have user_default_group = "mldonkey" and
-user_groups = ["mldonkey"]. This means all users can use all features of
-MLDonkey and see all files in use by MLDonkey core, just like before.
-
-To hide user downloads from each other, create a new group with
-group_admin = false and assign all users to this group and remove them
-from all admin groups
-
-
-Additional features
-===================
-- file_completed_cmd has new environment variables $FILE_OWNER and $FILE_GROUP
-- remove option enable_user_config, replaced by membership of admin groups
-
-To-Do
-======
-- Suggestions ?