|
|
|
cr_perror(3) -- print a libcrash error or warning message
|
|
cr_perror() prints to standard error an error or warning message corresponding to error, which should be the return value from an immediately previous call to one of the libcrash calls. The message describes the problem that occurred, explains its implications when appropriate, and gives corrective action where appropriate. If called with a zero error value, indicating success, cr_perror() prints ... |
|
cr_read(3) -- read from crash dump
|
|
The cr_read() function attempts to read the memory area defined by mem_page and num_pages into the buffer pointed to by buf from the crash dump opened using crash_cb. The cr_read() starts at the position in the crash dump associated with the physical memory offset given by mem_page. If the physical memory page mem_page does not exist in the crash dump, cr_read() sets *num_pages to 0 and returns 0.... |
|
|
cr_set_node(3) -- set node number
|
|
The cr_set_node() function expects the physical node number passed in node_num. The node number will be used by cr_read() and cr_isaddr() to access the node private memory contained on a particular node. This function is only valid for ccnumadir (version 4) dumps. If the old_node_num argument is non-NULL, the address referenced by old_node_num will be set to the previous node number. If old_node_n... |
|
cr_uncompress(3) -- uncompress a file in a crash dump
|
|
The cr_uncompress() ensures that a file, part of a crash dump described by crash_cb, is uncompressed and matches its expected size and checksum (as computed by cksum(1)). This call is most often used to ensure the integrity of module files that are a part of the crash dump; see cr_info(3). pathname is the name of the file to uncompress. Supported compression methods include gzip(1), which appends ... |
|
cr_verify(3) -- verify integrity of crash dump
|
|
cr_verify() uncompresses and verifies the sizes and checksums of every file in the crash dump identified by crash_cb. flags is a bitmask of zero or more of the following flag values: CR_NOCHECKSUM cr_verify() will not attempt to verify checksums of files in the crash dump if this flag is set. Only sizes will be verified. CR_DELAYMSGS cr_verify() will write messages to stderr during time-consuming ... |
|
csa_add_calendar(3) -- add a calendar to the calendar service
|
|
The csa_add_calendar function creates a calendar on the calendar service. If the user does not have sufficient authority to add a calendar to the service, the error CSA_E_NO_AUTHORITY is returned. If the calendar already exists the error CSA_E_CALENDAR_EXISTS is returned. |
|
csa_add_entry(3) -- add an entry to the specified calendar
|
|
The csa_add_entry function adds a new entry to a calendar. The handle for the new entry is returned. Only the owner of the calendar, users with CSA_OWNER_RIGHTS, users with CSA_INSERT_PUBLIC_ENTRIES, user with CSA_INSERT_CONFIDENTIAL_ENTRIES, or users with CSA_INSERT_PRIVATE_ENTRIES access rights can add entries to the calendar. |
|
csa_call_callbacks(3) -- force the invocation of the callback functions associated with the specified callback list(s)
|
|
The csa_call_callbacks function causes the service to call the registered callback functions associationed with the specified callback list(s). The service will process each specified callback list and call the registered callback functions if there have been changes that would trigger the callbacks of that type. The order in which callbacks are invoked is implementation specific. |
|
csa_delete_calendar(3) -- delete a calendar from the calendar service
|
|
The csa_delete_calendar function deletes a calendar on the calendar service. Only the owner of the calendar, or a user with the owner authority, can remove the calendar from the calendar service. |
|
csa_delete_entry(3) -- delete an entry from a calendar
|
|
The csa_delete_entry function will delete an entry in a calendar. The delete_scope indicates the scope of the deletion if the entry has any associated recurring entries. All of the recurring entries can be deleted, only the specified entry can be deleted, or only the recurring entries that follow the specified entry can be deleted. Only the calendar owner, users with CSA_OWNER_RIGHTS, users with C... |
|
csa_free(3) -- free memory allocated by the calendaring service
|
|
The csa_free function frees memory allocated by the calendaring service. After the call, the pointer memory will be invalid and should not be referenced again. When any CSA function allocates and returns a buffer to the application, the application will free that memory with this call when it is finished with the memory. When a CSA function returns a base pointer to a complex structure containing ... |
|
csa_free_time_search(3) -- searches one or more calendars for available free time
|
|
The csa_free_time_search function searches for available free time on one or more calendars and returns a list of free time intervals found. Free time is an interval of time that is not currently scheduled on one or more calendars. The free time search is based on a date and time range and the minimum time duration required of the free time interval. Only the owner of the calendar, users with CSA_... |
|
csa_list_calendars(3) -- list the calendars supported by a calendar service
|
|
The csa_list_calendars function lists all the calendars supported by the specified calendar service. The names of the calendars supported are returned in calendar_names, which is an array of CSA_calendar_users structures with number_names elements. It is implementation specific what authority a calendar user needs to invoke this function. |
|
csa_list_calendar_attributes(3) -- list the names of the calendar attributes associated with a calendar
|
|
The csa_list_calendar_attributes function lists the names of the calendar attributes associated with a calendar. Using the returned calendar attribute name(s), the attribute value(s) may be read using the csa_read_calendar_attributes(3) function. Only the owner of the calendar, users with CSA_OWNER_RIGHTS, or users with CSA_VIEW_CALENDAR_ATTRIBUTES access rights can list the calendar attributes. |
|
csa_list_entries(3) -- list the calendar entries that match all the attribute search criteria
|
|
The csa_list_entries function lists the entry handles for the calendar entries that match all the attribute search criteria. Using the returned entry handles, the entries can have their attributes listed and read, or the entries can updated or deleted. Only the calendar owner, users with CSA_OWNER_RIGHTS, users with CSA_VIEW_PUBLIC_ENTRIES, user with CSA_VIEW_CONFIDENTIAL_ENTRIES, or users with CS... |
