rt-email-group-admin(8) Request Tracker Reference rt-email-group-admin(8)NAME
rt-email-group-admin - Command line tool for administrating NotifyGroup actions
SYNOPSIS
rt-email-group-admin --list
rt-email-group-admin --create 'Notify foo team' --group Foo
rt-email-group-admin --create 'Notify foo team as comment' --comment --group Foo
rt-email-group-admin --create 'Notify group Foo and Bar' --group Foo --group Bar
rt-email-group-admin --create 'Notify user foo@bar.com' --user foo@bar.com
rt-email-group-admin --create 'Notify VIPs' --user vip1@bar.com
rt-email-group-admin --add 'Notify VIPs' --user vip2@bar.com --group vip1 --user vip3@foo.com
rt-email-group-admin --rename 'Notify VIPs' --newname 'Inform VIPs'
rt-email-group-admin --switch 'Notify VIPs'
rt-email-group-admin --delete 'Notify user foo@bar.com'
DESCRIPTION
This script list, create, modify or delete scrip actions in the RT DB. Once you've created an action you can use it in a scrip.
For example you can create the following action using this script:
rt-email-group-admin --create 'Notify developers' --group 'Development Team'
Then you can add the followoing scrip to your Bugs queue:
Condition: On Create
Action: Notify developers
Template: Transaction
Stage: TransactionCreate
Your development team will be notified on every new ticket in the queue.
USAGE
rt-email-group-admin --COMMAND ARGS
COMMANDS
list
Lists actions and its descriptions.
create NAME [--comment] [--group GNAME] [--user UNAME]
Creates new action with NAME and adds users and/or groups to its recipient list. Would be notify as comment if --comment specified.
add NAME [--group GNAME] [--user UNAME]
Adds groups and/or users to recipients of the action NAME.
delete NAME
Deletes action NAME if scrips doesn't use it.
switch NAME
Switch action NAME from notify as correspondence to comment and back.
rename NAME --newname NEWNAME
Renames action NAME to NEWNAME.
NOTES
If command has option --group or --user then you can use it more then once, if other is not specified.
AUTHOR
Ruslan U. Zakirov <ruz@bestpractical.com>
SEE ALSO
RT::Action::NotifyGroup, RT::Action::NotifyGroupAsComment
perl v5.14.2 2013-05-22 rt-email-group-admin(8)
Check Out this Related Man Page
PTS_RENAME(1) AFS Command Reference PTS_RENAME(1)NAME
pts_rename - Changes the name of a Protection Database entry
SYNOPSIS
pts rename -oldname <old name> -newname <new name>
[-cell <cell name>] [-noauth] [-localauth]
[-force] [-help]
pts ren -o <old name> -ne <new name> [-c <cell name>]
[-no] [-l] [-f] [-h]
DESCRIPTION
The pts rename command changes the name of the user, machine, or group entry specified by the -oldname argument to the name specified by
the -newname argument. It is not possible to change a user or machine entry's name to look like a regular group entry's name (have a colon
in it).
Members of the system:administrators group can change a regular group name into a prefix-less name and vice versa. When changing a prefix-
less group name into a regular group name or a regular group name to another regular group name, the owner field of the new name (the part
before the colon) must correctly reflect the group's owner.
Changing a regular group's owner with the pts chown command automatically changes the owner field (the part before the colon) of the
group's name, but does not change the owner field of any groups owned by the group. Use this command to rename those groups to a form that
accurately reflects their ownership.
CAUTIONS
By convention, many aspects of an AFS user account have the same name as the user's Protection Database entry, including the Authentication
Database entry, volume, and mount point. When using this command to change a user name, also change the names of all related entities to
maintain consistency. For instructions, see the chapter on user accounts in the OpenAFS Administration Guide.
OPTIONS -oldname <old name>
Specifies the current full name of the entry.
-newname <new name>
Specifies the new full name for the entry. For regular groups, the owner field (the part before the colon) of the new name must reflect
the actual ownership of the group.
-cell <cell name>
Names the cell in which to run the command. For more details, see pts(1).
-force
Enables the command to continue executing as far as possible when errors or other problems occur, rather than halting execution at the
first error.
-help
Prints the online help for this command. All other valid options are ignored.
-localauth
Constructs a server ticket using a key from the local /etc/openafs/server/KeyFile file. Do not combine this flag with the -cell or
-noauth options. For more details, see pts(1).
-noauth
Assigns the unprivileged identity anonymous to the issuer. For more details, see pts(1).
EXAMPLES
The following example changes the name of the group staff, owned by the privileged user "admin", to "admin:staff":
% pts rename -oldname staff -newname admin:staff
The following example changes the name of the group "admin:finance" to the group "finance". The issuer must belong to the
system:administrators group.
% pts rename -oldname admin:finance -newname finance
PRIVILEGE REQUIRED
To change a regular group name to a prefix-less name or vice versa, or to change a user or machine entry's name, the issuer must belong to
the system:administrators group.
To change a group name to a new name of the same type (regular or prefix-less), the issuer must own the group or belong to the
system:administrators group.
SEE ALSO pts(1), pts_chown(1)COPYRIGHT
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas
Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.
OpenAFS 2014-04-08 PTS_RENAME(1)