| Previous Contents Index Next |
| iPlanet Calendar Server Administration Guide |
Appendix A Command Line Utilities
This appendix provides complete details on the available commands, options, values, syntax notation, and usage rules for the iPlanet Calendar Server command line utilities. It provides supporting reference material for the topics described in Chapter 3 "Administering iPlanet Calendar Server.Administration for iPlanet Calendar Server is provided by a set of command line utilities. Each utility accepts options from the command line and can be invoked from batch, shell, and scripting programs such as Perl. Where applicable, default values for the available option are taken from the ics.conf configuration file.
Command Line Utility Syntax
iPlanet Calendar Server command line utilities use the following syntax:utility [-option [value]] command [target]
utility is the executable name of the utility, such as cscal.
option determines which action the command performs. Options are in lowercase and preceded by a hyphen (-), such as -d. An option enclosed in brackets ([]) indicates it is available, but is not required. When available, a combination of two or more options can be used at the same time.
value further qualifies the action specified by an option, such as a description used with the -d option. A value enclosed in brackets ([]) indicates it is available, but is not required. Values that include spaces must be enclosed in quotation marks (" "). Multiple values must be enclosed in quotation marks ("") and each value separated by a space unless indicated otherwise, such as the use of a semiclon delimited list in some cases.
command is an action the utility can perform, such as list. Commands separated by a vertical bar (|) indicate that either one (but not both) can be used at the same time.
target is the object on which the command takes effect, such as CALID (calendar ID) or USERID.
Usage Rules
The following rules provide general usage guidelines for the command line utilities:
If no command is specified, the utility lists all options and commands along with examples.
When required passwords are not specified, the utility will prompt for it.
The -v (verbose) and -q (quiet) options are available for every utility.
When a command is dangerous (one that can result in data loss), the utility will prompt for confirmation before executing the command. An example of a dangerous command is deleting a calendar or user. The -q (quiet) option, however, disables confirmation prompting.
The version command is available for every command line utility.
Command Line Utility Summary
Table A-1 summarizes the command line utilities.
csattribute
The csattribute utility lets you manage the iPlanet Calendar Server attributes in the LDAP Server. It provides the following commands:
add creates an LDAP attribute and value for a specified object.
Syntax
csattribute [-q|-v] -a attribute=val [-t resource | user] add targetcsattribute [-q|-v] -a attribute[=val] [-t resource | user] delete target
The iPlanet Calendar Server can be running or stopped.
On Unix systems, must be run while logged in as the user and group under which the iPlanet Calendar Server is running (such as icsuser and icsgroup) that was specified during installation, or as root.
Examples
csattribute -a icsCalendar=calA add userAThe above command adds the LDAP attribute icsCalendar with the value calA to the userID userA.
csattribute -a icsCalendar delete userA
The above command deletes the LDAP attribute icsCalendar from userA.
The above command displays the attributes of userA.
Table A-2 describes the commands available for the csattribute utility.
Table A-2 csattribute Utility Commands
Add an LDAP attribute and value to a specified target (user or resource object).
Table A-3 describes the csattribute utility command options.
csbackup
The csbackup utility lets you backup individual calendars, users, and the calendar database. It provides the following commands:
database to backup the calendar database.
calendar to backup a specified calendar.
defcal to backup a user's default calendar.
version displays the version number of the utility currently installed.
Syntax
csbackup [-q|-v] [-f] database targetcsbackup [-q|-v] -c CALID calendar target
csbackup [-q|-v] -a USERID [-b BASEDN] defcal target
Must be run locally on the machine where iPlanet Calendar Server is installed.
The iPlanet Calendar Server can be running or stopped.
On Unix systems, must be run while logged in as the user and group under which the iPlanet Calendar Server is running (such as icsuser and icsgroup) that was specified during installation, or as root.
Examples
csbackup database backupdirThe above example backs up the calendar database to a directory named backupdir.
csbackup -c calA calendar calA.ics
The above example backs up the calendar with the CALID calA to the file calA.ics as text/calendar.
csbackup -a userA defcal userA.xml
The above example backs up the default calendar for user userA to the file userA.xml as text/xml.
Table A-4 describes the commands available for the csbackup utility.
Table A-5 describes the csbackup utility command options.
Table A-5 csbackup Utility Command Options
Verbose mode which displays all available information about the command being performed. Default is off.
The USERID of the calendar user to backup. This option is required for the defcal command. There is no default.
The base DN to be used for this user. The default is taken from the setting local.ugldapbasedn defined in the ics.conf file.
The Base DN (distinguished name) is the entry in your LDAP directory used as the starting point from which searches will occur. For example, if you specify a base DN of ou=people, o=siroe.com, all LDAP search operations executed by iPlanet Calendar Server will examine only the ou=people subtree in the o=siroe.com directory tree.
The CALID to backup. This option is required with the calendar command. There is no default.
To prepare the backup file for use with the Solstace or Legato backup programs. For more information, see Backup and Restore Procedures.
cscal
The cscal utility lets you manage calendars and their properties. It provides the following commands:
create a calendar
modify calendar properties and group scheduling access control
reset calendar properties to the default settings
version displays the version number of the utility currently installed
Syntax
cscal [-q|-v] [-a ACEs] [-c charset] [-d description] [-g categories] [-k yes|no] [-l langcode] [-m email] [-n name] [-o owner] [-y otherowners] create|modify CALIDcscal [-q|-v] [-o owner] delete|disable|list|reset [CALID]
cscal [-q|-v] [-k yes|no] [-o owner] enable [CALID]
Must be run locally on the machine where iPlanet Calendar Server is installed.
The iPlanet Calendar Server can be running or stopped.
On Unix systems, must be run while logged in as the user and group under which the iPlanet Calendar Server is running (such as icsuser and icsgroup) that was specified during installation, or as root.
Examples
cscal -o userA -n calA create calAThe above example creates the calendar with the CALID calA with userA as the primary owner with the visible name exampleA using the default access control settings (as defined by the setting calstore.calendar.default.acl in the ics.conf file).
cscal -a "@^a^rw^g" -g sports -y userB modify calA
The above example modifies calendar calA so that it can be read and written to anyone, is associated with the category sports, and is co-owned by userB.
The above example deletes calA (removes it from the calendar database).
The above example deletes all calendars whose primary owner is userA (removes them from the calendar database).
The above example disables the calendar with the CALID calA (users will not be allowed to read, write to, or locate it using the user interface).
The above example enables the calendar with the CALID calA (users are allowed to read or write to it using the user interface), but does not allow double-booking.
The above example lists the properties of calA.
The above example lists all the properties of calA.
The above example lists all the calendars in the database.
The above example resets the calendar with the CALID calA to the default configuration settings.
The above example removes a description from the calendar with the CALID calA.
The above example removes all categories from the calendar with the CALID calA.
The above example removes other owners from the calendar with the CALID calA.
Table A-6 describes the commands available for the cscal utility.
Table A-7 describes the cscal utility command options.
Table A-7 cscal Utility Command Options
Verbose mode which displays all available information about the command being performed. Default is off.
Access Control Entries (ACE) for a specified calendar which determines who can access a calendar for group scheduling and what types of permissions they have, such as create, delete, read, and write privileges. An ACE string, called an Access Control List (ACL), must be enclosed in quotation marks ("").
Default is taken from the setting calstore.calendar.default.acl defined in the ics.conf file.
For details on the ACE format, see Access Control.
Description (a viewable comment about the purpose of the calendar). The default is no description.
Category. Multiple categories must be enclosed in quotation marks ("") and separated by spaces. The default is no category.
If double booking is allowed for a calendar. For example, yes means the calendar can have more than one event scheduled for the same time slot. The default is taken from the setting user.allow.doublebook defined in the ics.conf file
Note that this option is available only for calendars associated with a resource and will return an error if issued against a user's calendar.
Primary owner. The default setting is the CALID which is usually the same as the USERID.
Other owners. Multiple owners must be enclosed in quotation marks ("") and separated by spaces. The default is no other owners.
cscomponents
The cscomponents utility lets you manage components (events and todos) in a calendar. It provides the following commands:
delete events and tasks in a calendar.
list events and tasks in a calendar.
version displays the version number of the utility currently installed.
Syntax
cscomponents [-v|-q] [-e endtime] [-s starttime] [-t event|task] delete|list CALIDMust be run locally on the machine where iPlanet Calendar Server is installed.
The iPlanet Calendar Server can be running or stopped.
On Unix systems, must be run while logged in as the user and group under which the iPlanet Calendar Server is running (such as icsuser and icsgroup) that was specified during installation, or as root.
Examples
cscomponents -s 19980101T000000Z -e 19981231T000000Z delete calAThe above command deletes all 1998 events in the calendar with the CALID calA.
The above command lists all events and tasks, with details, in the calendar with the CALID calA.
Table A-8 describes the commands available for the cscomponent utility.
Table A-8 cscomponent Utility Commands
Table A-9 describes the cscomponent utility command options.
csdb
The csdb utility lets you manage the calendar databases. It provides the following commands:
create a new database. If a database does not exist when the server is started, iPlanet Calendar Server creates one automatically.
delete an existing calendar database. A database cannot be deleted while it is open (when the iPlanet Calendar Server is running).
list information about the database.
recover a damaged calendar database.
version displays the version number of the utility currently installed.
Syntax
csdb [-q|-v] [-t caldb|sessdb|statdb] create|delete [dbdir]csdb [-q|-v] [-t caldb|sessdb|statdb] list [dbdir]
csdb [-q|-v] [-f] [-t caldb|sessdb|statdb] recover [dbdir]
Must be run locally on the machine where iPlanet Calendar Server is installed.
The iPlanet Calendar Server cannot be running if creating or deleting the database.
On Unix systems, must be run while logged in as the user and group under which the iPlanet Calendar Server is running (such as icsuser and icsgroup) that was specified during installation, or as root.
Examples
csdb -t caldb createThe above command creates new, un-populated databases in the current directory.
The above command deletes the databases in the current directory.
The above command lists information about the calendar database in the current directory.
The above command attempts to recover all damaged databases in the current directory.
The above command lists information about the sessions database in the current directory.
The above command attempts to recover a damaged statistics database in the current directory.
Table A-10 describes the commands available for the csdb utility.
Table A-11 describes the csdb utility command options.
csexport
The csexport utility lets you export a calendar to a file in iCalendar or XML format. It provides the following commands:
calendar exports a specified calendar.
version displays the version number of the utility currently installed.
Syntax
csexport [-v|-q] -c CALID calendar outputfileMust be run locally on the machine where iPlanet Calendar Server is installed.
The iPlanet Calendar Server can be running or stopped.
On Unix systems, must be run while logged in as the user and group under which the iPlanet Calendar Server is running (such as icsuser and icsgroup) that was specified during installation, or as root.
Examples
csexport -c calA calendar calA.icsThe above command exports the calendar with the CALID calA in iCalendar (text/calendar) format to file named calA.ics.
csexport -c calA calendar calA.xml
The above command exports the calendar with the CALID calA in XML (text/xml) format to file named calA.xml.
Table A-12 describes the commands available for the csexport utility.
Table A-12 csexport Utility Commands
Export the calendar to the specified output file. The data format of the file is determined by the specified file name extension:
Table A-13 describes the csexport utility command options.
csimport
The csimport utility lets you import a calendar from a file in iCalendar or XML format that was saved with the csexport utility. It provides the following commands:
calendar imports a specified calendar.
version displays the version number of the utility currently installed.
Syntax
csimport [-v|-q] -c CALID calendar inputfileMust be run locally on the machine where iPlanet Calendar Server is installed.
The iPlanet Calendar Server can be running or stopped.
On Unix systems, must be run while logged in as the user and group under which the iPlanet Calendar Server is running (such as icsuser and icsgroup) that was specified during installation, or as root.
Examples
csimport -c calA calendar calA.icsThe above command imports the calendar with the CALID calA from the file calA.ics and expects iCalendar (text/calendar file) format.
csimport -c calA calendar calA.xml
The above command imports the calendar with the CALID calA from the file calA.xml and expects XML (text/calendar file) format.
Table A-14 describes the commands available for the csimport utility.
Table A-14 csimport Utility Commands
Import the calendar from the specified input file. The data format of the file is determined by the file name extension:
Table A-15 describes the csimport utility command options.
csplugin
The csplugin utility lets you manage the CSAPI plug-ins configured for your iPlanet Calendar Server installation. It provides the following commands:
activate loads and starts a specified plug-in.
deactivate shut downs and disables the specified plug-in type and plug-in name. (For descriptions of the supported plug-in types, see the "-t" option in Table A-17.)
list displays all supported plug-ins.
version displays the version number of the utility currently installed.
Syntax
csplugin [-q|-v] [-r] -t ac|attr|auth|locate|lookup|xlate activate|deactivate pluginMust be run on the local machine on which iPlanet Calendar Server is installed.
The iPlanet Calendar Server can be running or stopped.
On Unix systems, must be run while logged in as the user and group under which the iPlanet Calendar Server is running (such as icsuser and icsgroup) that was specified during installation, or as root.
Examples
csplugin -v listThe above command list details about all the supported plug-ins, including the type, name and the activation status of each plug-in configured for use with this server instance.
csplugin activate -t lookup mylookup
The above command loads and enables the lookup type plug-in with the filename mylookup.
csplugin deactivate -t lookup mylookup -r
The above command disables the lookup type plug-in with the filename mylookup and then deletes it from the plugin directory.
Table A-16 describes the commands available for the csplugin utility.
Table A-16 csplugin Utility Commands
Load and enable the specified plug-in type and plug-in name. (For descriptions of the supported plug-in types, see the "-t" option in Table A-17.)
Shut down and disable the specified plug-in type and plug-in name. (For descriptions of the supported plug-in types, see the "-t" option in Table A-17.)
List all the supported plug-in types, names, and activation status. (For descriptions of the supported plug-in types, see the "-t" option in Table A-17.)
Table A-17 describes the csplugin utility command options.
csresource
The csresource utility lets you manage calendar resources objects stored in the LDAP server and in the iPlanet Calendar Server calendar database. It provides the following commands:
create adds a new resource for a specified calid
delete removes a resource or all resources
disable disables a resource or all resources
enable enables a resource or all resources
list displays a single resource or a list of all resources
Syntax
csresource [-q|-v] [-a ACEs] [-b BASEDN] -c CALID [-d description] [-k yes|no] [-o owner] [-y otherowners] create namecsresource [-q|-v] [-b BASEDN] delete|disable|enable|list [name]
Must be run locally on the machine where iPlanet Calendar Server is installed.
The iPlanet Calendar Server can be running or stopped.
On Unix systems, must be run while logged in as the user and group under which the iPlanet Calendar Server is running (such as icsuser and icsgroup) that was specified during installation, or as root.
Examples
csresource listThe above command displays a list of all resource calendars and their LDAP attributes.
csresource -c room1 create meetingroom1
The above command creates a resource calendar with the calendar ID room1 and the viewable name (LDAP cn attribute) meetingroom1.
csresource delete meetinggroom1
The above command deletes the resource calendar with the viewable name meetinggroom1.
csresource disable meetinggroom1
The above command disables the resource calendar with the viewable name meetinggroom1.
csresource -b enable meetinggroom1
The above example enables the calendar with the resource calendar with the viewable name meetinggroom1 (users are allowed to read or write to it using the user interface) and allows double-booking.
csresource -a "@^a^rw^g" -y userB modify meetinggroom1
The above example modifies calendar calA so that it can be read by and written to anyone, is associated with the category sports, and is co-owned by userB.
csresource -v list meetinggroom1
The above command displays the LDAP attributes of the resource calendar with the viewable name meetinggroom1.
Table A-18 describes the commands available for the csresource utility.
Table A-19 describes the csresource utility command options.
Table A-19 csresource Utility Command Options
Verbose mode which displays all available information about the command being performed. Default is off.
Access Control Entries (ACE) for a specified calendar which determines who can access a calendar associated with a resource object (such as a conference room) for group scheduling and what types of permissions they have, such as create, delete, read, and write privileges. An ACE string, called an Access Control List (ACL), must be enclosed in quotation marks ("").
Default is taken from the setting resource.default.acl defined in the ics.conf file.
For details on the ACE format, see Access Control.
The LDAP base DN (distinguished name) to be used for the specified resource. The default is taken from the setting local.ugldapbasedn defined in the ics.conf file.
The icsCalendar attribute. This option is required with the create command and there is no default.
Description (a viewable comment about the purpose of the calendar). The default is no description.
If double booking is allowed for a calendar associated with a resource object such as a conference room. If yes, the resource calendar can have more than one event scheduled for the same time slot.
.Default is taken from the setting resource.allow.doublebook defined in the ics.conf file.
Default is taken from the setting service.admin.calmaster.userid defined in the ics.conf file.
Other owners. Multiple owners must be enclosed in quotation marks ("") and separated by spaces. The default is no other owners.
csrestore
The csrestore utility lets you restore individual calendars, users, and the calendar database. It provides the following commands:
database restores the calendar database.
defcal restores a user's default calendar.
version displays the version number of the utility currently installed.
Syntax
csrestore [-v|-q] [-f] database inputdircsrestore [-v|-q] -c CALID calendar inputfile
csrestore [-v|-q] -a USERID [-b BASEDN] defcal inputfile
Must be run locally on the machine where iPlanet Calendar Server is installed.
The iPlanet Calendar Server cannot be running if restoring the calendar database.
On Unix systems, must be run while logged in as the user and group under which the iPlanet Calendar Server is running (such as icsuser and icsgroup) that was specified during installation, or as root.
Examples
csrestore database backupdirThe above command restores the calendar database stored in the directory backupdir that was previously saved using the csbackup command line utility.
csrestore -c calA calendar backupdir/calA.ics
The above command restores the calendar with the CALID calA from the file calA.ics located in the directory backupdir that was previously saved in iCalendar (text/calendar file) format using the csbackup or csexport utility.
csrestore -c calA calendar backupdir
The above command restores calA from the calendar database in backupdir that was previously saved using csbackup.
csrestore -a userA defcal backupdir/userA.ics
The above command restores the default calendar owned by userA from the file userA.ics located in the directory backupdir that was previously saved in iCalendar (text/calendar file) format using the csbackup or csexport utility.
Table A-20 describes the commands available for the csrestore utility.
Table A-21 describes the csrestore utility command options.
csschedule
The csschedul utility lets you manage schedule entries stored in the Group Scheduling Engine (GSE) queue. It provides the following commands:
list displays entries held in the Group Scheduling Engine queue requested by a specifed calendar ID.
delete removes an entry from the Group Scheduling Engine queue requested by a specifed calendar ID.
version displays the version number of the utility currently installed.
Syntax
csschedule [-q|-v] [-c count] [-e endtime] [-s starttime] [-t scheduletime -o offset] [-u uid] list [CALID]csschedule [-q|-v] [-t scheduletime -o offset -u UID -n sequencenumber -r RID] list [CALID]
csschedule [-q|-v] [-t scheduletime -o offset -u UID -n sequencenumber -r RID] delete CALID
csschedule [-q|-v] [-s starttime] [-e endtime] delete [CALID]
Must be run locally on the machine where iPlanet Calendar Server is installed.
The iPlanet Calendar Server must be stopped.
On Unix systems, must be run while logged in as the user and group under which the iPlanet Calendar Server is running (such as icsuser and icsgroup) that was specified during installation, or as root.
Examples
csschedule -v listThe above command lists, in detail, all entries stored in the GSE queue.
The above command lists the first ten entries stored in the GSE queue.
csschedule -s 20001231T103045Z -e 20001231T113045Z list
The above command lists the entries in the GSE queue in the scheduled between 10:30:45 to 11:30:45 on 12/31/2000.
csschedule -v -t 20001231T103045Z -o 2 -u 1111 -r 0 -n 0 list calA
The above command lists the entry in the GSE queue for calendar calA that is scheduled at 10:30:45, with an offset number of 2 at the time 10:30:45, on 12/31/2000 with the unique identifier 1111, the recurrence ID 0, and the sequence number 0.
csschedule -v -t 20001231T103045Z -o 1 -u 1111 -r 0 -n 0 delete calA
The above command deletes this one entry in the GSE queue for calendar calA at 13:30:45, the first offset at time 13:30:45, on 12/31/2000, with the unique identifier 1111, the recurrence ID 0, and the sequence number 0.
csschedule -v -s 20001231T103045Z -e 20001231T163045Z delete
The above command deletes entries in the GSE that are scheduled between 10:30:45 and 16:30:45 on 12/31/2000.
The above command deletes all entries in the GSE queue.
Table A-22 describes the commands available for the csschedule utility.
Table A-23 describes the csschedule utility command options.
csstart
The csstart utility lets you start the iPlanet Calendar Server. It provides the following commands:
check determines if all iPlanet Calendar Server services or a specified service is running.
list displays all the iPlanet Calendar Server services or a specified service.
service starts all iPlanet Calendar Server services or a specified service.
version displays the version number of the utility currently installed.
Syntax
csstart [-q|-v] check|list [servicename]csstart [-q|-v] [-f] service [servicename]
Must be run locally on the machine where iPlanet Calendar Server is installed.
Examples
csstart serviceThe above command starts all iPlanet Calendar Server services using the default ports and in the default start order.
The above command starts the local iPlanet Calendar Server HTTP service.
The above command checks if all local iPlanet Calendar Server services are started.
The above command lists all local iPlanet Calendar Server services that are started.
The above command starts all local iPlanet Calendar Server services.
Table A-24 describes the commands available for the csstart utility.
Table A-25 describes the csstart utility command options.
csstats
The csstats utility lets you display the statistics of iPlanet Calendar Server and provides the following commands:
list displays various statistics that are recorded as counters on the iPlanet Calendar Server.
version displays the version number of the utility currently installed.
Note For more information on counters, see Counters.
Syntax
csstats [-q|v] [-r registry] [-i iterations] [-s delay]] list [subsystem]Must be run locally on the machine where iPlanet Calendar Server is installed.
The iPlanet Calendar Server can be running or stopped.
On Unix systems, must be run while logged in as the user and group under which the iPlanet Calendar Server is running (such as icsuser and icsgroup) that was specified during installation, or as root.
Examples
csstats listThe above command displays basic information about counters and what types are available.
The above command lists counter statistics about the HTTP service subsystem (hpptstat).
csstats -i 3600 -s 10 list wcap
The above command lists counter statistics about the wcap subsystem (wcapstat) every 10 seconds for one hour (3600 seconds).
Table A-26 describes the commands available for the csstats utility.
Table A-27 describes the csstats utility command options.
csstop
The csstop utility lets you stop the iPlanet Calendar Server. It provides the following commands:
service stops all services or a specified service of iPlanet Calendar Server.
version displays the version number of the utility currently installed.
Syntax
csstop [-q|-v] check | list [servicename]csstop [-q|-v] [-f] service [servicename]
Can be run on the local machine where iPlanet Calendar Server is installed or from a remote machine.
Examples
csstop serviceThe above command stops all local iPlanet Calendar Server services.
The above command stops the local iPlanet Calendar Server HTTP service.
The above command checks if all local iPlanet Calendar Server services are stopped.
The above command lists all local iPlanet Calendar Server services that are started.
Table A-28 describes the commands available for the csstop utility.
Table A-29 describes the csstop utility command options.
cstool
The cstool utility lets you ping an iPlanet Calendar Server or force it to refresh its configuration. It provides the following commands:
ping a Calendar Server service to verify that it is listening on a specified port.
refresh a Calendar Server service to force it to refresh its configuration settings.
version lets you display the version number of the utility currently installed.
Syntax
cstool [-q|-v] [-h host] [-p port] [-t timeout] ping [servicename]cstool [-q|-v] [-h host] refresh [servicename]
The Calendar Server must be running.
On Unix systems, must be run while logged in as the user and group under which the iPlanet Calendar Server is running (such as icsuser and icsgroup) that was specified during installation, or as root.
Examples
cstool ping httpThe above command pings the cshttpd service.
cstool -p 80 -h calserver -p 80 ping http
The above command pings the machine with the host name calserver to see if the iPlanet Calendar Server cshttpd service is listening on port 80.
The above command forces a local iPlanet Calendar Server to refresh the cshttpd service's configuration.
Table A-30 describes the commands available for the cstool utility.
Table A-31 describes the cstool utility command options.
csuser
The csuser utility lets you manage calendar user information stored in an LDAP directory server and in the iPlanet Calendar Server calendar database. It provides the following commands:
check if user is enabled for calendaring.
create and enable a user for calendaring.
disable a user from logging in to the iPlanet Calendar Server.
enable a user to log on to the iPlanet Calendar Server.
Note This tool is provided as a convenience, but it is recommended that administrators provision user attributes using a directory service or a customized user provisioning mechanism.
Syntax
csuser [-q|-v] [-a ACEs] [-b BASEDN] [-c CALID] -g givenname [-k yes|no] -s surname -y userpassword create USERIDcsuser [-q|-v] [-b BASEDN] check|delete|disable|enable|list|reset [USERID]
The Calendar Server can be running or stopped.
Must be run locally on the machine where iPlanet Calendar Server is installed.
The LDAP server that stores calendar user information must be running.
On Unix systems, must be run while logged in as the user and group under which the iPlanet Calendar Server is running (such as icsuser and icsgroup) that was specified during installation, or as root.
Examples
csuser check JSmithThe above example checks if the calendar user JSmith is enabled for calendaring (if the existing calendar user has access to calendar data on this iPlanet Calendar Server).
csuser -g John -s Smith -y password -c JSmithcal create JSmith
The above example creates an LDAP user with the USERID JSmith with the givenname John, surname Smith, and the CALID JSmithcal.
The above example deletes the user JSmith.
The above example disables the calendar user JSmith from logging in to the iPlanet Calendar Server.
The above example enables JSmith for calendaring (lets existing calendar user JSmith log on to the iPlanet Calendar Server).
The above example lists all calendar attributes for JSmith.
The above example lists all calendar USERIDs prefixed with the string: user
The above example resets all calendar attributes for JSmith to the default configuration settings.
Table A-32 describes the commands available for the csuser utility.
Table A-33 describes the csuser utility command options.
Table A-33 csuser Utility Command Options
Verbose mode which displays all available information about the command being performed. Default is off.
Access Control Entries (ACE) for a specified calendar which determines who can access a calendar for group scheduling and what types of permissions they have, such as create, delete, read, and write privileges. An ACE string, called an Access Control List (ACL), must be enclosed in quotation marks ("").
Default is taken from the setting calstore.calendar.default.acl defined in the ics.conf file.
For details on the ACE format, see Access Control.
The LDAP base DN (distinguished name) of the specified USERID. The default is taken from the setting local.ugldapbasedn defined in the ics.conf file.
The CALID of the default calendar to associate with the specified USERID. The default is the USERID.
The user's LDAP givenname (first name). This option is required. There is no default.
If double booking is allowed for a user's calendar. If yes, the user's calendar can have more than one event scheduled for the same time slot.
Default is taken from the setting user.allow.doublebook defined in the ics.conf file.
The user's LDAP surname (last name). This option is required. There is no default.
The calendar user's password. This option is required. There is no default.
Previous Contents Index Next
Copyright © 2000 Sun Microsystems, Inc. Some preexisting portions Copyright © 2000 Netscape Communications Corp. All rights reserved.
Last Updated November 06, 2000