| Oracle Calendar Server Reference Manual Release 5.5 Part Number B10094-01 |
|
| View PDF |
| Oracle Calendar Server Reference Manual Release 5.5 Part Number B10094-01 |
|
| View PDF |
This appendix contains full instructions on the usage and syntax of all utilities shipped with your calendar server. Note that the installation script does not install UNIX-only utilities on Windows NT platforms. All utilities are installed in the /users/unison/bin directory.
The following table lists all utilities in alphabetical order.
uniaddnode - Create a new calendar server node or re-initialize an existing one.
uniaddnode -n <node-ID> [-t <timezone>] [-a <nodealias>] [-r] [-y]
uniaddnode -n <node-ID> -w <DmPsw> [-p <SysOpPsw>] [-t <timezone>] [-a <nodealias>] [-r] [-y] uniaddnode -v uniaddnode -h
This utility creates and initializes a new calendar server node for use with either an internal directory or a directory server. It can also re-initialize an existing node.
uniaddnode runs only if the calendar server is down.
<nodealias>
Specify an alias for the node. <nodealias> is a descriptive word (it cannot contain spaces).
<node-ID>
Specify the node-ID. The node-ID must be unique across all nodes in the network.
<SysOpPsw>
Provide the SYSOP password for the node. This option is only required for directory servers. If the password is not provided on the command line, prompting for it occurs. For internal directories, the SYSOP password can be set after creation of the node using the unipasswd utility.
Re-initialize the node.
Note that in the case of a directory server, all users and resources must first be removed from the node before it can be re-initialized.
<timezone>
Specify a time zone for the node. The default is the time zone set during installation of the calendar server. Time zones can be obtained from the unitzinfo utility, the /users/unison/misc/timezone.ini file, or the calendar server Reference Manual, Appendix D, "Time Zone Table".
<DmPsw>
Provide the directory server password for unrestricted access (i.e. the password associated with the value of the [LDAP] mgrdn parameter in the unison.ini file). This option is only required for installations using a directory server. If the password is not specified on the command line, prompting for it occurs.
Used with the -r option to auto-confirm the re-initialization.
Print the current version number of uniaddnode.
Print a usage message explaining how to run uniaddnode.
% uniaddnode -n 44 -a admin -t EST5EDT -w DmPsw -p sysOpPsw unidsndini: working, please wait ... Creation of reserved users successful. Creation of Administrators group successful. uniaddnode: unidsndini done uniaddnode: unidbi done
The following entry now appears in the [<YOURNODEID>] section of the /users/unison/misc/unison.ini file.
[44] name = <internally-assigned value> version = A.02.62 aliases = admin timezone = EST5EDT
/users/unison/misc/unison.ini
This is the calendar server configuration file. For each new node, a node entry is created in this file by the uniaddnode utility.
Exit values are:
0 Success
Any non-zero value signals an error.
uniadmrights - Manage the administration rights of users.
uniadmrights [-ls] [[-hday] [-pgrp] [-opgrp] | -all] [-n <node-ID>] [-host <hostname>] [-p <SysOpPsw>] uniadmrights -e <user> [-add | -del] [[-hday] [-pgrp] [-opgrp] | -all] [-n <node-ID>] [-host <hostname>] [-p <SysOpPsw>] uniadmrights -default [-add | -del] [[-hday] [-pgrp] [-opgrp] | -all] [-n <node-ID>] [-host <hostname>] [-p <SysOpPsw>] uniadmrights -v uniadmrights -h
This utility allows the SYSOP to grant certain administration rights to users as well as to revoke these rights. It can also be used to determine the rights held by each user.
The existing rights are granted on a per-node basis and apply to:
By default, uniadmrights lists ALL rights that have been granted by the SYSOP. Note that the -ls option is mutually exclusive with the -add option, and with the -del option.
The calendar server must be up to run uniadmrights.
|
Note: Use the ManageHolidays, ManageAdmGroups, and CreatePublicGroups keywords in the |
Grant a right. Used with the -e option.
Add or delete ALL rights held by the user when used with the -e option (and either the -add or -del option). List all users holding rights when used with the -ls option.
Set rights for all users with the default administrative rights profile (applied when the ManageAdmGroups, ManageResources and ManageHolidays parameters are not present in or are commented out of user.ini).
Remove a right. Used with the -e option.
<user>
Specify the user. If more than one match for the user is found in the database, uniadmrights fails. If no action (-add/-del/-all) is specified along with this option, the default behaviour is to grant the specified right(s) to the user; if no rights are specified, ALL rights are granted to the user. See FORMAT OF THE <user> ARGUMENT for details on the <user> argument.
The holiday administration right. This right allows the user to set which holidays appear in the agendas of all users in the node. Note that no designates are associated with holiday administration; only those users granted the holiday right by the SYSOP may administer holidays.
<hostname>
Specify the host. Required if the host is remote.
List all granted rights. This is the default behaviour when no option has been specified.
<node-ID>
Specify the node. Required if more than one node exists on the host.
The public groups right. Allows the user to create public groups. The user, as owner of the public group, can make modifications to the group as well as delete the group itself. Since there are no designates associated with a public group, only its creator (owner) will be able to make modifications to it, or delete it.
<SysOpPsw>
Provide the SYSOP password; required if one is set. If this option is not used and a password is required, uniadmrights prompts the user for it.
The administrative groups right. Allows the user to create, delete, and/or modify administrative groups. Any user holding this right can delete and/or modify an existing administrative group, regardless of whether or not they are its creator. Since there are no designates associated with an administrative group, only those users holding this right will be able to modify or delete an administrative group.
Print the current version number of uniadmrights.
Print a usage message explaining how to run uniadmrights.
The <user> argument is a string of the form "key=value/key=value/...", where "key" is one of those listed below, and "value" is any string. Both "key" and "value" are case insensitive. The "value" string may be terminated by a wild card symbol (*). If a forward slash "/" is to be included in a string, it should be escaped with the character "\" to prevent it from being interpreted as a key-value pair delimiter - i.e. "S=Hoopla/OU1=R\/D".
If, in a UNIX environment, a shell will be processing the string (e.g. the string is provided on the command line or is passed as an argument to the utility), the string should be enclosed in quotation marks. Furthermore, if characters meaningful to the shell are included in the string, they may need to be escaped (i.e. preceded by the escape character "\") to prevent the shell from interpreting them.
|
Note: If the ID key-value pair is specified in the user argument, all other key-value pairs specified along with it are ignored. |
Some example specifications are: "S=Kilpi/G=Eeva", "S=B*/G=Nicole/O=Acme", "O=Acme/ID=1111/OU1=authors"
% uniadmrights
% uniadmrights -ls -hday -n 80
% uniadmrights -pgrp -host gravel
% uniadmrights -e "S=Martin/G=Don/OU1=r&d" -add -hday -n 80
% uniadmrights -default -add -pgrp -n 80
% uniadmrights -e "S=Bean/G=Joan" -del -all -host montreal
It is important to understand the implications of the directory server configuration for calendar server utilities.
In a supplier-consumer configuration, the scheduling of updates between the consumer and supplier may result in temporary differences between the two. This may mean that a calendar server utility is reading from a consumer directory server that has not yet been synchronized with its supplier.
Exit values are:
0 Success
1 Failure
2 Usage error
uniarch - Create a tar archive of the calendar server.
uniarch [-d] [-y] [-t | -f <filename>] uniarch -v uniarch -h
uniarch creates a backup of the calendar server. By default, the entire /users/unison directory is archived.
You must invoke uniarch from outside of the directory or directories it is backing up. For example, to back up the entire calendar server, you invoke uniarch from outside of the /users/unison directory.
uniarch can only be run if the calendar server is down.
|
Warning: uniarch backs up the calendar server internal database. If a directory server is being used, its database should also be backed up. |
Back up only the contents of /users/unison/db/nodes, the calendar server database.
<filename>
Specify the name of the archive file. If this option is not used, prompting for the filename occurs.
Force the tar default device to be used for the archive destination file.
By default, uniarch asks for confirmation before proceeding with the creation of the archive. This option tells uniarch to automatically proceed, without prompting for confirmation. Default if there is no tty associated with the calling process.
Print the current version number of uniarch.
Print a usage message explaining how to run uniarch.
/users/unison directory:
% uniarch uniarch: working, please wait ... uniarch: input tar archive destination file name: jan07-99.bkup uniarch: archive "/users/unison" and redirect to "jan07-99.bkup"? (y/n) uniarch: archive completed
% uniarch -d -f jan07-99-db.bkup uniarch: working, please wait ... uniarch: archive "/users/unison/db/nodes" and redirect to "jan07-99-db.bkup"? (y/n) uniarch: archive completed
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unib2lendian - Convert a calendar server node database from a format for big-endian UNIX processors to a format for little-endian Windows NT processors. For more details on this utility, contact Oracle support.
unicheck - Verify the calendar server file system.
unicheck [-nowarn] [-nodb | -maxdb <n>] [-c] unicheck -v unicheck -h
unicheck verifies the calendar server file system. The utility first checks that the version of the calendar server is intended to run on the local operating system. If this is not the case, unicheck prompts the user to determine whether or not they wish to continue. If the version runs on the local operating system, unicheck then verifies:
Any discrepancies are reported. Unless an entire file or directory is missing, any problems found are fixed running uniclean.
unicheck should be run periodically to ensure that the file system is in good order.
unicheck can be run whether the calendar server is up or down.
<n>
Specifies the maximum number of node databases unicheck should consider. For example, if <n>=30, unicheck checks the files of only the first 30 databases.
Do not print warning messages (error messages are still printed).
Do not check database files.
Computes a system-independent checksum for each static file. If this option is used, output should be redirected to a file for future use.
Print the current version number of unicheck.
Print a usage message explaining how to run unicheck.
unicheck (for brevity, sections of the output have been replaced by [...]):
% unicheck unicheck: checking all directories unicheck: checking directory "/users/unison" unicheck: checking directory "/users/unison/tmp" [...] unicheck: checking files in directory "/users/unison/bin" unicheck: checking files in directory "/users/unison/misc" [...] unicheck: checking versions of files in directory "/users/unison/bin" unicheck: check completed
unicheck, suppressing any warning messages and computing a checksum for each file (for brevity, sections of the output have been replaced by [...]):
% unicheck -nowarn -c unicheck: checking all directories unicheck: checking directory "/users/unison" unicheck: checking directory "/users/unison/tmp" [...] unicheck: checking files in directory "/users/unison/bin" unicheck: checking files in directory "/users/unison/misc" unicheck: checking files in directory "/users/unison/man" [...] unicheck: checking versions of files in directory "/users/unison/bin" unicheck: computing checksums unicksum: checksum of the file "/users/unison/misc/timezone.ini" is 17289 unicksum: checksum of the file "/users/unison/bin/addme" is 33775 [...] unicheck: check completed
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unicksum - Generate a checksum for a file.
unicksum <filename> unicksum -v unicksum -h
unicksum generates a checksum for a file that is used to determine whether or not differences exist between two instances of the same file.
unicksum runs whether the calendar server is up or down.
Print the version number of unicksum.
Print a usage message explaining how to run unicksum.
unitzinfo executable:
% unicksum unitzinfo unicksum: checksum of the file "unitzinfo" is 18187
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
uniclean - Clean up the calendar server file system.
uniclean uniclean -v uniclean -h
uniclean cleans up the calendar server file system by removing some transient files and ensuring file/directory and owner/group permissions are properly set.
uniclean can be run when the calendar server is up or down.
Print the current version number of uniclean.
Print a usage message explaining how to run uniclean.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unicheck
uniclr_ipc - Clear IPC resources consumed by the calendar server.
uniclr_ipc [-s] [-q] uniclr_ipc -v uniclr_ipc -h
uniclr_ipc clears IPC (Inter-Process Communication) resources consumed by the calendar server. By default, all IPC resources are freed. The -s and -q options are available to selectively clear only semaphore or message-queue resources respectively.
uniclr_ipc can only be run if the calendar server is down.
Clear semaphore-related resources only.
Clear message-queue related resources only.
Print the version number of uniclr_ipc.
Print a usage message explaining how to run uniclr_ipc.
In all of the following examples, the calendar server is down.
% uniclr_ipc uniclr_ipc: working, please wait... uniclr_ipc: ipc resources cleared
% uniclr_ipc -s uniclr_ipc: working, please wait... uniclr_ipc: ipc semaphore-related resources cleared
% uniclr_ipc -q uniclr_ipc: working, please wait... uniclr_ipc: ipc message-queue related resources cleared
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unicpinr - Copy resource data from a file created by unicpoutr to a calendar server node.
unicpinr [-add] [-f <filename>] [-start <day> <month> <year>] [-end <day> <month> <year>] [-host <hostname>] <Node-ID> [-p <SysOpPsw>] unicpinr -ls [<filename(s)>] unicpinr -v unicpinr -h
Copies a file containing resource data (created with the unicpoutr utility) into a calendar server node. The utility can be used in conjunction with unicpoutr to move a resource from one node to another, or to add the agenda of one resource to that of another (see EXAMPLES).
By default, the resource specified in the file must already exist in the destination calendar server node. If this is not the case, the -add option is used to add it.
unicpinr can only be run if the calendar server is up.
It is important to understand how unicpinr handles the information in the file during the copy into the destination node.
These are the values for the keys R, N, CA, S, G, ID, LOC, PHONE, EXT, FAX (see RESOURCE IDENTIFIER KEYS below for details on these keys). Only non-null values are output to the file by unicpoutr so not all keys may have a value in the file.
unicpinr uses these values to uniquely identify an existing resource in the destination node.
Where the resource already exists in the destination node, these values are already set and unicpinr does NOT overwrite them with those in the input file.
Where a resource already exists in the destination node, unicpinr simply adds the agenda information in the input file to the existing agenda.
All events listed in the file are copied into the destination node with the resource as the owner. Where appropriate, the description of each event contains extra data indicating the invitees to the event, their status, and the original creator and owner. Recurring or repeating instances of an event are disconnected from each other and copied in as individual events.
The -start and -end options can be used to import only those events that fall within the specified time.
Add the resource to the database before copying in the file. It is an error to specify this option if the resource already exists in the node. In the case of a directory server, the resource is created under the baseDN.
<day> <month> <year>
Set the end dates of the events to be processed. By default, all events in the file are created; this option and the -start option allow you to exclude certain events. Dates must be expressed in the form "day month year". Years must be specified using four digits. Some legal dates are "12 mar 1995", "15 october 1994", "25 12 1995" (for December 25, 1995). Variations such as "mar 12 1995" or "12 dec" are illegal and produce an error message.
<filename>
Specify the input file name. The file must have been created with the unicpoutr utility. By default, standard input is used.
<hostname>
Specify the host on which the specified node can be found. The default is the local host.
List the file name followed by the name of the resource it contains for each specified file name. Files not created with the unicpoutr command are not listed. If no file names are specified, the files of the current directory (.) are examined.
<SysOpPsw>
Provide the SYSOP password. If this option is not used, prompting for the password occurs.
<day> <month> <year>
Set the start date of the events to be processed. By default, all events in the file are created; this option and the -end option allow you to exclude certain events. Dates must be expressed in the form "day month year". Years must be specified using four digits. Some legal dates are "12 mar 1995", "15 october 1994", "25 12 1995" (for December 25, 1995). Variations such as "mar 12 1995" or "12 dec" are illegal and produce an error message.
Print the current version number of unicpinr.
Print a usage message explaining how to run unicpinr.
| Key | Description |
|---|---|
|
|
Resource name |
|
|
Resource number |
|
|
Capacity |
|
|
Contact's surname |
|
|
Contact's given name |
|
|
Location |
|
|
Phone number |
|
|
Phone extension |
|
|
Fax phone number |
unicpinr is used in conjunction with unicpoutr and unires to move a resource from one node to another. In the following example, the resource "betacam" will be moved from node 30 to 35.
% unires -ls "R=Betacam" -n 30 R=Betacam/CA=1/ID=1234
% unicpoutr "R=Betacam" -f betacam.dat 30
% unires -del "R=Betacam" -n 30
% unicpinr -add -f betacam.dat 35
unicpinr can be used in conjunction with unicpoutr to add the agenda of one resource to that of another resource. This example adds the agenda for "PineNook" to the agenda for "OakCranny" and at the same time changes the capacity of "OakCranny" to 5.
% unicpoutr "R=PineNook" -f pinenook.dat 30
% vi pinenook.dat
% unicpinr -f pinenook.dat 30
The agenda information for PineNook has been added to the existing agenda information for OakCranny.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
Depending on the size of the agenda in the file, unicpinr may take some time to complete.
The unicp family of utilities have the following limitations that must be considered.
From the perspective of a moved user (or resource), each of the moved events in the new agenda is a personal event with enough data in the description to determine who created the event and who the attendees are. All links are broken but there is sufficient information in the description to allow the links to be rebuilt.
Note also that where the agenda of one user (or resource) is being added to that of another, double-booking may occur.
When a user (or resource) is moved to a new node, that user (or resource) should be deleted from the old node (using uniuser -del (or unires -del)).
When a resource is deleted, all traces of that resource are removed. Thus, that resource is no longer an invitee to events.
When a user is deleted, all traces of that user are removed. Thus, that user is no longer an invitee to events created by other users. Furthermore, and most importantly, all events created by the user are deleted. As a consequence, any user in the old node who was invited to an event by the moved user, will no longer be able to view the event.
If several users (and/or resources) are to be moved, it is best to perform the move in three phases:
unicpoutu and/or unicpoutr).unicpinu and/or unicpinr).This ensures that information on any links among the users (and/or resources) being moved is not lost (see "Deleting a resource" above).
It is important to understand the implications of the directory server configuration for calendar server utilities. In a supplier-consumer configuration, the scheduling of updates between the consumer and supplier may result in temporary differences between the two. This may mean that a calendar server utility is reading from a consumer directory server that has not yet been synchronized with its supplier.
unicpoutr, unicpr
unicpinu - Copy the contents of a file of user data created by unicpoutu to a calendar server node.
unicpinu [-add ] [-f <filename>] [-start <day> <month> <year>] [-end <day> <month> <year>] [-host <hostname>] <node-ID> [-p <SysOpPsw>] unicpinu -ls [<filename(s)>] unicpinu -v unicpinu -h
unicpinu copies a file containing user data (created by unicpoutu) into a calendar server node. The utility can be used in conjunction with unicpoutu to add the agenda of one user to that of another user (see EXAMPLES). Although it can also be used, in conjunction with unicpoutu, to move a user from one node to another, unimvuser is the proper utility for moving users. unimvuser prevents the data loss that occurs when moving users with unicpoutu and unicpinu.
By default, the user specified in the file must already exist in the destination calendar server node. If this is not the case, they can be added using the -add option.
unicpinu can only be run if the calendar server is up.
It is important to understand how unicpinu handles the information in the input file during the copy into the destination node:
These are the values for the keys S, G, I, and X, and the keys OU1, OU2, OU3, OU4, O, C, A and P respectively (see NAME AND ADDRESS KEYS below for details on these keys). Only non-null values are output to the file by unicpoutu so not all keys may have a value in the file.
unicpinu uses these values to uniquely identify an existing user in the destination node.
Personal information includes employee number, phone number, extension, fax number, job title and office mailing address.
Where the user already exists in the destination node, these values are already set and unicpinu does NOT overwrite them with those in the input file.
Where a user already exists in the destination node, unicpinu simply adds the agenda information in the input file to the existing agenda.
All events listed in the file are copied into the destination node with the user as the owner. Where appropriate, the description of each event contains extra data indicating the invitees to the event, their status, and the original creator and owner. Recurring or repeating instances of an event are disconnected from each other and copied in as individual events.
The -start and -end options can be used to import events and completed tasks that fall within a specified range. Incomplete tasks are always imported.
|
Warning: Holidays are output by unicpoutu as meetings, and therefore input by unicpinu as meetings. Only the existing holidays in the destination node appear as holidays in the user's agenda. |
Add the user to the database and then copy in the user's agenda. It is an error to specify this option if the user already exists. Note that for directory servers, the user must already exist in the directory server (all of the X.400 key-value pairs specified in the input file must match), and must not already be a calendar user.
<day> <month> <year>
Set the end date for the events and tasks to be processed. By default, all events and tasks in the file are created; this option and the -start option allow you to exclude certain events and tasks. Dates must be expressed in the form "day month year". Years must be expressed using four digits. Some legal dates are "12 mar 1995", "15 october 1994", "25 12 1995" (for December 25, 1995). Variations such as "mar 12 1995" or "12 dec" are illegal and produce an error message.
<filename>
Specify the input file name. The file must be created with the unicpoutu utility. If this option is not specified, standard input is used.
<hostname>
Specify the host on which the specified node is found. The default is the local host.
<filename(s)>
Print the filename followed by the X.400 name and address of the user contained in the file, for each specified file name. Files not created by the unicpoutu command are not listed. If no file names are specified, the files in the current directory (.) are examined.
<SysOpPsw>
Provide the SYSOP password. If this option is not used, prompting for the password occurs.
<day> <month> <year>
Set the start date for the events and tasks to be processed. By default, all events and tasks in the file are created; this option and the -end option allow you to exclude certain events and tasks. Dates must be expressed in the form "day month year". Years must be expressed using four digits. Some legal dates are "12 mar 1995", "15 october 1994", "25 12 1995" (for December 25, 1995). Variations such as "mar 12 1995" or "12 dec" are illegal and produce an error message.
Print the current version number of unicpinu.
Print a usage message explaining how to run unicpinu.
unicpinu is used in conjunction with unicpoutu and uniuser to move a user from one node to another. In this example the user "Sarah Herman" will be moved from node 20 to 44, and one of her organizational units changed from "Sales" to "R&D".
|
Warning: Use this procedure ONLY if unimvuser cannot handle the move you need to make. See WARNINGS below for information on the data that is lost during this procedure. |
% uniuser -ls "S=Herman/G=S*" -n 20 S=Herman/G=Sarah/OU1=Dallas/OU2=Sales/ID=1234
% unicpoutu "G=Sara*/S=Herman -f sherman.dat 20
unicpinu -add command is to succeed.
% uniuser -del "G=Sara*/S=Herman" -n 20
% unicpinu -add -f sherman.dat 44 S=Herman/G=Sarah/OU1=Dallas/OU2=Sales/ID=1234
unicpinu can be used in conjunction with unicpoutu to add one user's agenda to that of another user. This example adds Sarah Herman's agenda to Yannick Olafsen's agenda.
% unicpoutu "G=Sara*/S=Herman" -f sherman.dat 20
sherman.dat file to modify the X.400 name and address to match that contained in the database for Yannick Olafsen.
% vi sherman.dat
% unicpinu -f sherman.dat 24
The agenda information for Sarah Herman is added to the existing agenda information for Yannick Olafsen.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
Depending on the size of the agenda in the file, unicpinu may take some time to complete.
The unicp family of utilities have the following limitations that must be considered.
From the perspective of a moved user (or resource), each of the moved events in the new agenda is a personal event with enough data in the description to determine who created the event and who the attendees are. All links are broken but there is sufficient information in the description to allow the links to be rebuilt.
Note also that where the agenda of one user (or resource) is being added to that of another, double-booking may occur.
When a user (or resource) is moved to a new node, that user (or resource) should be deleted from the old node (using uniuser -del (or unires -del)).
When a resource is deleted, all traces of that resource are removed. Thus, that resource is no longer an invitee to events.
When a user is deleted, all traces of that user are removed. Thus, that user is no longer an invitee to events created by other users. Furthermore, and most importantly, all events created by the user are deleted. As a consequence, any user in the old node who was invited to an event by the moved user, will no longer be able to view the event.
If several users (and/or resources) are to be moved, it is best to perform the move in three phases:
unicpoutu and/or unicpoutr).unicpinu and/or unicpinr).This ensures that information on any links among the users (and/or resources) being moved is not lost (see "Deleting a user (or resource)" above).
It is important to understand the implications of the directory server configuration for calendar server utilities. In a supplier-consumer configuration, the scheduling of updates between the consumer and supplier may result in temporary differences between the two. This may mean that a calendar server utility is reading from a consumer directory server that has not yet been synchronized with its supplier.
unicpoutu, unicpu
unicpoutr - Copy resource data from a calendar server node into a file.
unicpoutr res [-f <filename>] [-host <hostname>] [-start <day> <month> <year>] [-end <day> <month> <year>] <node-ID> [-p <SysOpPsw>] unicpoutr -v unicpoutr -h
unicpoutr copies a resource's data from a calendar server node to a file. It can be used in conjunction with the unicpinr utility to move a resource from one node to another as well as to copy the resource agenda from one resource to another.
unicpoutr can only be run if the calendar server is up.
The res argument must match a single resource or an error is reported. See FORMAT OF THE res ARGUMENT below for details on how to specify this argument.
unicpoutr copies the following information to the file (see unicpr for more information concerning the format and content of the output file):
Agenda information includes the past and future events either owned by the resource or to which the resource is invited. Holiday events are not included unless the -holiday option is used. The -start and -end options may be used to export those events with an attendance record which falls within a specified time period.
The following information is NOT copied to the file:
<day> <month> <year>
Set the end date of the events to be processed. By default, all events are output; this option and the -start option allow you to exclude certain events. Dates must be expressed in the form "day month year". Years must be specified using four digits. Some legal dates are "12 mar 1995", "15 october 1994", "25 12 1995" (for December 25, 1995). Variations such as "mar 12 1995" or "12 dec" are illegal and produce an error message.
<filename>
Specify the output file name. The file must not exist. By default, the standard output is used.
<hostname>
Specify the host on which the database for the specified node is found. The default is the local host.
<sysOpPsw>
Provide the SYSOP password. If this option is not used, prompting for the password occurs.
<day> <month> <year>
Set the start date of the events to be processed. By default, all events are output; this option and the -end option allow you to exclude certain events. Dates must be expressed in the form "day month year". Years must be specified using four digits. Some legal dates are "12 mar 1995", "15 october 1994", "25 12 1995" (for December 25, 1995). Variations such as "mar 12 1995" or "12 dec" are illegal and produce an error message.
Print the current version number of unicpoutr.
Print a message explaining how to run unicpoutr.
The res argument is a string of the form "key=value/key=value/...", where "key" is one of those listed below, and "value" is any string. Both "key" and "value" are case insensitive. The "value" string may be terminated by a wild card symbol (*). If a forward slash "/" is to be included in a string, it should be escaped with the character "\" to prevent it from being interpreted as a key-value pair delimiter - i.e. "R=betacam\/loaner/S=Khupfer".
If, in a UNIX environment, a shell will be processing the string (e.g. the string is provided on the command line or is passed as an argument to the utility), the string should be enclosed in quotation marks. Furthermore, if characters meaningful to the shell are included in the string, they should be escaped (i.e. preceded by the escape character "\") to prevent the shell from interpreting them.
Note that if the ID key-value pair is specified in the res argument, all other key-value pairs specified along with it are ignored.
| Key | Field |
|---|---|
|
|
Resource name |
|
|
Resource number |
|
|
Capacity |
|
|
Contact's surname |
|
|
Contact's given name |
|
|
Identifier |
|
|
Location |
|
|
Phone number |
|
|
Phone extension |
|
|
Fax phone number |
kitchen.dat:
% unicpoutr "R=Kitchen" -f kitchen.dat 20
% unicpoutr "R=Kitchen" -f kitchen.dat -start 10 1 1998 20
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
Depending on the size of the agenda, unicpoutr may take some time to complete.
The unicp family of utilities have the following limitations that must be considered.
From the perspective of a moved user (or resource), each of the moved events in the new agenda is a personal event with enough data in the description to determine who created the event and who the attendees are. All links are broken but there is sufficient information in the description to allow the links to be rebuilt.
Note also that where the agenda of one user (or resource) is being added to that of another, double-booking may occur.
When a user (or resource) is moved to a new node, that user (or resource) should be deleted from the old node (using uniuser -del (or unires -del)).
When a resource is deleted, all traces of that resource are removed. Thus, that resource is no longer an invitee to events.
When a user is deleted, all traces of that user are removed. Thus, that user is no longer an invitee to events created by other users. Furthermore, and most importantly, all events created by the user are deleted. As a consequence, any user in the old node who was invited to an event by the moved user will no longer be able to view the event.
If several users (and/or resources) are to be moved, it is best to perform the move in three phases:
unicpoutu and/or unicpoutr).unicpinu and/or unicpinr).This ensures that information on any links among the users (and/or resources) being moved is not lost (see "Deleting a user (or resource)" above).
It is important to understand the implications of the directory server configuration for calendar server utilities. In a supplier-consumer configuration, the scheduling of updates between the consumer and supplier may result in temporary differences between the two. This may mean that a calendar server utility is reading from a consumer directory server that has not yet been synchronized with its supplier.
unicpinr, unicpr
unicpoutu - Copy user data from a calendar server node to a file.
unicpoutu user [-f <filename>] [-host <hostname>] [-start <day> <month> <year>] [-end <day> <month> <year>] [-holiday] <node-ID> [-p <SysOpPsw>] unicpoutu -v unicpoutu -h
unicpoutu copies a user's data from a calendar server node to a file. It can be used in conjunction with the unicpinu utility to copy an agenda from one user to another. Although it can also be used, in conjunction with unicpinu, to move a user from one node to another, unimvuser is the proper utility for moving users. unimvuser prevents the data loss that occurs when moving users with unicpoutu and unicpinu.
unicpoutu can only be run if the calendar server is up.
The user argument must match a single user or an error is reported. See FORMAT OF THE user ARGUMENT below for details on how to specify this argument.
unicpoutu copies the following information to the file (see unicpu for more information concerning the format and content of the output file):
This includes the past and future events either owned by the user or to which the user is invited. Holiday events are not included unless the -holiday option is used. The -start and -end options may be used to export events falling within a specified time period.
Also included are all incomplete tasks and, by default, all completed tasks. The -start and -end options may be used to export completed tasks falling within a specified time period.
The following information is NOT copied to the file:
<day> <month> <year>
Set the end date of the events and tasks to be processed. By default, all events and tasks are output; this option and the -start option allow you to exclude certain events and tasks. Dates must be expressed in "day month year" form. Years must be specified using four digits. Some legal dates are "12 mar 1995", "15 october 1994", "25 12 1995" (for December 25, 1995). Variations such as "mar 12 1995" or "12 dec" are illegal and produce an error message.
<filename>
Specify the output file name. The file must not exist. By default, standard output is used.
Include the holidays from the user's agenda in the output file. Holidays are output as meetings, with all users in the node included as attendees to the meeting. If the user's agenda is subsequently input into a new node using unicpinu, only the existing holidays in the new node appear as holidays in the user's agenda; the holidays from the old node appear as meetings.
<hostname>
Specify the host on which the specified node can be found. The default is the local host.
<sysOpPsw>
Provide the SYSOP password. If this option is not used, prompting for the password occurs.
<day> <month> <year>
Set the start date of the events and tasks to be processed. By default, all events and tasks are output; this option and the -end option allow you to exclude certain events and tasks. Dates must be expressed in "day month year" form. Years must be specified using four digits. Some legal dates are "12 mar 1995", "15 october 1994", "25 12 1995" (for December 25, 1995). Variations such as "mar 12 1995" or "12 dec" are illegal and produce an error message.
Print the current version number of unicpoutu.
Print a usage message explaining how to run unicpoutu.
The user argument is a string of the form "key=value/key=value/...", where "key" is one of those listed below, and "value" is any string. Both "key" and "value" are case insensitive. The "value" string may be terminated by a wild card symbol (*). If a forward slash "/" is to be included in a string, it should be escaped with the character "\" to prevent it from being interpreted as a key-value pair delimiter - i.e. "S=Hoopla/OU1=R\/D".
If, in a UNIX environment, a shell will be processing the string (e.g. the string is provided on the command line or is passed as an argument to the utility), the string should be enclosed in quotation marks. Furthermore, if characters meaningful to the shell are included in the string, they should be escaped (i.e. preceded by the escape character "\") to prevent the shell from interpreting them.
|
Note: If the ID key-value pair is specified in the user argument, all other key-value pairs specified along with it are ignored. |
% unicpoutu "S=Herman/G=Sa*" -f sherman.dat 20
unicpoutu "S=Herman/G=Sa*" -f sherman.dat -start 10 1 1998
20
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
Depending on the size of the agenda, unicpoutu may take some time to complete.
The unicp family of utilities have the following limitations that must be considered.
From the perspective of a moved user (or resource), each of the moved events in the new agenda is a personal event with enough data in the description to determine who created the event and who the attendees are. All links are broken but there is sufficient information in the description to allow the links to be rebuilt.
Note also that where the agenda of one user (or resource) is being added to that of another, double-booking may occur.
When a user (or resource) is moved to a new node, that user (or resource) should be deleted from the old node (using uniuser -del (or unires -del)).
When a resource is deleted, all traces of that resource are removed. Thus, that resource is no longer an invitee to events.
When a user is deleted, all traces of that user are removed. Thus, that user is no longer an invitee to events created by other users. Furthermore, and most importantly, all events created by the user are deleted. As a consequence, any user in the old node who was invited to an event by the moved user will no longer be able to view the event.
If several users (and/or resources) are to be moved, it is best to perform the move in three phases:
unicpoutu and/or unicpoutr).unicpinu and/or unicpinr).This ensures that information on any links among the users (and/or resources) being moved is not lost (see "Deleting a user (or resource)" above).
It is important to understand the implications of the directory server configuration for calendar server utilities. In a supplier-consumer configuration, the scheduling of updates between the consumer and supplier may result in temporary differences between the two. This may mean that a calendar server utility is reading from a consumer directory server that has not yet been synchronized with its supplier.
unicpinu, unicpu
unicpr - Format of the file the unicpoutr utility creates, and the unicpinr utility reads.
The unicpoutr utility creates, and the unicpinr utility reads, an ASCII file with the following format.
{ <resource identification> } K Events: <event descriptions>
Except for the open brace bracket and close brace bracket which respectively open and close the <resource identification> section of the file, each line of the file begins with a single character code which defines the data stored on that line. A space follows the single character code. The unicpinr utility ignores blank lines and lines beginning with unknown codes.
Codes in the <resource identification> section are not legal in the <event descriptions> section, and vice versa.
The following describes the lines that the <resource identification> section may contain.
The following describes the lines that the <event descriptions> section may contain.
{ F Unison Export File V A.04.00 E FALSE X S=Baker/G=James R a Kitchen R b 12 R c 10 R d (123)-456-7890 R e 217 R f (123)-456-7891 I Password P 4 480 1140 1 15 127 2 0 15 0 0 0 #These define display and notification preferences as follows: # 4 ShowEventTitles # 480 StartDay at 8:00am # 1140 EndDay at 7:00pm # 1 StartWeek display on Sunday # 15 Display in time increments of 15 min. # 127 Display all days Sunday to Saturday # 2 Display time in am/pm format # 0 Periodic refresh disabled # 15 Refresh frequency 15 minutes # 0 Mail notification disabled # 0 No reminders # 0 No lead time before reminders N 1 } K Events: S 2262975 D 75 T Lunch G Kitchen I 0 R N0 M Kitchen W Kitchen A TRUE 1 5 C Lunch time C David Robinson C Kathy Bates O
unicpinr(8), unicpoutr(8).
unicpu - File format of the file the unicpoutu utility creates, and the unicpinu utility reads.
The unicpoutu utility creates, and the unicpinu utility reads, an ASCII file with the following format.
{ <user identification> } K Events: <event descriptions> K Tasks: <task descriptions>
Except for the open brace bracket and close brace bracket which respectively open and close the <user identification> section of the file, each line of the file begins with a single character code which defines the data stored on that line. A space follows the single character code. The unicpinu utility ignores blank lines and lines beginning with unknown codes.
Codes in the <user identification> are not legal in either of the other two sections, and vice versa.
The following describes the lines that the <user identification> section may contain.
The following describes the lines that the <event descriptions> section may contain.
The following describes the lines that the <task descriptions> section may contain.
{ F Unison Export File V A.02.51 E FALSE X S=Baker/G=James/I=T/OU1=Labs/OU2=SysAdmin U a Calendar Server Corporation, U a 1234 Software Blvd., U a Suite 999, U a Software Valley, CA 99999. U b 12 U c (123)-456-7890 U d (123)-456-7891 U e 215 U f System Administrator I Password P 4 480 1140 1 15 127 2 0 15 0 0 0 #These define display and notification preferences as follows: # 4 ShowEventTitles # 480 StartDay at 8:00am # 1140 EndDay at 7:00pm # 1 StartWeek display on Sunday # 15 Display in time increments of 15 min. # 127 Display all days Sunday to Saturday # 2 Display time in am/pm format # 0 Periodic refresh disabled # 15 Refresh frequency 15 minutes # 0 Mail notification disabled # 0 No reminders # 0 No lead time before reminders N 2 1 } K Events: S 2262975 D 75 T Friday R&D meeting G Conference Room I 0 R N0 M Baker James W Baker James A TRUE 1 5 C Discuss next week's activities. C James Baker C David Robinson C Kathy Bates O S D=25/Y=2000/M=April/T=00:00/z=EST5EDT D 1440 T Company Holiday I 1 R A2 M Robinson David W Robinson David A TRUE 0 0 O K Tasks: S D=1/Y=2000/M=April/T=8:00/z=EST5EDT D D=30/Y=2000/M=April/T=17:00/z=EST5EDT T System Overhaul. R 3 L 70 M Baker James W Baker James C Upgrade OS version from A.02.50 to A.04.51 O
unicpinu(8), unicpoutu(8)
unidbbackup - Create an archive of a calendar server node and related configuration information.
unidbbackup -d <dst> unidbbackup -v unidbbackup -h
unidbbackup creates a backup of a calendar server node and its related configuration information. More specifically, it creates a backup of the /users/unison/misc directory and the /users/unison/db directory. As the information in these two directories is interrelated, it is important to ensure they are backed up at the same time.
unidbrestore is the complementary utility to unidbbackup. By default, these utilities perform a copy of the source to the destination. If behaviour other than a straight copy is needed, an alternate backup/restore command can be specified using the [UTL] external_backup and external_restore parameters in the unison.ini file. See FILES below for details on how to specify an alternate backup command.
unidbbackup can be run when the calendar server is either up or down.
|
Warning: unidbbackup backs up the calendar server internal database. If a directory server is being used, its database should also be backed up. |
<dst>
Specify the destination for the archive, where <dst> is a directory name.
Print the current version number of unidbbackup.
Print a usage message explaining how to run unidbbackup.
/backups/cserver/jan.7.99:
% unidbbackup -d /backups/cserver/jan.7.99
Exit values are:
0 Success
Any non-zero value signals an error
/users/unison/misc/unison.ini
The following keys in the [UTL] section of this file are of relevance to this utility:
lock_timeout
This key sets the timeout, in seconds, for the lock operation on the database.
backup_timeout
This key sets the timeout, in seconds, for the backup operation on the database.
external_backup
This key provides a way for an alternate backup utility to be invoked by unidbbackup. unidbbackup uses the value of this key, along with the arguments supplied to unidbbackup on the command line, to construct (and subsequently invoke) the following command line:
value_of_external_backup [-f] -s <src> -d <dst>
where:
unidbbackup constructs this from the <dst> argument specified by the user on the unidbbackup command line)unidbbackup constructs this argument based on the information it finds in the /users/unison/misc/unison.ini file)unidbbackup iteratively invokes the generated command line until all of the required database files are backed up, locking and unlocking the database for each iteration.
The administrator must ensure that the generated command line is in fact a valid one for the alternate utility. It may be that an intermediate utility is required to take this command line, create one which is valid, and then invoke it. In this case, external_backup would be set to invoke the intermediate utility.
The accepted value for external_backup is any command line. There is no assigned default value for this key.
unidbrestore
unidbconv - Convert a version 2.50, 2.60 or 2.61 node database to version 2.62.
unidbconv -n <node-ID> | all [-p <pagevalue>] unidbconv -v unidbconv -h
unidbconv converts a version 2.50, 2.60 or 2.61 node database to version 2.62. In general you do not invoke this utility directly (a conversion is done automatically during the upgrade to a newer version of the calendar server). The last two digits of the "version" parameter in the [<YOURNODEID>] section of the unison.ini file indicate the version of the node.
|
Warning: You should back up the calendar server before invoking unidbconv as this utility overwrites the existing database. |
The calendar server must be down to run unidbconv.
<node-ID> | all
Perform the conversion on the specified node only (if <node-ID> is used) or on all nodes (if all is used).
<pagevalue>
Specify the number of cache pages to use for scanning and rebuilding key files. If this option is not used, the default value of 256 is used instead.
Print the version number of unidbconv.
Print a usage message explaining how to run unidbconv.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unidbfix - Check, repair, defragment and maintain a calendar server node database.
unidbfix -c [-pix] -n <node-ID> | all [-r] [-sfgn] [-kp <pagevalue>] unidbfix -f [-pix] -n <node-ID> | all [-r] [-y] [-sfgn] [-kp <pagevalue>] unidbfix -d [-pix] -n <node-ID> | all [-r] [-y] [-sfgn] [-kp <pagevalue>] unidbfix -export [-pix] -n <node-ID> | all [-r] [-kp <pagevalue>] unidbfix -import [-pix] -n <node-ID> | all [-r] [-y] [-kp <pagevalue>] unidbfix -ck -n <node-ID> | all [-r] [-y] [-kp <pagevalue>] unidbfix -k -n <node-ID> | all [-r] [-y] [-kp <pagevalue>] unidbfix -i [-pix] -n <node-ID> | all [-r] [-kp <pagevalue>] unidbfix -v unidbfix -h
unidbfix checks for and repairs database corruptions and/or inconsistencies, and/or defragments and compresses a node database. You should run unidbfix as part of a regular database maintenance program.
unidbfix carries out checks/repairs on the following parts of the database of the specified node:
unidbfix runs in one of eight different modes as listed below. If, in any mode, unidbfix makes a fix, it reports that fix. The scan phases for each mode appear in the order in which they occur. See the NOTES section for additional information on the Remote Nodes, Bins, and File Fragmentation scan phases.
unidbfix modesunidbfix only runs if the calendar server is down.
Run in check mode. unidbfix reports all database corruptions and inconsistencies but takes no action to correct them (use fix mode to do this). If unidbfix detects an error, it stops the check after the scan phase in which it finds the errors. For instance, if it discovers an error during the File Sizes scan phase, it terminates on completion of this scan phase. It does not proceed to the Nodes scan phase.
Run in check key mode. Checks only the key files of the database.
Run in defragment mode. In this mode unidbfix frees space occupied by deleted records and then compresses the database. To ensure database consistency, unidbfix checks the database for errors and fixes any it finds before it proceeds with defragmentation.
|
Warning: While it is possible to interrupt unidbfix during the defragmentation phase using a kill -9, this causes irreversible damage to the database. |
Run in export mode. In export mode unidbfix writes remote node information from the database to the remotenode.ini file. Note that it writes only the non-null fields for each remote node to the file. See the REMOTE NODES SCAN PHASE note for an example of how to use the -export mode.
Run in fix mode. Fix and clean up the database. This fixes all errors detected in check mode. In some circumstances unidbfix may be forced to delete data (e.g. where corruption to the data is such that unidbfix is unable to repair it, or where orphan data cannot be safely re-integrated).
Run in info mode. In this mode unidbfix outputs various database statistics to the dbfix.log file.
Run in import mode. In import mode unidbfix writes remote node information from the remotenode.ini file to the database. See the REMOTE NODES SCAN PHASE note for an example of how to use the -import mode as well as warnings on its use.
Run in fix key mode. Rebuilds only the key files of the database.
<pagevalue>
Specifies the number of cache pages to use for scanning and rebuilding key files. If this option is not used, the default value of 256 is used instead.
<node-ID> | all
Specify the node to check/fix/defragment. Use -n all to scan all the nodes on a computer.
Turn off the progress indicator. By default unidbfix outputs a progress indicator, for each utility it calls, to standard error.
Overwrite the /users/unison/log/dbfix.log log file, rather than append output to it.
Turn on foreign node checking and fixing. Use only if you have foreign nodes and items.
|
Warning: Using this option when you do not have foreign nodes and items may result in changes to the database. These changes may or may not be problematic. |
Turn fix and defragmentation confirmation message off.
Print the current version number of unidbfix.
Print a usage message, and a short description of each option.
% unidbfix -c -n 35
% unidbfix -f -n 12
% unidbfix -d -n 10 -r
/users/unison/log/dbfix.log
unidbfix writes any errors it finds and/or any fixes it makes, to this file. It lists each error as a DATABASE ERROR, and each repair as a Fix. unidbfix can repair any database error it finds. Totals of all errors found, fixes made, and records deleted during fixing, appear at the end of the file. Note that the total number of database errors need not equal the total number of fixes. You do not normally need to consult this file.
/users/unison/log/unison.ini
Consult this file for a listing of all local nodes, with their corresponding directory names and node-IDs.
remotenode.ini
unidbfix uses this file in import and export modes. It creates this file in a node's perm directory the first time it runs on the node. The file contains a listing of all the remote node records and their data fields. The information for each remote node is as follows:
[Node-ID] RN_NUMCONNECT: any number zero and above RN_ACCESSMETHOD: must be 2 RN_SERVICENAME: must be "unieng" RN_HOSTNAME: name of the remote host
Node-ID is the remote node identification number. It must be enclosed in square brackets and it must start a line. A field can have a null value. If any field has an invalid value, unidbfix returns an error message, and does not make the change for the remote node with the error.
The following sample remotenode.ini file contains two remote nodes: the first has the node-ID 730 and the name "NewYork"; the second has the node-ID 631 and the name "LosAngeles".
[730]
RN_NUMCONNECT = 2
RN_ACCESSMETHOD = 2
RN_SERVICENAME = "unieng"
RN_HOSTNAME = "NewYork"
[631]
RN_NUMCONNECT = 2
RN_ACCESSMETHOD = 2
RN_SERVICENAME = "unieng"
RN_HOSTNAME = "LosAngeles"
unidbfix.lck
This is a lock file which prevents multiple instances of unidbfix from running on the same node simultaneously. unidbfix creates this in the perm directory of the node on which it is running. In the event that a kill -9 or a system crash prevents unidbfix from running to completion, this file remains in place. It may be manually deleted.
Exit values are:
0 Success
No errors found (check mode)
Errors found but fixed (fix mode)
Successfully defragmented (defragment mode)
Successful import (import mode)
Successful export (export mode)
1 Errors Found
Errors were found (check mode)
2 Usage error
3 User interrupt
4 Aborted
Another instance of unidbfix was running on the node.
5 Stopped
unidbfix either found errors in the remote node records while in fix or check mode, or it could not find the remotenode.ini file. It needed more information to be able to continue checking or fixing.
Note that unidbfix rebuilds the key files of the database in fix, defragment, import, and fix key modes. If unidbfix is interrupted during any of these modes, the key files may have been deleted and not yet rebuilt. For this reason, it is highly recommended that you run unidbfix again after an interruption.
In the Bins and the File Fragmentation scan phases, unidbfix rebuilds files without checking for, or reporting, previously existing errors. In all other scan phases all errors reported in check mode are reported in fix mode before being fixed.
For this scan phase to run, the node's remotenode.ini must exist, and its contents must agree with the list of remote nodes in the database. When one of these conditions is not met, you can use the -export and -import modes to rectify the situation. The explanations that follow use the node-ID "43".
emotenode.ini file does not exist for node 43. In this case, generate one from the remote node list in the database:
% unidbfix -export -n 43
remotenode.ini file for node 43. In this case, rectify the discrepancy as follows.
First write the remote node information from the database to the remotenode.ini file for node 43:
% unidbfix -export -n 43
Make any required edits to the resulting remotenode.ini file.
Update the database with the modified file:
% unidbfix -import -n 43
unistart, unistop, uninode
unidbrestore - Restore a calendar server node and configuration information from a backup created by unidbbackup.
unidbrestore -s <src> [-d <dst>] [-n <node-ID>] unidbrestore -v unidbrestore -h
unidbrestore - restores the node and configuration information of a calendar server from a backup created by unidbbackup.
unidbbackup is the complementary utility to unidbrestore. By default, these utilities perform a copy of the source to the destination. If behaviour other than a straight copy is needed, an alternate backup/restore command can be specified using the [UTL] external_backup and external_restore parameters in the unison.ini file. See FILES below for details on how to specify an alternate restore command.
unidbrestore can only be run when the calendar server is down.
<dst>
Specify the destination for the restore. By default this is the /users/unison directory.
<node-ID>
Specify a node to restore.
<src>
Specify the backup source, where <src> is a directory name.
Print the current version number of unidbrestore.
Print a usage message explaining how to run unidbrestore.
/backups/cserver/jan.7.99 to the directory /users/unison:
% unidbrestore -s /backups/cserver/jan.7.99 -n 45
Exit values are:
0 Success
Any non-zero value signals an error
/users/unison/misc/unison.ini
The following parameters in the [UTL] section are of relevance to this utility:
lock_timeout
This parameter sets the timeout, in seconds, for the lock operation on the database.
restore_timeout
This parameter sets the timeout, in seconds, for the restore operation on the database.
external_restore
This parameter provides a way for an alternate restore utility to be invoked by unidbrestore. unidbrestore uses the value of this parameter, along with the arguments supplied to unidbrestore on the command line, to construct (and subsequently invoke) the following command line:
value_of_external_restore [-f] -s <src> -d <dst>
where
-d <dst> specifies the destination for the restore (unidbrestore constructs this from the dst argument supplied on the unidbrestore command or if no argument was supplied, uses the default)-s <src> specifies the source to be restored (unidbrestore constructs this from the src argument supplied on the unidbrestore command line)-f indicates that the source is a file (absence of this flag indicates the source is a directory)unidbrestore iteratively invokes the generated command line until all of the required database files are restored, locking and unlocking the database for each iteration.
It is up to the user to ensure that the generated command line is in fact a valid one for the alternate utility. It may be that an intermediate utility is required to take this command line, create one which is valid, and then invoke it. In this case, "external_restore" would be set to invoke the intermediate utility.
The accepted value for "external_restore" is any command line. There is no assigned default value for this key.
unidbbackup
unidomain - Create a new calendar domain. For Business-to-Business (B2B) deployments only.
unidomain -add -hostalias <alias> -domainid <id> -domainname <name> -t <timezone> -adminpassword <password> [-cds <hostname>] [-n <node-ID>] [-p <sysOpPassword>] [-disablepasswordmod] [-capacity <num>] [-reldn <dn>] [-resreldn <dn>] [-logo <imagename>] [-sitelogo <imagename>] [-sitename <name>] [-templatedir <dir>] [-supportemail <addr>] [-manageuseroff] [-manageresourceoff] [-manageholidayoff] [-manageeventcaloff] [-disable] [-y] unidomain -listaliases [-cds <hostname>] [-p <sysOpPassword>] unidomain -listdomainids [-cds <hostname>] [-p <sysOpPassword>] unidomain -v unidomain -h
unidomain is a command-line alternative to the Calendar Administrator for creating calendar domains. A domain is the representation on the calendar server of a single customer account. Each domain is associated with a single calendar server node. For more information on domains and the Calendar Domain Service, consult your calendar server Administrator's Guide.
You must use the -domainid option to specify a Domain ID for the new domain. This Domain ID must be unique in the Calendar Domain Service specified by the -cds option. To obtain a current list of all domain IDs in use on a given Calendar Domain Service, run unidomain with the -listdomainids option.
You must also use the -hostalias option to specify a calendar server alias for the new domain. The required alias is NOT simply the hostname of the calendar server, but one of the parameters listed in the [HOSTS] section of the /users/unison/misc/domain/domain.ini file. To see a list of all available calendar server aliases and the names of their corresponding hosts, run unidomain with the -listaliases option.
By default, unidomain will display the information you have specified for the new domain, and prompt you to continue if that information is correct.
unidomain will write many of the domain properties you specify in the /users/unison/misc/domain/domain.ini file. These parameters may be changed after domain creation. See Chapter 5 of your calendar server's Administrator's Guide for details on the parameters involved.
unidomain will also write a value for the domain.ini [YOURDOMAINID] adm.adminurl parameter. This URL provides an address for the Domain Administrator to manage the new domain through the Calendar Administrator.
unidomain can only be run when the calendar server is up.
Creates a new calendar domain.
<password>
Specify an initial password for the Domain Administrator of the domain being created.
Specify the maximum number of users and event calendars combined that may be created in the new domain. This value may be changed later using the Calendar Administrator. If this option is not used, the default value of 10 is assumed.
<hostname>
Specify a Calendar Domain Service host. If this option is not used, the local host is assumed.
Disable the new calendar domain. The Calendar Administrator will still be able to manage the domain normally, but clients featuring Domain-ID sign-in will be blocked (Outlook Connector 2.0 and greater, native clients 5.1 and greater, Web clients 2.2 and greater).
Prevent the Domain Administrator of the new domain from changing his or her password through the Calendar Administrator.
<id>
Specify a Domain ID for the new domain. This ID is usually a short string representative of the customer account. The value of the <id> argument may be any non-null alphanumeric string beginning with a letter that is unique in the Calendar Domain Service indicated by the -cds option. Domain IDs are case-insensitive; the Domain ID "acme1" cannot be used if the ID "ACME1" already exists. See also the -listdomainids option.
<name>
Specify the name of the company represented by the new domain.
<alias>
Specify the Calendar Domain Service alias of the calendar server host on which the new domain is to be created. The value of the <alias> argument must be one of the aliases configured in the [HOSTS] section of the /users/unison/misc/domain/domain.ini file. See also the -listaliases option.
Lists all available Calendar Domain Service aliases and calendar server hostnames currently in use on the Calendar Domain Service host specified by the -cds option.
Lists all Domain IDs currently in use on the Calendar Domain Service specified by the -cds option.
<imagename>
Specify an image file to display for this domain in the Calendar Administrator. The value of the <imagename> argument may be a filename within the Calendar Administrator's configured images directory or a fully qualified URL.
Remove from the Domain Administrator of this domain the right to manage event calendars and their events through the Calendar Administrator.
Remove from the Domain Administrator of this domain the right to manage holidays through the Calendar Administrator.
Remove from the Domain Administrator of this domain the right to manage resources through the Calendar Administrator.
Remove from the Domain Administrator of this domain the right to manage users through the Calendar Administrator.
<node-ID>
Specify a node to associate with this domain. If this option is not used, unidomain will use the first empty node it finds. If you use this option, the node you specify must already exist on the host indicated by the -hostalias option, and must not be associated with any other domain. Use of this option is strongly discouraged in most circumstances.
<sysOpPassword>
Specify the SYSOP password; this password should be the same for all calendar server nodes. if you do not supply the password, unidomain will prompt for it.
<dn>
Specify a Relative DN for this domain, relative to the calendar server base DN. Required only for installations using an external LDAP directory server.
<dn>
Specify a Resource Relative DN for this domain, relative to the domain's Relative DN (specified by the -reldn option). Only for installations using an external LDAP directory server. If this option is not used, the default value of "ou=Resources" is assumed.
<imagename>
Specify an image file to display in the Calendar Administrator to represent the provider for this domain. The value of the <imagename> argument may be a filename within the Calendar Administrator's configured images directory or a fully qualified URL.
<name>
Specify the name of this domain's provider as it should appear in the Calendar Administrator. The value of the <name> argument will override the Calendar Administrator's default Provider Name for this domain only. Other existing domains and future domains will not be affected.
<addr>
An e-mail address to display in the Calendar Administrator for the Domain Administrator to contact in case of errors or problems.
<timezone>
The time zone of the new domain. Use any of the values listed in the calendar server Reference Manual, Appendix D, "Time Zone Table".
<dir>
Specify a template directory for the Calendar Administrator to use for this domain. The value of the <dir> argument may be either a path relative to the Calendar Administrator CGI or FastCGI file, or it may be a fully qualified URL. The value of the <dir> argument will override the Calendar Administrator's default template directory for this domain only. Other existing domains and future domains will not be affected.
Proceed without asking for confirmation.
Print the current version number of unidomain.
Print a usage message explaining how to run unidomain.
% unidomain -listdomainids -cds cds.oracle.com The following Domain IDs already exist: ACME1 ACME2 TESTCO
% unidomain -listaliases -cds cds.oracle.com Alias Hostname calserver3 host3.oracle.com calserver2 host2.oracle.com calserver1 host1.oracle.com
calserver1", granting the Domain Administrator the right to manage users, resources and holidays but not event calendars:
% unidomain -add -hostalias calserver1 -domainid acme1 -domainname "Acme Corporation" -adminpassword sesame -t EST5EDT -cds cds.oracle.com -manageeventcaloff -p sysopPassword unidomain: Calendar domain provisioned successfully.
/users/unison/misc/domain/domain.ini
This configuration files is located on the Calendar Domain Service host, and contains most of the information that can be specified in the command-line argument given to this utility. See Chapter 5 of your calendar server's Administrator's Guide for details on the parameters involved.
Exit values are:
0 Success
Any non-zero value signals a failure
unidsacisetup - Set the access control information in the directory server for the calendar server ADMIN group.
unidsacisetup [-w <mgrDnPwd>] unidsacisetup -info unidsacisetup -v unidsacisetup -h
unidsacisetup sets the directory server access control information (ACI) for the calendar server ADMIN group. Although you can use directory server utilities to set ACIs, it is advisable to use unidsacisetup to ensure the ACI for the ADMIN group is properly set. Most calendar server utilities do not run unless the ACI for the ADMIN group is set.
This utility should be run every time a new calendar server ADMIN group is created, i.e. every time the [LDAP] admingroup parameter in the unison.ini file is changed.
unidsacisetup runs whether the calendar server is up or down. The directory server, however, must be running.
Display the list of directory servers for which this utility can create access control information.
<mgrDnPwd>
Provide the directory server manager password (this is the password associated with the [LDAP] mgrdn parameter in unison.ini). If this option is not used, unidsacisetup prompts the user for the password.
Print the version number of unidsacisetup.
Print a usage message explaining how to run unidsacisetup.
unidsacisetup can set ACI:
% unidsacisetup -info
% unidsacisetup
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unidsdiff - Find and delete differences between a calendar server node and a directory server.
unidsdiff [-d] [-noprompt] [-n <node-ID>] [-host <hostname>] [-p <SysOpPsw>] [-verbose] unidsdiff -v unidsdiff -h
This utility finds all users and resources in a calendar server node without a match in the directory server and vice versa. By default, it only reports discrepancies. Use the -d option to delete discrepancies.
The calendar server assigns each user and resource a unique identifier called an xItemId. unidsdiff first checks that each xItemId (for the specified node) in the directory server:
If unidsdiff detects an xItemId which does not pass one of these checks, it aborts; directory server utilities must be used to correct the problem. Otherwise unidsdiff proceeds to verify that:
The calendar server must be up to run unidsdiff.
Delete the differences found. The user is prompted to confirm each deletion. Without the -d option, unidsdiff simply lists the differences.
<hostname>
Specify the host to connect to. Required if host is remote.
<node-ID>
Specify a node. Required if more than one exists.
Disable prompting when used with the -d option.
<SysOpPsw>
Provide the SYSOP password.
Display all Distinguished Names in the directory associated with the node.
Print the current version number of unidsdiff.
Print a usage message explaining how to run unidsdiff.
unidsdiff on node 10:
% unidsdiff -n 10 -host inkpen Enter SYSOP password: unidsdiff: detected 0 duplicate "ctCalXItemId" attributes in directory unidsdiff: detected 0 multi-valued "ctCalXItemId" attributes in directory unidsdiff: detected 0 badly-formed "ctCalXItemId" attributes in directory unidsdiff: detected 0 calendar-stores without a matching directory entry unidsdiff: detected 0 calendar directory entries without a matching calendar-store
In this case, no discrepancies were found between the directory server and the calendar server. A verbose version of the same command would result in the following output:
% unidsdiff -n 10 -host inkpen -verbose Enter SYSOP password: DN="cn=Lorde Audre,o=Acme,c=us"<ctCalXItemID010:00346> DN="cn=Kilpi Eeva,o=Acme,c=us"<ctCalXItemID010:00347> : : DN="cn=Cohen Leonard,o=Acme,c=us"<ctCalXItemID010:00484> DN="cn=Atwood Margaret,o=Acme,c=us"<ctCalXItemID010:00485> DN="cn=Brossard Nicole,o=Acme,c=us"<ctCalXItemID010:00486> unidsdiff: detected 0 duplicate "ctCalXItemId" attributes in directory unidsdiff: detected 0 multi-valued "ctCalXItemId" attributes in directory unidsdiff: detected 0 badly-formed "ctCalXItemId" attributes in directory unidsdiff: detected 0 calendar-stores without a matching directory entry unidsdiff: detected 0 calendar directory entries without a matching calendar-store
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
It is important to understand the implications of the directory server configuration for calendar server utilities. In a supplier-consumer configuration, the scheduling of updates between the consumer and supplier may result in temporary differences between the two. This may mean that a calendar server utility is reading from a consumer directory server that has not yet been synchronized with its supplier.
unidssearch - List all users in a directory server who are not calendar users.
unidssearch [-f <LDAPfilter>] [-c <#ofDNs>] [-n <node-ID>] unidssearch -v unidssearch -h
unidssearch lists all users in the directory server who are not calendar users. The output of this command may be redirected to a file, modified as needed, and subsequently used as input to uniuser (using the -ex option). See OUTPUT FORMAT for information on the format of the file output by unidssearch.
The calendar server must be up to run unidssearch.
In Business-to-Business (B2B) deployments, unidssearch will produce no output if run on a node that is not part of a calendar domain.
<LDAPfilter>
Specify a raw LDAP filter to combine ("AND") with the default filter to retrieve users from an LDAP directory. Refer to your directory server documentation for exact attributes that can be specified in the LDAP filter. The values specified in the filter must be in the configured character set of the directory server (e.g. UTF-8, T.61). The default filter is:
[&(objectClass=organizationalPerson)(|(!(ctCalXItemId=*)) (!(ctCalXItemId=*:*)))]
<#ofDNs>
Limit the number of results returned to this number.
<node-ID>
Required for Business-to-Business (B2B) deployments. Returns only users within the relative DN of the domain identified with the specified node.
Print the current version number of unidssearch.
Print a usage message explaining how to run unidssearch.
The content of the file output by unidssearch has the following format:
A did=cn=jdoe, o=Acme, c=US A did=cn=confroom4, o=Acme, c=US
Each entry has an initial "A" character, followed by a "did". The "A" flags the user as one to add to the directory server as a calendar user. The "did" is the Directory ID or Distinguished Name of the user, uniquely identifying that user in the Directory Server.
The format of this file is the same as that required for the input file to the uniuser -ex command. If this is the intended use of the file, additional user data may be appended to the "did", in X.400 format. For example:
A did=cn=jdoe, o=Acme, c=US/G=John/OU=Sales
% unidssearch > dsonly.txt
% unidssearch -c 50
% unidssearch -f "(sn=Smith*)"
It is important to understand the implications of the directory server configuration for calendar server utilities. In a supplier-consumer configuration, the scheduling of updates between the consumer and supplier may result in temporary differences between the two. This may mean that a calendar server utility is reading from a consumer directory server that has not yet been synchronized with its supplier.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
uniuser
unidssync - Synchronize the information in a calendar server node with that in a directory server.
unidssync [-n <node-ID>] [-host <hostname>] [-p <SysOpPsw>] unidssync -v unidssync -h
unidssync is only used when connected to an external directory server. This utility synchronizes the information in a calendar server node with that in the directory server.
unidssync should be run when other applications using the directory server have changed directory server entries without the knowledge of the calendar server, AND when the [ENG] dac_itemget parameter in unison.ini is set to "FALSE" to enhance performance (in this case, the calendar server retrieves its information from the internal store rather than from the directory server).
These conditions might allow discrepancies to arise between the information in the internal store of the calendar server node and that in the directory server. unidssync eliminates discrepancies, using the directory server as the authority. It should be run as part of a regular maintenance program.
The calendar server must be up to run unidssync.
<host>
Specify the host. Required if connecting to a remote host.
<node-ID>
Specify the node. Required if more than one node exists.
<sysOpPsw>
Provide the SYSOP password. If it is not provided on the command line, prompting for it occurs.
Print the current version number of unidssync.
Print a usage message explaining how to run unidssync.
% unidssync -n 10 -host fergus unidssync: 152 internal calendar directory entries to synchronize SYNCHRONIZING <10,234> <S="Okeefe",G=Georgia)<U> DONE SYNCHRONIZING <10,235> <S="Whittome",G=Irene)<U> DONE SYNCHRONIZING <10,236> <S="Cornell",G=Joseph)<U> DONE : : SYNCHRONIZING <10,383> <S="Goodwin",G=Betty)<U> DONE SYNCHRONIZING <10,384> <S="Dickson",G=Jennifer) <U> DONE SYNCHRONIZING <10,385> <S="Wagschal",G=Marian) <U> DONE SYNCHRONIZING <10,386> <S="Giacometti",G=Alberto) <U> DONE unidssync: 152 internal calendar directory entries synchronized
It is important to understand the implications of the directory server configuration for calendar server utilities. In a supplier-consumer configuration, the scheduling of updates between the consumer and supplier may result in temporary differences between the two. This may mean that a calendar server utility is reading from a consumer directory server that has not yet been synchronized with its supplier.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unidsup - Report the status of the directory server.
unidsup [-q] [-host <hostname>] unidsup -v unidsup -h
unidsup reports whether or not the directory server is running.
The calendar server must be up to run unidsup.
<hostname>
Provide the name of the calendar server host. If this option is not present, the local host is assumed.
Operate in quiet mode (produces no output when the directory server is up).
Print the version number of unidsup.
Print a usage message explaining how to run unidsup.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
uniencrypt - Encrypt a password for inclusion in a calendar server configuration file.
uniencrypt -m <encryption_method> -s <string> uniencrypt -v uniencrypt -h
uniencrypt uses the encryption method specified by the -m option to encrypt the password specified by the -p option. Any password supplied in a calendar server configuration file (such as those specified by the [LDAP] bindpwd and writednpassword parameters) must first be encrypted using this utility.
uniencrypt returns the encrypted password preceded by the encryption method used to generate it. For example, {acipher}ruyr84jf. Generally, this entire value, including the encryption method and curly braces, should be enclosed in double quotes and included as the value of the password specified in the calendar server configuration file. For example:
[LDAP] bindpwd = "{acipher}ruyr84jf"
uniencrypt can be run when the calendar server is up or down.
<encryption_method>
Specifies the encryption method to use. Accepted values currently include only acipher, a proprietary affine cipher encryption method, and encd. If this argument is not used, acipher will be used by default.
<string>
Specifies the string to encrypt. If this is option is not used, uniencrypt will prompt for the string to encrypt.
Print the current version number of uniencrypt.
Print a usage message explaining how to run uniencrypt.
% uniencrypt -s secure {acypher}u0bI1inm
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unigrpls - Display both the public and administrative groups in a calendar server database.
unigrpls [-grp <groupname>] [-members] [-host <hostname>] [-n <node-ID>] [-p <SysOpPsw>] unigrpls -v unigrpls -h
unigrpls prints both the public and administrative groups in the specified calendar server node. By default, all groups are displayed along with the total number of members in each. The -members option is used to display each member in the group.
Note that if a directory server is used, any groups created in the directory server are also included in the output of unigrpls. If members are listed, only the members of the directory server group who are also calendar users are output.
unigrpls can only be run if the calendar server is up.
<groupname>
Specify a group.
Print the individual members for each group output.
<hostname>
Specify the host on which the operation is to be performed. The default is the local host.
<node-ID>
Specify the node on which the group is located. Required if more than one node is configured.
<sysOpPsw>
Specify the SYSOP password. Without this option, prompting for the password occurs.
Print the current version number of unigrpls.
Print a usage message explaining how to run unigrpls.
% unigrpls -host jupiter -n 20
% unigrpls -grp "Managers" -members -n 10
% unigrpls -members
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unil2bendian - Convert a calendar server node database from a format for little-endian Windows NT processors to a format for big-endian processors. For more details on this utility, contact Oracle support.
unil2lendian - Convert a calendar server node database from a format for little-endian Windows NT processors to a format for little-endian UNIX processors (Red Hat Linux or Tru64 UNIX) and vice-versa. For more details on this utility, contact Oracle support.
unilogons - Display calendar server SIGNON/SIGNOFF statistics.
unilogons [-s <starttime>] [-e <endtime>] [-i <interval>] [-f <filename>] unilogons -t -s <starttime> -e <endtime> -i <interval> [-f <filename>] unilogons -t [<time>] [-f <filename>] unilogons -v unilogons -h
unilogons displays the signon and signoff activity of users on a calendar server at a specific time or during a specific time period. By default it uses the information in the /users/unison/log/act.log file. The -f option may be used to specify another input file.
The -t option displays activity at a precise moment, while the -s and -e options display activity during a defined period. The -i option specifies a regular time interval (e.g. every 15 minutes) within a specified period.
By default, all activity between the default start-time (the first minute of the current day) and the default end-time (the current system time) is displayed.
The calendar server must be up to run unilogons.
<endtime>
Specify an end time for the statistics. Without this option, the default end time is the current time of the current day. See TIME ARGUMENT FORMAT below for details on how to specify <endtime>.
<filename>
Specify the name of the input file. By default the input file is /users/unison/log/act.log. The input file specified with the -f option must be in the same format as the act.log file.
<interval>
Specify a time interval. The default interval is <endtime> minus <starttime>. See INTERVAL ARGUMENT FORMAT below for details on how to specify interval.
<starttime>
Specify a start time for the statistics. Without this option, the default start time is the first minute of the current day. See TIME ARGUMENT FORMAT below for details on how to specify <starttime>.
[<time>]
If used without the -s, e, and -i options, this displays statistics for the current time (-t) or for a given time (-t <time>). When used together with all of the -s, -e, and -i options, the -t (without a time argument) restricts output to activity at only the precise times determined by the interval (-i) argument. See the last two EXAMPLES for sample output of the -s, -e, -i options both with and without the -t option. See TIME ARGUMENT FORMAT below for details on how to specify time.
Print the current version number of unilogons.
Print a usage message explaining how to run unilogons.
The <starttime>, <endtime>, and <time> arguments may each be expressed as either:
where
day
is a number between 1 and 31;
month
is either the full name of the month or the first three letters of the full name (e.g. jan, feb, mar, etc.) (month is case-insensitive);
year
must be 1991 or higher and must be specified using four digits; and
time
is in the form HH:MM or HH:MM:SS (HH is an integer between 0 and 23, MM is an integer between 0 and 59, and SS is an integer between 0 and 59).
The order of the individual elements in the argument is unimportant. What is important is that either day and month be specified, or time be specified. For example, the following are all valid:
Feb 22 1996 10:00:00 22 february 10:00:00 10:00:00 february 22 1996 1996 feb 22 feb 22 10:00:00
Default values for day, month, year and time are current day, current month, current year and current system time respectively.
Any missing field in time (HH, MM, or SS) is replaced with the current HH, MM, or SS value. Thus, if the current date and time is March 12 1998 10:12:34, and only HH:MM are specified in the argument, the SS becomes "34":
-e 12:41-> March 12 1998 12:41:34-s 12:41-> March 12 1998 12:41:34
If none of the time fields are specified, starttime defaults to the first minute of the day, and endtime defaults to the last minute of the day:
-s feb 22-> feb 22 1998 00:00:00-e feb 22-> feb 22 1998 23:59:59
The interval argument must be an integer greater than zero and be input as minute, hour or day as follows:
minutes: 1m, 2m, etc. up to 999999999m (9 digits) hours: 1h, 2h, etc. up to 9999999h (7 digits) days: 1d, 2d, etc. up to 99999d (5 digits)
unilogons -t
unilogons -t oct 6 1998 15:00
This would produce the following output:
Time 1: Oct 6 1998 15:00:00 ------------------------------------- Client Logged-On Name & Version unisncd 2 Windows/32/CorporateTime 1 ------------------------------------- Totals: 3
unilogons -t -s oct 6 1998 15:00:00 -e oct 6 1998 17:00:00 -i 15m
A sample section of the output from this command shows the form of what is output for each of the times 15:00:00, 15:15:00, 15:30:00, etc., up to 17:00:00. (Compare this with the output of the next example, where the -t is removed from the command line.)
Time 1: Oct 6 1998 15:00:00 ------------------------------------- Client Logged-On Name & Version unisncd 2 Windows/32/CorporateTime 1 ------------------------------------- Totals 3
unilogons -s oct 6 1998 15:00:00 -e oct 6 1998 17:00:00 -i 15m
For each of the 15-minute time intervals within the entire time period, output similar to the following is displayed:
Time Period 1: From Oct 6 1998 15:00:00 Till Oct 6 1998 15:15:00 -------------------------------------------------------------------------------- Client Logons Logoffs Average Time Median Time Name & Version Logged-On(hrs) Logged-On(hrs) Not Available 0 2 20.71 23.98 unisncd 2 0 9.83 9.83 Windows/32/CorporateTime 4 4 0.02 0.02 -------------------------------------------------------------------------------- Totals 6 6
/users/unison/log/act.log
By default unilogons obtains its information from this file. Note that this file is only created if the [ENG] activity parameter in unison.ini is set to "TRUE".
unilogons may take some time to finish depending on the size of the input file.
The disk space requirement to run unilogons is one and a half times the input file. Thus, if the size of the input file is 8 Mb, approximately 12 Mb of free disk space is required to run unilogons. unilogons creates its temporary files in the /users/unison/tmp directory so sufficient free space must exist in that directory.
Exit values are:
0 Success
1 Failure
unimvuser - Move a user from one calendar server node to another.
unimvuser -u <user> -host1 <hostname1> -host2 <hostname2> -n1 <node-ID1> -n2 <node-ID2> [-p1 <sysOpPsw1>] [-p2 <sysOpPsw2>] [-up <userPsw>] [-UID <preserve>] [-verbose] unimvuser -v unimvuser -h
unimvuser moves a user from one calendar server node to another.
|
Note: See the WARNINGS section below before attempting to move a user from a 5.0 or greater node to a 4.0 or earlier node. |
The move operation makes the following changes to the user information:
unimvuser logs these changes, along with the rest of its activity, in the /users/unison/log/unimvuser.log file.
It is important to understand that the move operation may still be in progress even after unimvuser has successfully completed. In particular, work is being done by the destination node (the node to which the user has moved) and by remote nodes (where other users reside who may have invited the user). Until the work is complete, the moved user sees an incomplete agenda.
The time required to complete the move operation depends on the number of requests waiting in the request queue of the Corporate-Wide Services daemon/service. For this reason, it is advisable to run unimvuser during off-peak hours for the calendar server.
In addition, the user being moved should not attempt to sign in to the calendar server before unimvuser has completed, nor should any other user attempt to work as a designate for the user being moved. Any changes made under these circumstances will be lost.
Never run more than one unimvuser operation at the same time. Even if the users involved are on different nodes and you run unimvuser on different calendar server hosts, the users may share some meetings or events; this scenario can cause database corruptions.
unimvuser can move a user from a node using an external directory server to a node using the calendar server's internal directory, but cannot move a user from a node using the calendar server's internal directory to a node using an external directory server.
Always use the most recent version of unimvuser, even when moving a user between nodes on calendar server hosts of earlier versions. For example, if your node network has two calendar server hosts of version 5.1 and one host of version 5.2, you should use the unimvuser utility in the bin directory of the 5.2 server.
In addition, it is recommended that you always invoke unimvuser from the command line rather than through the Windows NT administration tool.
Be aware also that differences in the configurations between the source host and the destination host may cause problems or block the move entirely. For example, if the maximum number of instances of a recurring meeting (unison.ini [ENG] maxinstances parameter) on the source server is set higher than on the destination server, and the user to be moved owns a recurring meeting with more instances than the destination host allows, the move will fail.
Note also that users cannot be specified using only the UID key/value pair.
The calendar server must be up to run unimvuser.
<hostname1>
Specify the host name of the source node.
<hostname2>
Specify the host name of the destination node.
<node-ID1>
Specify the source node.
<node-ID2>
Specify the destination node.
<sysOpPsw1>
Provide the SYSOP password for the source node. If this option is not used, prompting for the password occurs.
<sysOpPsw2>
Provide the SYSOP password for the destination node. If this option is not used, prompting for the password occurs.
<user>
Specify the user to be moved. See FORMAT OF THE user ARGUMENT below for details on the proper specification of the user argument. For directory servers, the user must already exist in the directory server used by the destination node.
Preserve original CAPI event UIDs. This option is required if CAPI is used on both the source and the destination node.
<userPsw>
Internal directory only. Specifies a new password for the user. If this option is not used, the user will be able to log into the calendar server without a password. In the case of a directory server, this option has no effect since the password is stored in the directory server and thus remains unchanged.
Use verbose mode.
Print the current version number of unimvuser.
Print a usage message explaining how to run unimvuser.
The user argument is a string of the form "key=value/key=value/...", where "key" is one of those listed below, and "value" is any string. Both "key" and "value" are case insensitive. For all keys except the ID key, the "value" string may be terminated by a wild card symbol (*). If a forward slash "/" is to be included in a string, it should be escaped with the character "\" to prevent it from being interpreted as a key-value pair delimiter - i.e. "S=Hoopla/OU1=R\/D".
If, in a UNIX environment, a shell will be processing the string (e.g. the string is provided on the command line or is passed as an argument to the utility), the string should be enclosed in quotation marks. Furthermore, if characters meaningful to the shell are included in the string, they should be escaped (i.e. preceded by the escape character "\") to prevent the shell from interpreting them.
% unimvuser -u "ID=354" -host1 horus -host2 nut -n1 12 -n2 25
/users/unison/log/unimvuser.log
unimvuser logs its activity in this file.
If you move a user from a 5.0 or greater node to a 4.0 node, the user loses the following data:
For this reason, performing such a move is not recommended. unimvuser warns you of this data loss and asks for confirmation before proceeding with the move.
It is important to understand the implications of the directory server configuration for calendar server utilities. In a supplier-consumer configuration, the scheduling of updates between the consumer and supplier may result in temporary differences between the two. This may mean that a calendar server utility is reading from a consumer directory server that has not yet been synchronized with its supplier.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
uniuser
uninode - Administer a calendar server node network.
uninode -add [-nologinfo] <hostname> uninode -apply [-y | -n] [-nologinfo] [<SysOpPsw>] uninode -cws [-nologinfo] [<node-ID> | <hostname> | <group>] uninode -edit [-e <editor>] [<SysOpPsw>] uninode -import [-nologinfo] [<SysOpPsw>] uninode -init [-nologinfo] [<SysOpPsw>] uninode -reset [-nologinfo] [<node-ID> | <hostname> | <group>] [<SysOpPsw>] uninode -retry [-nologinfo] [<node-ID> | <hostname> | <group>] [<SysOpPsw>] uninode -snc [-nologinfo] [<node-ID> | <hostname> | <group>] uninode -test <node-ID> | <hostname> | <group> uninode -v uninode -h
uninode is a centralized tool for setting up and administering a calendar server node network. See EXAMPLES for an example of setting up a node network. Use uninode to add and remove nodes from the node network, as well as to add and remove connections between nodes. Also use uninode to make queries about the node network configuration and about the status of remote connections.
uninode uses the node network configuration information in the nodes.ini file to configure the node network. Only one nodes.ini file should exist for a node network, regardless of how many calendar servers are linked. Furthermore, you manage the calendar server node network, that is you run uninode, from the machine on which this file exists. When your node network includes coexistence of multiple calendar server versions, always make sure that the host of the nodes.ini file is of the most recent version.
The <sysOpPsw> is the SYSOP password for the node in the calendar server network with the lowest node-ID on the machine hosting the nodes.ini file.
<node-ID>, <hostname> and <group> each restrict uninode's actions to certain nodes in the nodes.ini file. <node-ID> restricts uninode to the specified node, <hostname> to the nodes on the specified host, and <group> to the nodes in the specified group. <group> may be one of the following:
all
all included (+) and all excluded (-) nodes
included
all included (+) nodes
excluded
all excluded (-) nodes
<group> may also be a customized group name. Consult your calendar server Administrator's Guide for further details on the meaning of each of these values. If none of these values are specified, uninode will assume the value all.
If you are using a directory server, you may want to run unidssync on each node before running uninode to ensure that the local information in each node is synchronized with what is in the directory server. Note that all nodes in a calendar server node network must use the same directory server.
uninode only runs if the calendar server is up.
uninode is not used with Business-to-Business (B2B) deployments.
<hostname>
Add all nodes found on the specified host to the nodes.ini file. This option first determines which nodes exist on the specified host. It then removes all lines for that host in the nodes.ini file, and finally adds a line for each node found on the host. Nodes are added as excluded nodes. You must edit the nodes.ini file to include them in the network.
Apply the configuration in the nodes.ini file. The <node-ID>, <group>, and <hostname> arguments restrict the application to specified nodes in the nodes.ini file.
uninode first verifies that:
nodes.ini file is correctuniengd and unisncd servers are upuniengd is greater than A.01.15nodes.ini file exists only on the host currently running uninodeIf any of these verifications fails, uninode terminates.
Otherwise, it proceeds to check the remote node information in each of the nodes involved, and if it finds there are entries missing, it prompts the user to confirm the addition of the missing entries. Use the -y or -n option to automatically provide a response. Note that uninode does not delete any surplus entries from any of the nodes.
Print the following information for each connection between two nodes. This includes information from the CWS daemon/service.
The number of TCP/IP connections, between the two nodes, configured in the nodes.ini file.
The actual number of TCP/IP connections between the two nodes.
The number of CWS requests currently in the CWS queue.
The number of CWS requests processed.
The number of items (users and resources) in the local copy of the remote directory.
<editor>
Safely edit a COPY of the nodes.ini file using the specified text editor. uninode first performs the verifications described in the -apply option and terminates if any of the verifications fails. If all verifications succeed, it invokes the editor. On exit from the editor uninode parses the edited file, and, if it does not find any errors, updates the original nodes.ini file. If uninode finds errors in the edited file, it prompts the user to either re-edit the file or abort the operation.
Same as -apply with the -y option.
Construct a nodes.ini file from the currently running node network configuration. The node with the lowest node-ID on the machine hosting the nodes.ini file is the one from which uninode begins construction of the file. If a nodes.ini file already exists, uninode prompts for confirmation to overwrite it.
Prevent correction of any directory inconsistency when you use the -apply option.
Do not write to the log file. By default, uninode logs any errors, as well as any output it sends to the screen, to the uninode.log file.
Reset the statistics of a Synchronous Network Connection (SNC) daemon. It is recommended that you reset all nodes at the same time by running uninode -reset all. Resetting the statistics allows the administrator to compare the statistics for different nodes at a later time.
Restart the retry mechanism of an SNC daemon. When there are fewer connections available than are configured, the SNC daemon attempts to acquire new connections at specific time intervals. It retries at intervals of 1, 2, 4, 8, 16, 32, and finally every 64 minutes. This option resets the interval to 1 minute. One use of this option might be to run uninode -retry all after a network-related problem is solved.
Print the following information on the TCP/IP connections for the specified node, or for each node in the specified group or on the specified host.
The number of TCP/IP connections to the node configured, as per the information in the nodes.ini file.
The actual number of TCP/IP connections to the node.
The number of connections to the node currently available.
The number of connections to the node currently in use.
The number of times the SNC daemon lost a connection to the node.
The time (expressed in the format <mm>:<ss> format) before the next attempt to reconnect a lost connection.
The number of requests currently in the queue.
The number of cancelled requests.
The number of checks for queued requests. Checks are performed when a connection is waiting in the queue.
The number of requests for connections the SNC daemon/service granted since it started.
Verify that it is possible to connect to a node or group of nodes. See the -apply option for a list of the items uninode -test verifies.
Auto-confirm the correction of any directory inconsistency when you use the -apply option.
Print the current version number of uninode.
Print a usage message explaining how to run uninode.
You have a company with offices in three different countries. Each office runs its own calendar server. You want to set up a node network and manage it from the calendar server running on "gravlax" in Sweden.
nodes.ini file.
% uninode -init
Since no node network currently exists, uninode creates an empty nodes.ini file with sample lines included as comments.
% uninode -add gravlax % uninode -add gnocchi % uninode -add biryani
nodes.ini file.
% cat nodes.ini - H=biryani/N=32 - H=biryani/N=31 - H=gnocchi/N=25 - H=gnocchi/N=24 - H=gnocchi/N=23 - H=gnocchi/N=22 - H=gnocchi/N=21 - H=gravlax/N=13 - H=gravlax/N=12 - H=gravlax/N=11
% vi /users/unison/misc/nodes.ini
The nodes.ini file now contains the following lines.
% cat /users/unison/misc/nodes.ini + H=biryani/N=32/ALIAS=salesIndia/GR=india + H=biryani/N=31/ALIAS=adminIndia/GR=india - H=gnocchi/N=26/ALIAS=tempItaly/GR=italy + H=gnocchi/N=25/ALIAS=supportItaly/GR=italy + H=gnocchi/N=24/ALIAS=financeItaly/GR=italy + H=gnocchi/N=23/ALIAS=r&dItaly/GR=italy + H=gnocchi/N=22/ALIAS=salesItaly/GR=italy + H=gnocchi/N=21/ALIAS=adminItaly/GR=italy - H=gravlax/N=16/ALIAS=tempSweden/GR=sweden + H=gravlax/N=13/ALIAS=r&dSweden/GR=sweden + H=gravlax/N=12/ALIAS=salesSweden/GR=sweden + H=gravlax/N=11/ALIAS=adminSweden/GR=sweden included:2 india:+2 italy:+3 sweden:+2
The node network has the following characteristics:
In this configuration, the total number of connections from node 13 is 22 (two to each of the other nine nodes in the network gives 18, plus two to each of the other two included nodes in the "sweden" group gives 4).
Consult your calendar server's Administrator's Guide for rules on configuring connections between nodes.
Next, apply the configuration. Since this is the first time that nodes "see" other nodes, you expect inconsistencies in their remote node directories. For this reason you use the -y option.
% uninode -apply -y
During execution of this command, uninode prints out information on the work it is performing. For example:
Processing node 11 connected to gravlax, node 11 connected to gravlax, node 12 added 11->12, TCP/IP connection placed a request in the CWS queue to get node 12 user directory
/users/unison/misc/nodes.ini
Contains the list of nodes and the rules that describe the calendar server's node network configuration.
/users/unison/log/uninode.log
By default, uninode logs any errors, as well as any output it sends to the screen, to this file.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unipasswd - Change a calendar server SYSOP or CWSOP password.
unipasswd [-sysop | -cwsop] [-n <node-ID>] [-host <hostname>] [-p <sysOpPsw>] unipasswd -v unipasswd -h
unipasswd changes the password of the SYSOP or CWSOP of a given node. Note that the -sysop and -cwsop options are all mutually exclusive.
The maximum length of a password is 15 characters.
unipasswd only runs if the calendar server is up.
If you use a Business-to-Business (B2B) deployment, always omit the -n option when changing SYSOP and CWSOP passwords. By default, unipasswd will change these passwords for all nodes. See WARNINGS.
Change the password of the CWSOP.
<hostname>
Specify the host on which the operation is to be performed. The default is the local host.
<node-ID>
Specify the node on which the password is to be changed. Required if more than one node exists.
<sysOpPsw>
Provide the current SYSOP password.
Change the password of the SYSOP.
Print the current version number of unipasswd.
Print a usage message explaining how to run unipasswd.
% unipasswd -host jupiter -n 20
% unipasswd -cwsop
Do not change the SYSOP and CWSOP passwords for individual nodes. Doing so may cause the Calendar Administrator web interface to fail. In addition, after changing the SYSOP password, make sure that you update the [ADMINSETTINGS] serverpassword and serveroldpassword parameters in uniwebadm.ini. Failure to do so may cause an interruption in Calendar Administrator services.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
uniping - Ping another calendar server.
uniping [-host <hostname>] [-n <node-ID>] [-u <user>] [-p <password>] [-domain] [-i <sec>] [-allnodes] [-s <size>] [-stats] [-log] [-time] uniping -v uniping -h
uniping sends echo messages to a node or a node network. Receiving nodes reply to the message, and uniping prints the elapsed time between sending the original message and receiving the replies. Use this utility to verify that a node is up, or to measure server response time under various load conditions.
Before sending any messages, uniping first authenticates the specified user on the specified node. uniping only sends messages if this authentication is successful.
uniping runs whether the calendar server is up or down.
Send the echo message to all nodes connected to the node network containing the specified node.
Business-to-Business (B2B) deployments only. Used with the -host option. Checks whether the specified host is running Calendar Domain Services.
<hostname>
Specify the name of a calendar server host. If this option is not used, the local host is assumed.
<sec>
Specify an interval in seconds after which uniping repeats its echo message. If this option is not used, uniping sends one echo message to each specified node.
Print errors to a log file (/users/unison/log/uniping.log).
<node-ID>
Specify a node to connect to. Required if more than one node exists on the calendar server specified by the -host option.
<password>
Provide the password for the user specified by the -u option. If you do not use the -u option, use -p to provide the SYSOP password. If you do not use the -p option, uniping will prompt you for the password.
<size>
Specify the size of the echo message in bytes. The default is 64 bytes.
Display statistics on startup.
Display the time at which each message is sent.
<user>
Specify a user name to use for authentication. If this option is not used, SYSOP is used by default. Please note: this user name must be valid on the node specified by the -n option. Use the -p option to specify this user's password. See "FORMAT OF THE user ARGUMENT" below.
Print the version number of uniping.
Print a usage message explaining how to run uniping.
The user argument is a string of the form "key=value/key=value/...", where "key" is one of those listed below, and "value" is any string. Both "key" and "value" are case insensitive. For all keys except the ID key, the "value" string may be terminated by a wild card symbol (*). If a forward slash "/" is to be included in a string, it should be escaped with the character "\" to prevent it from being interpreted as a key-value pair delimiter - i.e. "S=Hoopla/OU1=R\/D".
If, in a UNIX environment, a shell will be processing the string (e.g. the string is provided on the command line or is passed as an argument to the utility), the string should be enclosed in quotation marks. Furthermore, if characters meaningful to the shell are included in the string, they should be escaped (i.e. preceded by the escape character "\") to prevent the shell from interpreting them.
% uniping -host scribe -n 14 Enter password: scribe,14: 40 ms.
% uniping -n 60 -u "S=Hammett/G=Dashiell" -allnodes -time Enter password: Fri Jul 07 10:23:41 2000: scribe,14: 40 ms. Fri Jul 07 10:23:41 2000: scribe,60: 0 ms. Fri Jul 07 10:23:41 2000: scribe,66: 114 ms.
Exit values are:
0 Success
1 Failure
2 Usage error
unireqdump - View, and optionally delete, requests in the queue of the Corporate-Wide Services (CWS) daemon.
unireqdump [-delete] [-excl <filter>] [-incl <filter>] [-item <itemnum>] [-remotenode <node-ID>] [-prompt] [-reqid <ID>] [-trcode <code>] [-n <node-ID>] [-p <sysOpPsw>] unireqdump -v unireqdump -h
unireqdump outputs the set of requests currently in the queue of the Corporate-Wide Services daemon/service, unicwsd. The utility is also used to delete requests from the queue (using the -delete option).
By default, all requests in the queue are output. The -excl, -incl, -item, -remotenode, -reqid, and -trcode options allow you to select requests satisfying specific criteria. These options are applied successively so each of the requests in the output must meet the combined criteria for all of the options specified.
Numeric arguments can be either decimal or hexadecimal values (where hexadecimal values are prefixed by "0x"). The single exception is the ID argument to the -reqid option, where a hexadecimal value is always assumed, even if the "0x" prefix is not present.
unireqdump can only be run if the calendar server is up.
Enable the deletion option. After each request is output, the user is prompted to confirm whether or not they wish to delete it. The -prompt option may be used along with this option to tell unireqdump to automatically delete ALL of the requests in the output, without prompting for confirmation.
<filter>
Set an exclusion filter. Requests matching this filter are excluded from the output. The possible filters are:
<filter>
Set an inclusion filter. Requests matching this filter are included in the output. The possible filters are listed under the -excl option.
<itemnum>
Select only requests matching the specified item number. itemnum is the numeric ID of the item.
<node-ID>
Specify the node from which the request originated. Required if more than one node exists on the server running unireqdump. The SYSOP password unireqdump requires is the one for this node.
<sysOpPsw>
Provide the SYSOP password. If the password is not supplied on the command line, prompting for it occurs.
Used with the -delete option to tell unireqdump to automatically delete all of the requests in the output, without prompting for confirmation. Use this option with care!
<node-ID>
Select only requests destined for the specified remote node.
<ID>
Select the request with the specified ID. ID is a hexadecimal value (it is not necessary to prefix the value with "0x", though doing so causes no harm).
<code>
Select requests with the specified transaction code. The transaction code may be expressed numerically (the numeric values are available in the documentation for the calendar programming interface), or as one of the following strings:
agendaget attendadd echo eventattend eventcreated eventdeleted eventmodified foreignerdeleted instanceadded instancemodified itemdeleted itemmodified mailmessagepost nodeitemsget notifynewevent notifynewinstance securityadd securitydeleted securitymodified
Print the current version number of unireqdump.
Print a usage message explaining how to run unireqdump.
unireqdump -n 10 -p sysOpPsw
unireqdump -delete -n 10 -p sysOpPsw
unireqdump -excl serviced -p sysOpPsw
unireqdump -delete -excl serviced -remotenode 20 -trcode eventattend -n 10 -p sysOpPsw
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unires - List, add, or delete calendar resources, or modify the information associated with them.
unires -ls [<res>] [-format <format>] [-host <hostname>] -n <node-ID> [-p <sysOpPsw>] unires -format <format> [-host <hostname>] -n <node-ID> [-p <sysOpPsw>]
unires -add <res> [-s <sections>] [-host <hostname>] -n <node-ID> [-p <sysOpPsw>]
unires -del <res> [-y] [-host <hostname>] -n <node-ID> [-p <sysOpPsw>] unires -desdel <res> [-host <hostname>] -n <node-ID> [-p <sysOpPsw>] unires -grpdel <res> [-host <hostname>] -n <node-ID> [-p <sysOpPsw>]
unires -mod <res> -s <sections> | -m <modifier> [-host <hostname>] -n <node-ID> [-p <sysOpPsw>]
unires -ex <filename> [-s <sections>] [-k] [-host <hostname>] -n <node-ID> [-p <sysOpPsw>]
unires -s [<sections>] -n <node-ID> [-p <sysOpPsw>] unires -info unires -v unires -h
unires is used to list, add, or delete calendar resources, and to modify the information associated with them. Resources are identified by their names so each must be unique. Details on how to specify the res argument are given in the FORMAT OF THE res ARGUMENT section below. Note that the -ls, -add, -del, -grpdel, -desdel, and -mod options are all mutually exclusive.
The information associated with a resource is a combination of the key-value pairs described in the FORMAT OF THE res ARGUMENT below and that contained in the resource.ini file (which includes the resource preferences, security, personal group, admin group membership, and the list of users permitted to work as a designate for the resource).
uniuser is the complementary utility for users.
unires can only be run if the calendar server is up.
<res>
Create a new resource. If the resource already exists, an error is reported. The information associated with the new resource is a combination of what is specified in the res argument, and the default values in the resource.ini file. By default, when unires reads the resource.ini file, it considers only the default values in the [GEN] section. Use the -s option to apply default values from other sections of the resource.ini file. Use the -ex option to create multiple resources.
When using the calendar server's internal directory, the "R" key is mandatory for the -add option.
For external directory server contexts, the DID (Directory ID) should be specified in the res argument. If no DID is specified, unires will generate one from the "R=" value. See EXAMPLES.
<res>
Delete the specified resource. unires prompts for confirmation before performing the deletion unless the -y option is used. To delete more than one resource, use the -ex option.
<res>
Delete the list of designates for the specified resource. If more than one resource matches <res>, the command fails.
This option exists only under UNIX. It allows you to first output the list of existing calendar resources to a file, then edit the file to make desired modifications, and finally input the changes back into the node. The following sequence of commands is performed:
% unires -ls -n node-ID > file % vi file % unires -ex file -n node-ID % rm file
<filename>
Perform the additions, deletions and/or modifications specified in filename. Each line of the file must begin with one of the characters `.', `#', `A', `a', `D', `d', `M', `m', `S', `s', or `+'. This initial character specifies the action to take, as follows:
The initial character must be followed by a space and a resource specification. In the case of a modification, the ID for the resource must be supplied; it is used to identify the resource, while the other key-value pairs specified along with it are applied as the modifications. See EXAMPLES.
For each deletion specified in the file, unires prompts for confirmation before performing the deletion. The -y option may be used to automatically provide confirmation.
One way to create this file is to save the output of unires -ls to a file. This can then be edited and input to unires -ex.
The -s sections option may be used with -ex to set the corresponding resource information to the default values contained in the specified sections of the resource.ini file.
For directory servers, the DID can be followed by data in X.400 format. Note that the ability to modify the name of a resource (the "R" key) depends on the directory server.
<format>
This option is used to select resource information fields and customize the format of the output. The -info option lists the parameters that can be used to specify the customized format. These are also listed in the FORMAT OF THE res ARGUMENT section below. If this option is not used, all resource information fields are output, and a default presentation is used. See EXAMPLES.
<res>
Delete the specified resource from all admin groups. A single resource must match <res> or the command fails.
<hostname>
Specifies a host on which to look for the node specified by the -n option. Required for remote hosts. If -host is not present, unires will assume the local host. For modification or deletion, if -host is specified and -n is not, unires will search for a master node on the specified host. If a master node is found, unires will use it to locate the selected users.
List the format parameters used with the -format option.
Used with the -ex option to force unires to process all lines in the file even if it encounters an error. Errors are sent to standard error; use file redirection to capture these to a file.
[<res>]
If a resource is specified, -ls lists that resource (in the specified node). Each output line contains a period (`.'), a space, the resource description, and the ID of the resource. If no resource is specified, all resources in the node are listed. The -format option can be used with -ls to configure the presentation of the output (see EXAMPLES).
<modifier>
Specify a modification to make to the resource information. The modifier is a string of the same form as the <res> argument with the following exceptions: the ID key may NOT be specified, and the PSW key MAY be specified.
<res>
Modify the information associated with the specified resource. This option is used with either the -s sections or the -m modifier option. When used with the -s option, it sets the corresponding information for the resource to the values contained in the specified sections of the resource.ini file. When used with the -m modifier option, modifications are made to the key-value pairs listed in the FORMAT OF THE res ARGUMENT. In the case of a directory server, the ability to modify the name of a resource (the R key) may depend on the directory server.
<node-ID>
Specify a node.
<sysOpPsw>
Provide the SYSOP password for the specified node. If this option is not used, prompting for the password occurs.
[<sections>]
Evaluate all or some of the contents of the resource.ini file and output information from it to standard output.
Use this option without the <sections> argument to determine what sections exist in the resource.ini file. The output in this case is a list of all section names along with their respective "Info" key-value pairs.
Use the <sections> argument to evaluate all of the key-value pairs in the specified sections. In this case all key-value pairs in the specified sections are output, along with any errors detected in these pairs. This is one way to validate the contents of the resource.ini file. See the -add and -mod options for information on using -s <sections> to apply values from resource.ini.
The <sections> argument is a list of one or more section names, each separated by a forward slash (e.g. "GEN/GR1/GR2" specifies the sections GEN, GR1 and GR2). Evaluation is done from left to right. Thus, in the above example, GEN is evaluated first, GR1 second, and GR2 last. Where the same key appears in more than one section, the value of the last instance evaluated takes precedence.
Used with the -del and -ex options to auto-confirm the deletion(s).
Print the current version number of unires.
Print a usage message explaining how to run unires.
The res is a string of the form "key=value/key=value/...", where "key" is one of those listed below, and "value" is any string. Both "key" and "value" are case insensitive. For all keys except the ID key, the "value" string may be terminated by a wild card symbol (*). If a forward slash "/" is to be included in a string, it should be escaped with the character "\" to prevent it from being interpreted as a key-value pair delimiter - i.e. "S=Hoopla/G=James\/Jim".
If, in a UNIX environment, a shell will be processing the string (e.g. the string is provided on the command line or is passed as an argument to the utility), the string should be enclosed in quotation marks. Furthermore, if characters meaningful to the shell are included in the string, they should be escaped (i.e. preceded by the escape character "\") to prevent the shell from interpreting them.
Note that if the ID key-value pair is specified in the res argument, all other key-value pairs specified along with it are ignored. Also note that the PSW key may only be specified in the res argument for the -add option.
The format parameters listed in the third column below are used with the -format option to configure the presentation of a listing (see EXAMPLES).
% unires -ls "R=HPLaser*" -n 12 Enter SysOp password: . R=HPLASER dorian/S=Wilde/G=Oscar/ID=438 . R=HPLASER sula/S=Morrison/G=Toni/ID=512
% unires -ls "R=HPLaser*" -format "%r Contact: %g %s" -n 12 Enter SysOp password: HPLASER dorian Contact: Oscar Wilde HPLASER sula Contact: Toni Morrison
% unires -format "%r: %g %s" -n 12 Enter SysOp password: HPLASER dorian: Oscar Wilde HPLASER sula: Toni Morrison RedRoom: Jeannette Winterson BlueRoom: James Thurber Apple Laptop: Audre Lorde SGI Indy: Milan Kundera Olivetti Typewriter: Dashiell Hammett
% unires -add "R=oakroom" -n 12
% unires -add "DID=cn=oakroom,o=Acme,c=US" -n 12
% unires -mod "R=oakroom" -m "CA=15" -n 12
Multiple additions, deletions, modifications are done using the -ex option. In this example two new resources are added (a BetaCam and a VCR; the contact for the BetaCam is specified at the same time as the add is being done), the capacity of an existing resource is modified, and an existing resource is deleted. A directory server is being used.
% vi multiple.dat % cat multiple.dat A DID=cn=betacam,o=Acme,c=US/S=Fellini/G=Fred A DID=cn=vcr1,o=Acme,c=US M R=RedRoom/CA=25/ID=441 D R=BlueRoom
Note that in the case of the modification, the resource is the one which has ID=441; the capacity of the resource is modified to "25".
unires:
% unires -ex multiple.dat -n 12
unires: added "cn=betacam,o=Acme,c=US" unires: added "cn=vcr1,o=Acme,c=US" unires: modified "RedRoom" unires: deleted "BlueRoom"
unires.ini
This file specifies possible calendar resource configurations. See also the calendar server Reference Manual, Appendix A, "User and Resource Parameters".
It is important to understand the implications of the directory server configuration for calendar server utilities. In a supplier-consumer configuration, the scheduling of updates between the consumer and supplier may result in temporary differences between the two. This may mean that a calendar server utility is reading from a consumer directory server that has not yet been synchronized with its supplier.
This utility uses the [UTL] adm_modres<field> parameters in unison.ini to determine whether or not it can modify the corresponding resource key-value pairs. For example, if adm_modrescapacity is set to "FALSE", then the value associated with the CA key cannot be modified by this utility.
If no corresponding adm_modres<field> for a particular key appears in the file, the utility assumes it CAN modify it.
Deleting resources with a large numbers of meetings and events can take a long time and cause a decrease in performance for other calendar users. It is recommended that you delete such resources outside of normal hours, or at least not at times of peak calendar usage.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
uniuser is the complementary utility for users
unirmold - Remove old events and tasks from agendas in a calendar server database.
unirmold [<user>] [-event | -task] [-n <numOfDays>] [-y] <node-ID> [-p <sysOpPsw>] [-include <types>] [-sync] unirmold -res [<resource>] [-n <numOfDays>] [-y] <node-ID> [-p <sysOpPsw>] unirmold -v unirmold -h
unirmold removes events and/or tasks older than a specified number of days from agendas in a calendar server database.
To remove an event from an agenda, unirmold "uninvites" the owner of the agenda from the event. This has two consequences: the event no longer appears in that agenda AND the owner of that agenda no longer appears on the list of invitees to the event. The update to the list of invitees propagates as necessary to the other nodes in the node network.
By default, unirmold removes all events and tasks older than 90 days from all user agendas in the node and all events older than 90 days from all resource agendas in the specified node. The -res option restricts unirmold to events in resource agendas. The <user> argument restricts unirmold to the agendas of the specified users. See FORMAT OF THE <user> ARGUMENT below for details on how to specify <user>.
When using unirmold in -res mode, you may specify a resource filter using the <resource> argument. See FORMAT OF THE <resource> ARGUMENT below for details on how to specify <resource>.
|
Note:
|
unirmold only runs if the calendar server is up.
Delete only old events. By default unirmold deletes both events and tasks from the user agenda.
<types>
Delete events which are special types of events. Currently this option applies only to events which are either Outlook journal entries or sticky notes. The <types> argument is one or more of the following: journal, sticky. For example, to delete both events which are journal entries and events which are sticky notes, use -include journal sticky. To delete only events which are sticky notes, use -include sticky.
<numOfDays>
Delete events and tasks that are more than <numOfDays> days old from the agenda. If you do not use this option, the default value is 90 days. The minimum value is 30 days.
<sysOpPsw>
Provide the SYSOP password for the node. If you do not use this option, unirmold prompts for the password.
<resource>
Remove all events in resource agendas only. You may specify a filter to select specific resources by providing the <resource> argument. See FORMAT OF THE <resource> ARGUMENT below for details.
Removes all sync records from the user agenda.
Delete only old tasks from the user agenda. If this option is not used, both events and tasks are deleted.
Eliminate prompting for confirmation of any deletions.
Print the current version number of unirmold.
Print a usage message explaining how to run unirmold.
The user argument is a string of the form "key=value/key=value/...", where "key" is one of those listed below, and "value" is any string. Both "key" and "value" are case insensitive. The "value" string may be terminated by a wild card symbol (*). If a forward slash "/" is to be included in a string, it should be escaped with the character "\" to prevent it from being interpreted as a key-value pair delimiter - i.e. "S=Hoopla/OU1=R\/D".
If, in a UNIX environment, a shell will be processing the string (e.g. the string is provided on the command line or is passed as an argument to the utility), the string should be enclosed in quotation marks. Furthermore, if characters meaningful to the shell are included in the string, they should be escaped (i.e. preceded by the escape character "\") to prevent the shell from interpreting them.
|
Note: If the ID key-value pair is specified in the user argument, all other key-value pairs specified along with it are ignored. |
The <resource> is a string of the form "key=value/key=value/...", where "key" is one of those listed below, and "value" is any string. Both "key" and "value" are case insensitive. For all keys except the ID key, the "value" string may be terminated by a wild card symbol (*). If a forward slash "/" is to be included in a string, it should be escaped with the character "\" to prevent it from being interpreted as a key-value pair delimiter - i.e. "S=Hoopla/G=James\/Jim".
If, in a UNIX environment, a shell will be processing the string (e.g. the string is provided on the command line or is passed as an argument to the utility), the string should be enclosed in quotation marks. Furthermore, if characters meaningful to the shell are included in the string, they should be escaped (i.e. preceded by the escape character "\") to prevent the shell from interpreting them.
Note that if the ID key-value pair is specified in the <resource> argument, all other key-value pairs specified along with it are ignored.
| Key | Field | Format parameter |
|---|---|---|
|
|
Resource name |
%R |
|
|
Resource number |
%N |
|
|
Identifier |
%ID |
% unirmold 10
% unirmold "s=wembley" -event -n 30 10
% unirmold -res -n 30 10
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unirndel - Delete a remote node from a local calendar server node database.
unirndel remoteNoteId [<sysOpPsw>] [-n <node-ID>] unirndel -v unirndel -h
unirndel deletes all references to a remote node from the database of a local node. By default the local node is the one with the name "N1". unirndel should only be used to delete a remote node created for test purposes. You should consult Oracle Support before using unirndel.
It is recommended that you back up the local /users/unison/db directory before running unirndel.
unirndel runs only if the calendar server is up.
<node-ID>
Specifies the node-ID of the local node database from which the remote node should be deleted.
Print the current version number of unirndel.
Print a usage message explaining how to run unirndel.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unirnsynch - Propagate deletions in the local information of one node to another node in the network.
unirnsynch -rn <node-ID> [-rhost <hostname>] [-rp <remote-sysop-password>] -n <node-ID> [-host <hostname>] [-p <sysop-password>] unirnsynch -v unirnsynch -h
unirnsynch is used to propagate deletions in the local information of one node to another node in the network. Each node in a node network contains both local information and remote node information, where:
The remote node information of a given node is constructed from the local information of each of the other nodes in the node network.
Changes to the local information of a node are normally automatically propagated to the remote node information of all other nodes in the network. However, if for any reason discrepancies do occur, the remote node information can be updated using unirnsynch and/or uninode. uninode (using the -apply option) may be used to add missing entries while unirnsynch is used to delete entries which no longer exist in the local information.
uninode -cws all may be used to determine whether or not discrepancies exist (see the IMPORT-DIR field of the output).
The calendar server must be up to run unirnsynch.
<hostname>
Specify the host where the node that has had deletions to local information resides.
<node-ID>
Specify the node-ID of the node that has had deletions to its local information.
<sysOpPsw>
Provide the SYSOP password of the node that has had deletions to its local information.
<hostname>
Specify the host where the node that is to have its remote node information updated resides. Default is the local host.
<node-ID>
Specify the node-ID of the node that is to have its remote node information updated.
<remote-sysOpPsw>
Provide the SYSOP password of the node that is to have its remote node information updated.
Print the current version number of unirnsynch.
Print a usage message explaining how to run unirnsynch.
% unirnsynch -rn 20 -rhost salt -rp remote-sysOpPsw -n 30 -host pepper -p sysOpPsw
Exit values are:
0 Success
1 Usage error
2 System error
uninode
unisizeof - Compute the size of the calendar server installation.
unisizeof [-db | -n <node-ID>] unisizeof -v unisizeof -h
unisizeof computes the size of a calendar server installation. By default, it determines the size of the /users/unison directory, including all database nodes and the calendar server (executables, *.ini files, etc.). Use the -db option to determine the size of the entire database and the -n option to determine the size of a single database node.
unisizeof runs whether the calendar server is up or down.
Compute the size of the entire database. The entire database is made up of all nodes on the server.
<node-ID>
Compute the database size of the specified node.
Print the version number of unisizeof.
Print a usage message explaining how to run unisizeof.
% unisizeof unisizeof: total size of the calendar server 44216K
% unisizeof -db unisizeof: total size of the calendar server database is 10010K
% unisizeof -n 10 unisizeof: database size for nodeid [10] is 760K
/users/unison/misc/unison.ini
Used to determine the default node (i.e. the node for which "name = N1" in this file) when unisizeof is used with the -db option.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unislice - Extract information from the calendar server's log files.
unislice <logFile(s)> [-s <starttime>] [-e <endtime>] unislice -v unislice -h
unislice extracts information from the specified log file(s) and sends it to standard output. The unisnapshot utility uses unislice to gather information contained in log files. The <logFile(s)> argument is a list of one or more log files; each must be a fully-specified pathname separated from the others by a space. unislice can run on most of the log files in the /users/unison/log directory.
unislice runs whether the calendar server is up or down.
<endtime>
Set an end time. Only log file information with time stamps prior to this time are included in the output. Thus, if an end time of January 1 is set, no information from the 1st of January is included. See FORMAT OF starttime, endtime ARGUMENTS below for details on how to specify these arguments.
<starttime>
Set a start time. Only log file information with time stamps on or after this time are included in the output. See FORMAT OF starttime, endtime ARGUMENTS below for details on how to specify these arguments.
Print the current version number of unislice.
Print a usage message explaining how to run unislice.
Each of these arguments can take one of the forms:
where
is a number between 1 and 31;
is either the full name of the month or one of the following abbreviations: jan, feb, mar, apr, aug, sep, sept, oct, nov, dec (month is case-insensitive);
is specified using four digits; and
is in the form HH:MM or HH:MM:SS (HH is an integer between 0 and 23).
uniengd log file:
% unislice /users/unison/log/eng.log
uniengd messages logged on February 7th 1995:
% unislice /users/unison/log/eng.log -s 7 feb 1995 -e feb 8 1995
eng.log messages after 1 PM, July 7:
% unislice /users/unison/log/eng.log -s july 7 13:00
eng.log messages before 9 AM, October 15, 1995:
% unislice /users/unison/log/eng.log -e oct 15 9:00 1995
eng.log messages logged in a 45-second period starting at 10 AM, January 30:
% unislice /users/unison/log/eng.log -s jan 30 10:00:00 -e jan 30 10:00:46
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unisnapshot
unisnapshot - Compile calendar server information for diagnostic purposes.
unisnapshot [<date>] [-nolog] [-p <sysOpPsw>] unisnapshot [-s <starttime>] [-e <endtime>] [-nolog] [-p <sysOpPsw>] unisnapshot -v unisnapshot -h
unisnapshot assembles information used by support staff to diagnose most calendar server problems. Should a problem ever arise, only this file need be supplied to support staff.
Output is written to the unisnapshot.log file in the /users/unison/log directory. unisnapshot can be restricted to include log file information logged during a single day, or during a specified time period. This reduces the amount of irrelevant information in the output.
Under Windows operating syatems, unisnapshot requires the SYSOP password for each node. See the -p option below for more information.
See FORMAT OF THE date ARGUMENT below for details on how to specify <date>.
unisnapshot can be run whether the calendar server is up or down.
<endtime>
Set an end time. Only log file information with time stamps prior to this time are included in the output of unisnapshot. Thus, if an end time of January 1 is set, no information from the 1st of January is included. <endtime> is a string of the same format as <date>.
Prevent unisnapshot from including log file information in its output.
<sysOpPsw>
This option exists only under Windows operating systems. Specify the SYSOP password to use to connect to each node. If you use this option, the SYSOP password must be the same for all nodes. If you do not use this option under Windows, unisnapshot prompts for the SYSOP password for the first node at the time it connects to that node. For each subsequent node, it prompts for the SYSOP password only if the SYSOP password for that node is different from the last SYSOP password entered.
<starttime>
Sets a start time. Only log file information with time stamps on or after this time are included in the output of unisnapshot. <starttime> is a string of the same format as date.
Print the current version number of unisnapshot.
Print a usage message explaining how to run unisnapshot.
The date argument takes one of the forms:
where
is a number between 1 and 31;
is either the full name of the month or one of the following abbreviations: jan, feb, mar, apr, aug, sep, sept, oct, nov, dec (month is case-insensitive);
is specified using four digits; and
is in the form HH:MM or HH:MM:SS (HH is an integer between 0 and 23).
If no year is specified, the default is the current year.
% unisnapshot
% unisnapshot -nolog
% unisnapshot 7 feb 1998
% unisnapshot -s july 7 13:00
% unisnapshot -e oct 15 9:00 1998
% unisnapshot -s jan 30 10:00:00 -e jan 30 10:00:46
/users/unison/log/unisnapshot.log
This is the file where unisnapshot writes its output. If a previous file exists at the time unisnapshot is invoked, it is overwritten.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unisnapshot may take some time to complete.
unisncdump - Retrieve statistics from the calendar server's Synchronous Network Connection daemon/service.
unisncdump [-host <hostname>] [-n <node-ID>] [-p <sysOpPsw>] [-screen] unisncdump -v unisncdump -h
unisncdump retrieves statistics from the unisncd daemon and writes them to the /users/unison/log/unisncdump.log file. Included are the number of configured and available connections for each service.
<hostname>
Specify the host on which the unisncd is located.
<node-ID>
Specify the calendar server node. Required if more than one node exists.
<sysOpPsw>
Provide the SYSOP password. If this option is not used, prompting for the password occurs.
Display the output on the screen instead of writing it to the log file.
Print the version number of unisncdump.
Print a usage message explaining how to run unisncdump.
unisncd statistics for node 11 on host "oregano" to the screen (the node network contains two nodes: 11 and 12).
% unisncdump -screen -n 11 -host oregano Enter SysOp password: ----------------------------------------------- DATE = Mon Sep 28 14:50:08 1998 PID = 1314 Host = oregano Service = unieng,12 Transactions: Request = 0 Check Request = 0 Cancel Request = 0 Free = 0 Connections: Configured = 2 Available = 2 Granted = 0 Request queue = 0 Failed = 0 Last failure = 0 Next attempt = 0 Attempt timeout = 0 Max wait before retry = 3840
/users/unison/log/unisncdump.log
unisncdump writes to this file by default.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unistart - Start up the calendar server.
unistart [-bypass] [-nocws | -cws] [-nosnc | -snc] [-das] [-r] [-w <secs>] [-c] [-n] [-s] unistart -v unistart -h
unistart starts the calendar server. The default action is to start all 5 the calendar server daemons/services, in the following order: unilckd, uniengd, unidasd (if a Directory Server is being used), unisncd, and unicwsd. If you start any of the daemons/services manually, you must respect this order to avoid problems. For example, if you start unisncd manually, you must be certain that unilckd, uniengd, and unidasd (if you are running a Directory Server) are all running, and that unicwsd is not running.
By default, unistart calls unicheck to check the file system. It invokes unicheck with the option "-maxdb 30", restricting the check to including only the first 30 node databases.
By default, unicheck is run before the daemons/services are started. This option causes unistart to execute without running unicheck.
Same as -cws. Included for backwards compatibility.
Starts only unicwsd, the Corporate-Wide services daemon/service, provided that the unilckd and uniengd daemons/services are up. To avoid problems, you should also be certain that unidasd (if you are running a Directory Server) and unisncd are running.
Starts only unidasd, provided that the unilckd and uniengd daemons/services are up. Note that this daemon is used only with directory servers. To avoid problems, you should also be certain that unisncd and unicwsd are not running.
Same as -nocws. Included for backwards compatibility.
By default, unicwsd is started if the [CWS] enable parameter in unison.ini is set to "TRUE". This option overrides this setting and prevents unicwsd from being started. If this option is used under NT, unicwsd can be brought up later by simply running unistart again without this option.
By default, unisncd is started if the [SNC] enable parameter in unison.ini is set to "TRUE". This option overrides this setting and prevents unisncd from being started.
Removes the log files act.log, cws.log, das.log, dbv.log, eng.log, lck.log, and snc.log from the /users/unison/log directory. Note that new log files are immediately created for cws.log, das.log, eng.log, lck.log, and snc.log.
Same as -w. Included for backwards compatibility.
Starts only unisncd, provided that the unilckd and uniengd daemons/services are up. To avoid problems, you should also be certain that unidasd (if you are running a Directory Server) is running and unicwsd is not running.
<secs>
When a process is started there is a short delay before a ps(1) command acknowledges the existence of the process. It is therefore appropriate to sleep until a ps(1) verifies that the process is running. The default period is 2 seconds. This option can be used to override this default; the <secs> argument specifies the number of seconds to sleep.
Print the current version number of unistart.
Print a usage message explaining how to run unistart.
unicheck; remove the old log files at the same time:
% unistart -bypass -r
% unistart -nocws
% unistart -cws
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unistat - Produce a report on a calendar server node.
unistat [-l | -p] [-s | -g] [-m] [-sn] -n <node-ID> unistat -v unistat -h
unistat produces a report for the specified node and sends it to standard output. unistat prompts the user for the SYSOP password for the node. The following information is included in the report:
The calendar server must be up for unistat to run.
Print the list of public groups.
Print the report in 128 characters per line mode. If this option is not used, the default is 80 characters per line.
Print the members of the public groups.
<node-ID>
Generate statistics for the specified node.
|
Note: On UNIX, the -n is optional; a node-ID may be specified on the command line without being preceded by -n. |
Create a PostScript report. File redirection should be used to capture this to a file.
Print database statistics.
Print serial numbers. Obsolete with Oracle Collaboration Suite.
Print the current version number of unistat.
Print a usage message explaining how to run unistat.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unistats - Display summary statistics of the data in a calendar server stats file.
unistats [-s <starttime>] [-e <endtime>] [-f <filename>] [-server <version>] [-client <entry>] [-n <node-ID>] [-user <name> | -res <resource> | -ruser] [-all] unistats -v unistats -h
Displays summary statistics of the data in a calendar server stats file. By default, the input file is /users/unison/log/stats.log. Filters (i.e. the -server, -client, -n, -user, -res, -ruser options) may be used to compile statistics from a subset of the information in the stats file.
The default output is a summary for each unique client. Different versions of the same client are treated as separate clients, and a summary is output for each. The -all option displays a summary incorporating all clients. All output is displayed in 122-character-wide format. A complete list of all output fields is given in the OUTPUT section below.
Display summary incorporating all interface clients.
<entry>
Display summary statistics on a specific calendar client. <entry> is the name and version of that client. See FORMAT OF THE entry, name, AND resource ARGUMENTS below for details on how to specify <entry>.
<endtime>
Specify end time for statistics. If this option is not used, the default is the current time of the current day of the current month of the current year. See FORMAT OF THE time ARGUMENT below for details on how to specify <endtime>.
<filename>
Specify the file to be used. This file must be in the same format as the default input file /users/unison/log/stats.log. This option is commonly used where a file has been created from an existing stats.log file and is supplied as input to unistats.
<node-ID>
Display summary statistics on a specific node. <node-ID> is a calendar server node-ID.
<resource>
Display summary statistics on a specific resource. <resource> is the name and/or identification number of the resource. See FORMAT OF THE entry, name, AND resource ARGUMENTS for details on how to specify <resource>.
Display summary statistics on all reserved users (e.g. SYSOP).
<starttime>
Specify a start time for the statistics. If this option is not used, the default start time is "Jan 1 1991 00:00:00". See FORMAT OF THE time ARGUMENT below for details on how to specify <starttime>.
<version>
Display summary statistics on a specific calendar server. <version> is the version number of that server (e.g. A.02.90).
<name>
Display summary statistics on a specific user. <name> is some combination of the surname, given name, and organizational units of the user. See FORMAT OF THE entry, name, AND resource ARGUMENTS below for details on how to specify <name>.
Print the current version number of unistats.
Print a usage message explaining how to run unistats.
Each of the arguments <entry>, <name>, and <resource> is a string of the form "key=value/key=value/...", where "key" is one of those listed below, and "value" is any string. Both "key" and "value" are case insensitive. The "value" string may be terminated by a wild card symbol (*). If a forward slash "/" is to be included in a string, it should be escaped with the character "\" to prevent it from being interpreted as a key-value pair delimiter - i.e. "S=Hoopla/OU1=R\/D".
If, in a UNIX environment, a shell will be processing the string (e.g. the string is provided on the command line or is passed as an argument to the utility), the string should be enclosed in quotation marks. Furthermore, if characters meaningful to the shell are included in the string, they should be escaped (i.e. preceded by the escape character "\") to prevent the shell from interpreting them.
Note that if the ID key-value pair is specified in the -res argument, all other key-value pairs specified along with it are ignored.
Some example specifications are:
-client "N=Windows CorporateTime - 32 Bit/V=version 4.1" -user "S=Carter/G=Angela" -res "R=laptop" -res "ID=328"
The <starttime> and <endtime> arguments may be expressed as either:
where
The order of the individual elements in the argument is unimportant. What is important is that either day and month be specified, or time be specified. The following are all valid examples:
Feb 22 1996 10:00:00 22 february 10:00:00 10:00:00 february 22 1996 1996 feb 22 feb 22 10:00:00
Default values for <day>, <month>, <year>, and <time> are the current day, current month, current year and current system time respectively.
Any missing field in <time> (HH, MM, or SS) is replaced with the current HH, MM, or SS value. E.g. if the current date and time is March 12 1998 10:41:34, and only HH:MM are specified in the argument, the SS becomes "34":
-e 12:41-> March 12 1998 12:41:34-s 12:41-> March 12 1998 12:41:34
If none of the time fields are specified, <starttime> defaults to the first minute of the day, and <endtime> defaults to the last minute of the day:
-s feb 22-> feb 22 1998 00:00:00-e feb 22-> feb 22 1998 23:59:59
All output fields displayed by unistats are explained here, in the order in which they will be seen:
/users/unison/log/stats.log):
% unistats
myfile.log:
% unistats -client "N=window*" -f myfile.log
% unistats -user "s=martin/g=don" -server "A.02.90"
% unistats -res "R=projector/ID=901" -client "N=Motif"
% unistats -s jul 19 -e jul 19
% unistats -all -user "S=*"
% unistats -ruser -n 70
/users/unison/log/stats.log
By default, unistats obtains its information from this file. The [ENG] stats parameter in unison.ini must be set to "TRUE" to enable uniengd to log information to this file.
/users/unison/log/unistats.log
unistats logs any errors in this file.
Exit values are:
0 Success
1 usage error
2 system error
unistatus - Determine the status of the calendar server.
unistatus [-f] [-d] [-s] [-q] [-n] [-e] unistatus -v unistatus -h
By default unistatus determines which of the calendar server daemons/services are running and prints their current status to standard output. The -d, -f, -n, -q, and -s options are currently supported only on UNIX platforms.
unistatus runs whether the calendar server is up or down.
Produce a report for daemon processes only.
Alter the default exit status values to provide information about the calendar server daemon/services. See EXIT STATUS below for the values and their meanings.
Produce an extensive ps-like report, taking into account the distinction between daemons and servers. The calendar server may have the following daemons and servers running:
uniengd daemon: always runnningunilckd daemon: always runningunieng server: one for each signed-on userunicwsd daemon: runs if corporate-wide services are enabledunisncd daemon: runs if remote-node services are enabled and/or a directory server is being usedunidasd daemons and servers: runs if a directory server is being usedSuppress the printing of the messages "CORPORATE-WIDE SERVICES are down" or "REMOTE-NODE SERVICES are down" when the unilckd and uniengd daemons/services are running but the unicwsd or unisncd daemons/services are not.
Force the quiet version of the command which does not produce the usual status message.
Produce a report for server processes.
Print the current version number of unistatus.
Print a usage message explaining how to run unistatus.
unistatus under NT.
% unistatus unistatus: unicwsd is running unistatus: unisncd is running unistatus: unidasd is running unistatus: uniengd is running unistatus: unilckd is running
% unistatus -f UID PID PPID STIME TIME COMMAND CLASS unison 23846 1 Sep 25 2:02 unilckd daemon unison 23851 1 Sep 25 0:00 uniengd daemon unison 23927 1 Sep 25 0:00 unidasd daemon unison 24007 1 Sep 25 0:00 unisncd daemon unison 24014 1 Sep 25 0:28 unicwsd daemon unison 24117 23851 Sep 25 0:18 uniengd server unison 24120 23851 Sep 25 0:16 uniengd server unison 24123 23851 Sep 25 0:16 uniengd server unison 24132 23851 Sep 25 0:00 uniengd server unison 24153 23851 Sep 25 0:00 uniengd server unison 24111 23927 Sep 25 0:00 unidasd server unison 24129 23927 Sep 25 0:00 unidasd server unison 24151 23927 Sep 25 0:00 unidasd server unison 24172 23927 Sep 25 0:00 unidasd server unison 24178 23927 Sep 25 0:00 unidasd server unistatus: the calendar server is up
% unistatus -s UID PID PPID STIME TIME COMMAND CLASS unison 24117 23851 Sep 25 0:18 uniengd server unison 24120 23851 Sep 25 0:16 uniengd server unison 24123 23851 Sep 25 0:16 uniengd server unison 24132 23851 Sep 25 0:00 uniengd server unison 24153 23851 Sep 25 0:00 uniengd server unison 24111 23927 Sep 25 0:00 unidasd server unison 24129 23927 Sep 25 0:00 unidasd server unison 24151 23927 Sep 25 0:00 unidasd server unison 24172 23927 Sep 25 0:00 unidasd server unison 24178 23927 Sep 25 0:00 unidasd server unistatus: the calendar server is up
% unistatus -d UID PID PPID STIME TIME COMMAND CLASS unison 23846 1 Sep 25 2:02 unilckd daemon unison 23851 1 Sep 25 0:00 uniengd daemon unison 23927 1 Sep 25 0:00 unidasd daemon unison 24007 1 Sep 25 0:00 unisncd daemon unison 24014 1 Sep 25 0:28 unicwsd daemon unistatus: the calendar server is up
The default exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
Use of the -e option alters the default exit values to encode the status of the various calendar server daemons/services. These values are as follows:
unistop - Shut down the calendar server.
unistop [-y] [-bypass] [-ser] [-cws] [-snc] [-das] [-dass] [-w <secs>] [-l <level>] [-cl <level>] unistop -v unistop -h
unistop shuts down all or part of a running calendar server. By default, all daemons/services are shut down, in the following order: unicwsd, unisncd, unidasd (if a directory server is being used), uniengd, and unilckd. If any users are currently signed-on, unistop prompts for confirmation before proceeding with the shutdown. If you stop any of the daemons/services manually, you must respect this order to avoid problems. For example, if you stop unisncd manually, you must be certain that unicwsd is not running and that unilckd, uniengd, and unidasd (if you are running a Directory Server) are all running.
The -bypass, -cl, -das, -dass, -l, -ser, -snc, -w, and -y options are all UNIX-only. The -l and -cl options are mutually exclusive.
unistop can only be run if the calendar server is at least partially up (i.e. one or more daemons/services are running).
Allow unistop to execute even if another unistart or unistop process is running.
<level>
Allow cycling of shutdown levels from 0 up to the specified level, when the current level fails. Thus, levels 0, 1, 2, & 3 are tried until either the specified level is reached or the shutdown is successful. The user is NOT prompted for any confirmation.
|
Warning: A shutdown at level 3 may corrupt the calendar server database. See the -l option for more information. |
Shut down only the Corporate-Wide Services daemon/service (unicwsd). The unilckd and uniengd daemons/services must be running for this option to succeed. To avoid problems, you should also be certain that unisncd and unidasd (if you are running a Directory Server) are both running.
Stop only the unidasd daemons and servers. These are used only with a directory server. The unilckd and uniengd daemons/services must be running for this option to succeed. To avoid problems, you should also be certain that unicwsd and unisncd are both running.
Stop only the unidasd servers. These are used only with a directory server.
<level>
The shutdown levels are 0, 1, 2 and 3, with the normal level (and the default) being 0. The higher the number, the more severe the shutdown. You should always begin with 0 and only in the rare event that this fails should you proceed to 1, then 2 and finally 3.
Shut down only the uniengd servers. The unilckd and uniengd daemons must be running for this option to succeed. Each uniengd server is associated with a signed-on calendar user; the uniengd daemon is always present when the calendar server is running. If this option is not used, both uniengd daemons and servers are shut down.
Shut down only the unisncd daemon. The unilckd and uniengd daemons must be running for this option to succeed. To avoid problems, you should also be certain that unidasd (if you are running a Directory Server) is running and unicwsd is not running.
<secs>
When a process is stopped there is a short delay during which the ps(1) command continues to acknowledge the existence of the process. It is therefore necessary to sleep for a short period of time until a ps verifies that the process is no longer running. The default delay is 4 seconds. This option overrides the default; the <secs> parameter specifies the number of seconds to sleep.
By default, if there are any users signed on to the calendar server, a prompt is issued to confirm that a shutdown is desired. This option causes unistop to automatically proceed with the shutdown even if there are users signed on. The shutdown of each of the active uniengd servers proceeds in such a way as to ensure the integrity of the database.
Print the current version number of unistop.
Print a usage message explaining how to run unistop.
% unistop
% unistop -cws
% unistop -das
% unistop -l 1
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unisyncrefresh - Refresh calendar server sync records.
unisyncrefresh [-node <node-ID>] [-host <hostname>] [-fr <date>] [-p <SYSOPpassword>] unisyncrefresh -v unisyncrefresh -h
unisyncrefresh refreshes calendar server synchronization records.
If you are experiencing long refresh times when piloting newer calendar clients including 3.0 versions of the Sync clients and Outlook Connector 3.3 with a small number of users, you can increase performance by creating a script to run unisyncrefresh automatically every 5 to 15 minutes.
unisyncrefresh can only be run if the calendar server is up.
<date>
Forces a specified start date for the refresh. This option is not recommended for general use; consult Oracle support for instructions on using this option in specific circumstances.
<hostname>
Specifies a host on which to look for the node specified by the -n option. Required for remote hosts. If -host is not present, unisyncrefresh will assume the local host. If -host is specified and -n is not, unisyncrefresh will search for a master node on the specified host.
<node-ID>
Specify a node. If -n is not used, unisyncrefresh will search for a master node located on the host specified by the -host option. If no master node exists, -n is required.
<SYSOPpassword>
Provide the SYSOP password for the specified node. If this option is not used, unisyncrefresh will prompt for the password.
Print the current version number of unisyncrefresh.
Print a usage message explaining how to run unisyncrefresh.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unitzinfo - Print information about a calendar server time zone.
unitzinfo [-c] [-l] [-t <timezone>] [-node <node-ID>] [-y <year>] unitzinfo -v unitzinfo -h
Extracts information from the calendar server time zone table found in the /users/unison/misc/timezone.ini file. By default, only the information for the configured time zone and the current year used by the calendar server is printed in an 80-character-wide format.
The calendar server table contains time zone information from the year 1991 to 2074 inclusive.
unitzinfo can be run whether the calendar server is up or down.
List the time zone information by country. Time zones within a country are listed in sequence. The printed fields are:
Print the information in 132-character-wide ("large") output format.
<node-ID>
Specify the node. This option causes the information for the time zone configured for the node to be output.
<timezone>
Specify the name of the time zone to print. If timezone has the value "all", the complete list of time zones is printed.
<year>
Specify the year for which the time zone information will be output (e.g. to view the DST period for that year). <year> must be specified using four digits. The default is the current year.
Print the current version number of unitzinfo.
Print a usage message explaining how to run unitzinfo.
% unitzinfo -node 20 EST5EDT Eastern Standard Time, Eastern Daylight Time U.S.A. (Eastern), Canada (Eastern), Bahamas, Haiti, Turks & Caicos Hours from GMT: -5h Daylight Saving Time : -4h (Apr 4,1999 - Oct 30,1999)
/users/unison/misc/timezone.ini
This file contains the time zone descriptions used by the calendar server.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
uniuser - List, add, or delete calendar users, or to modify the information associated with them.
uniuser -ls [<user>] [-format <format>] [-host <hostname>] -n <node-ID> [-p <sysOpPsw>] uniuser -format <format> -n <node-ID> [-p <sysOpPsw>]
uniuser -add <user> [-s <sections>] [-host <hostname>] -n <node-ID> [-p <sysOpPsw>]
uniuser -del <user> [-y] [-host <hostname>] [-n <node-ID>] [-p <sysOpPsw>] uniuser -desdel <user> [-host <hostname>] [-n <node-ID>] [-p <sysOpPsw>] uniuser -grpdel <user> [-host <hostname>] [-n <node-ID>] [-p <sysOpPsw>]
uniuser -mod <user> -s <sections> | -m <modifier> [-host <hostname>] [-n <node-ID>] [-p <sysOpPsw>]
uniuser -ex <filename> [-s <sections>] [-k] [-host <hostname>] [-n <node-ID>] [-p <sysOpPsw>] uniuser -edit [-host <hostname>] [-n <node-ID>] [-p <sysOpPsw>]
uniuser -s [<sections>] [-host <hostname>] -n <node-ID> [-p <sysOpPsw>] uniuser -info uniuser -v uniuser -h
uniuser can list, add, or delete calendar users, or modify the information associated with them. See the FORMAT OF THE user ARGUMENT section below for details on how to specify the user argument. Note that the -ls, -add, -del, -grpdel, -desdel, and -mod options are all mutually exclusive.
The information associated with a calendar user is a combination of the key-value pairs described in the FORMAT OF THE user ARGUMENT below, and that contained in the user.ini file. This includes user preferences, security, administrative rights, X.400 information, personal group, admin group membership and the list of persons permitted to work as a designate for the user.
It is recommended that you use uniuser to modify only user attributes that are specific to the calendar server. Any attributes that can be modified using the Oracle Internet Directory administration tools directly should not be modified through uniuser.
The calendar server must be up to run uniuser.
unires is the complementary utility for resources.
<user>
Create a new calendar user. The information associated with the new user is a combination of what is specified in the <user> argument and the default values in the user.ini file. By default, when uniuser reads the user.ini file, it considers only the values in the [GEN] section. Use the -s option to apply values from other sections of the user.ini file. Use the -ex option to add multiple users.
When using the calendar server's internal directory, the "S" key is mandatory for the -add option.
For external directories, the user must already exist in the directory server. The DID (Directory ID) for the user must be specified, and it must be in DN (Distinguished Name) format. This can be followed by data in X.400 format. See EXAMPLES.
<user>
Delete the specified calendar user. uniuser prompts for confirmation before performing the deletion unless the -y option is used. If more than one user is to be deleted, the -ex option must used.
This operation can take a long time for users with very large agendas, and may have an impact on the performance of the calendar server for other users. It is recommended that you only delete users in off-peak hours.
<user>
Delete the list of designates for the specified user. If more than one user matches <user>, the command fails.
This option only exists under UNIX. It allows you to first output the list of existing calendar users to a file, then edit the file to make desired modifications, and finally to input the changes back into the node. The following sequence of commands is performed:
% uniuser -ls -n node-ID > file % vi file % uniuser -ex file -n node-ID % rm file
<filename>
Perform the additions, deletions, and/or modifications specified in the file <filename>. Each line of the file must begin with one of the characters `.', `#', `A', `a', `D', `d', `M', `m', `S', `s', or `+'. This initial character specifies the action to take, as follows:
The initial character must be followed by a space and a user specification. In the case of a modification, the ID must be specified; it alone is used to identify the user, while the other key-value pairs specified along with it are applied as the modifications. See EXAMPLES.
For each deletion specified in the file, uniuser prompts for confirmation before performing the deletion. The -y option is used to automatically provide confirmation.
One way to create this file is to save the output of uniuser -ls to a file. This can then be edited and input to uniuser -ex.
The -s sections option may be used with -ex to set the corresponding user information to the default values contained in the specified sections of the user.ini file.
For directory servers, the most common way of adding many calendar users is to first use unidssearch to output the list of all non-calendar users to a file. This file can then be modified (if necessary), and input to uniuser using the -ex option. unidssearch outputs in the same "key=value/key=value/...." format that uniuser requires for input. See EXAMPLES.
<format>
This option is used to select user information fields and to customize the format of the output. The -info option lists the parameters that can be used to specify the customized format. These are also listed in the FORMAT OF THE user ARGUMENT section below. If this option is not used, all user information fields are output, and a default presentation format is used. See EXAMPLES.
<user>
Delete the specified user from all admin groups. A single user must match <user> or the command fails.
<hostname>
Specifies a host on which to look for the node specified by the -n option. Required for remote hosts. If -host is not present, uniuser will assume the local host. For modification or deletion, if -host is specified and -n is not, uniuser will search for a master node on the specified host. If a master node is found, uniuser will use it to locate the selected users.
List the format parameters used with the -format option.
Used with the -ex option to force uniuser to continue processing all lines in the file even if it encounters an error. Errors are sent to standard error; file redirection may be used to capture these to a file.
[<user>]
If a user is specified, -ls lists that user (in the specified node). If no user is specified, all users in the node are listed. The -format option can be used with -ls to configure the presentation of the output (see EXAMPLES).
<modifier>
Specify a modification to be made to the user information of a particular user. The modifier is a string of the same form as the user argument with the following exceptions: the ID key may NOT be specified, and the PSW, PUBLISHEDTYPE and GLOBALREADONLY keys MAY be specified.
<user>
Modify the information associated with the specified user. This option is used with either the -s or the -m options. When used with the -s option, it sets the corresponding information for the user to the values contained in the specified sections of the user.ini file. When used with the -m option, modifications are made to the user's X.400 information.
<node-ID>
Specify a node. If -n is not used, uniuser will search for a master node located on the host specified by the -host option. If a master node is found, uniuser will use it to locate or distribute the specified users. If no master node exists, -n is required.
<sysOpPsw>
Provide the SYSOP password for the specified node. If this option is not used, prompting for the password occurs.
[<sections>]
Evaluate all or some of the contents of the user.ini file and output information from it to standard output.
Use this option without the <sections> argument to determine what sections exist in the user.ini file. The output in this case is a list of all section names along with their respective "Info" key-value pairs.
Use the <sections> argument to evaluate all of the key-value pairs in the specified sections. In this case all key-value pairs in the specified sections are output, along with any errors detected in these pairs. This is one way to validate the contents of the user.ini file. See the -add and -mod options for information on using -s <sections> to apply values from the user.ini file.
The <sections> argument is a list of one or more section names, each separated by a forward slash (e.g. "GEN/GR1/GR2" specifies the sections GEN, GR1 and GR2). Evaluation is done from left to right. Thus, in the above example, GEN is evaluated first, GR1 second, and GR2 last. Where the same key appears in more than one section, the value of the last instance evaluated takes precedence.
Used with the -del and -ex options to auto-confirm the deletion(s).
Print the current version number of uniuser.
Print a usage message explaining how to run uniuser.
The user argument is a string of the form "key=value/key=value/...", where "key" is one of those listed below, and "value" is any string. Both "key" and "value" are case insensitive. For all keys except the ID key, the "value" string may be terminated by a wild card symbol (*). If a forward slash "/" is to be included in a string, it should be escaped with the character "\" to prevent it from being interpreted as a key-value pair delimiter - i.e. "S=Hoopla/OU1=R\/D".
If, in a UNIX environment, a shell will be processing the string (e.g. the string is provided on the command line or is passed as an argument to the utility), the string should be enclosed in quotation marks. Furthermore, if characters meaningful to the shell are included in the string, they should be escaped (i.e. preceded by the escape character "\") to prevent the shell from interpreting them.
|
Note: If the ID key-value pair is specified in the user argument, all other key-value pairs specified along with it are ignored. |
The format parameters listed in the third column below are used with the -format option to configure the presentation of a listing (see EXAMPLES).
% uniuser -ls "s=W*" -n 23 Enter SysOp password: S=Whitman/G=Walt/ID=154/C=US S=Winterson/G=Jeannette/ID=114/C=England
% uniuser -ls "s=W*" -format "%s:%g" -n 23 Enter SysOp password: Whitman:Walt Winterson:Jeannette
% uniuser -format "%s:%g" -n 23 Enter SysOp password: Brossard:Nicole Dillard:Annie Jansson:Tove Kilpi:Eeva Kundera:Milan Lorde:Audre Morrison:Toni Sanchez:Sonia Whitman:Walt Winterson:Jeannette
% uniuser -add "S=Angelou/G=Maya" -n 24
% uniuser -add "DID=cn=Maya Angelou, o=Acme, c=US" -n 24
[GEN] section of the user.ini file (Milan Kundera exists in node 23). Look at the values in the GEN section of the user.ini file and ensure they are all valid:
% uniuser -s "GEN" -n 23 StartDay = 08h00 EndDay = 18h00 TimeInc = 30 ShowSunday = FALSE ShowSaturday = FALSE TimeFormat = 2 RefreshFrequency = 60 DefaultReminder = 0 TimeBeforeReminder = 10 MailNotification = TRUE OU1 = OU2 = OU3 = OU4 = O = C = A = P = TimeZone = ViewNormalEvent = TIME ViewPersonalEvent = TIME ViewConfidentialEvent = TIME ViewNormalTask = NO ViewPersonalTask = NO ViewConfidentialTask = NO CanBookMe = TRUE
% uniuser -mod "S=Kundera/G=Milan" -s "GEN" -n 23
% uniuser -mod "S=Kundera/G=Milan" -m "ou1=authors" -n 23
Multiple additions, deletions, and modifications are done using the -ex option. In this example, three new calendar users are added, one modified, and one deleted. A directory server is being used.
% unidssearch > multiple.dat % cat multiple.dat A DID=cn=Italo Calvino,o=Acme, c=US A DID=cn=Herman Hesse,o=Acme, c=US A DID=cn=Doris Lessing,o=Acme, c=US A DID=cn=Anja Kauranen,o=Acme, c=US
% vi multiple.dat % cat multiple.dat A DID=cn=Italo Calvino,o=Acme, c=US/C=Italy A DID=cn=Herman Hesse,o=Acme, c=US A DID=cn=Doris Lessing,o=Acme, c=US A DID=Anja Kauranen,o=Acme, c=US M G=Walter/ID=154 D G=Nicole/S=Brossard
In the case of the modification, the ID is used to find the user, and the given name is modified to "Walter".
uniuser:
% uniuser -ex multiple.dat 23 Enter SYSOP password: uniuser: added "cn=Italo Calvino,o=Acme, c=US" uniuser: added "cn=Herman Hesse,o=Acme, c=US" uniuser: added "cn=Doris Lessing,o=Acme, c=US" uniuser: added "cn=Anja Kauranen,o=Acme, c=US" uniuser: modified "Whitman,Walt" uniuser: deleted "Brossard,Nicole"
Note that if this example did not use a directory server, the input file would contain the following:
% cat multiple.dat A S=Calvino/G=Italo/C=Italy A S=Hesse/G=Herman A S=Lessing/G=Doris A S=Kauranen/G=Anja M G=Walter/ID=154 D G=Nicole/S=Brossard
/users/unison/misc/user.ini
This file specifies possible calendar user configurations. See also the calendar server Reference Manual, Appendix A, "User and Resource Parameters".
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
This utility uses the [UTL] adm_moduser<field> parameters in unison.ini to determine whether or not it can modify the corresponding key-value pairs for the user. For example, if adm_modusersurname were set to FALSE, then the value associated with the S key could be modified by this utility.
If no corresponding adm_moduser<field> for a particular key appears in the file, the utility assumes it CAN modify it.
It is important to understand the implications of the directory server configuration for calendar server utilities. In a supplier-consumer configuration, the scheduling of updates between the consumer and supplier may result in temporary differences between the two. This may mean that a calendar server utility is reading from a consumer directory server that has not yet been synchronized with its supplier.
Deleting users with a large numbers of meetings and events can take a long time and cause a decrease in performance for other calendar users. It is recommended that you delete such users outside of normal hours, or at least not at times of peak calendar usage.
unires is the complementary utility for resources.
universion - Verify the version of the calendar server.
universion [-all] [-nowarn] universion -v universion -h
universion displays the version number of the calendar server and checks all scripts and binaries to see if their versions are up to date.
universion runs whether the calendar server is up or down.
Display version number for each component of the calendar server.
Suppress warning messages.
Print the current version number of universion.
Print a usage message explaining how to run universion.
% universion
% universion -all
Exit values are:
0 Success
1 Failure
2 Usage error
3 Warning error
4 Severe error
5 Critical error
6 User interrupt
uniwhatos - Determine whether the calendar server package runs under the current operating system.
uniwhatos uniwhatos -v uniwhatos -h
uniwhatos determines whether the current operating system is the one under which the calendar server package is intended to run. If a discrepancy exists, uniwhatos outputs the operating system(s) the package runs under.
The calendar server installation procedure calls this utility to determine whether or not to proceed with the installation.
uniwhatos runs whether the calendar server is up or down.
Print the current version number of uniwhatos.
Print a usage message explaining how to run uniwhatos.
uniwhatos finding no discrepancy between the actual and expected operating systems:
% uniwhatos HP-UX 10.x
uniwhatos finding a discrepancy between the actual and expected operating systems:
% uniwhatos uniwhatos: package for wrong OS installed expect: HP-UX B.10.x actual: HP-UX B.9.01
Exit values are:
0 Success
1 Failure
2 Usage error
3 Warning error
4 Severe error
5 Critical error
6 User interrupt
uniwho - Display information on signed-on calendar users.
uniwho [-a] [-t] [-j] [-x] [-f] [-p <pattern>] uniwho -v uniwho -h
This utility allows the system manager to determine who is using the calendar server, where they are signed-on from, and the process-ID associated with their session. The options allow the display of various combinations of process-id, network address, node-ID, and user information.
This information is essential in certain situations. For example, when a user has done an abnormal shutdown of a client (say a powerdown while their client is active) the associated server process for that client continues to remain active for a fixed period of time. If the calendar server is configured (via the [ENG] max_userlogons parameter in unison.ini) to limit the number of sessions per user to 1, this user will not be able to log on again until their server process had terminated. uniwho allows the system manager to find the process-ID of the session and terminate it.
uniwho can only be run if the calendar server is up.
Display the alias associated with the default network address.
Display telephone, job-title and X.400-address when available.
Display job-title when available.
<pattern>
Display information for sessions which contain <pattern> in their information. For example, the pattern "128.192.64.96" would result in the display of session information for those logged on from this IP address. Matching is performed on all fields (network address/alias, telephone number, job-title, X.400 address), regardless of which of these may have been specified on the command line.
Display telephone number when available.
Display X.400 address when available.
Print the current version number of uniwho.
Print a usage message explaining how to run uniwho.
% uniwho -a PID ALIAS NODEID XITEMID USER 2120 ark.boat.com 12 12,2 CWSOP,na 24091 sail.boat.com 12 12,316 Barnes,Pat,B 24298 row.boat.com 12 12,311 Beck,Tom,V
% uniwho -p Quality PID ADDRESS NODEID XITEMID USER 24298 199.88.48.81 12 12,311 Beck,Tom,V
% uniwho -f PID ADDRESS NODEID XITEMID USER 2120 199.88.48.6 12 12,2 CWSOP,na 24091 199.88.48.81 12 12,316 Barnes,Pat,B Engineer/R&D /barnesp@acme.com /738-1000/123 24298 199.88.48.85 12 12,311 Beck,Tom,V Technician QualityAssurance/QA /tomb@acme.com /738-2000/015
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
uniwho starts a calendar server process. If activity logging has been enabled (via the [ENG] activity parameter in unison.ini), the start-up and shutdown of this process is logged.
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|