Sponsored Content
Operating Systems AIX how to pre-determine if a reboot is required? Post 75209 by bakunin on Thursday 16th of June 2005 06:00:00 AM
Old 06-16-2005
Copy your fixes to a directory, then make this your current directory and issue an "inutoc .". A file called ".toc" will be created. For every package there is a multiline entry created, in the first line of this entry there is a single "b" or "B" if a bosboot is required.

You might want to search comp.unix.aix for "installp reboot" for this issue explained and check the AIX 5.2 (5.1) documentation for "installp" (rather lengthy) for the details of this.

You can try this by copying only one fix which you know to (not) require a reboot to a firectory and compare the various .toc-files generated by "inutoc".

Hope this helps.

bakunin
 

10 More Discussions You Might Find Interesting

1. Programming

pre defined variables

Hi First I want to explain the scenerio : In my project I want to control the printing of some messages. Thats why I use #ifdef MESSAGE ------------print message-------------- #endif And when I compile the program with -DMESSAGE option, it shows all message and without -DMESSAGE option... (7 Replies)
Discussion started by: sumsin
7 Replies

2. Solaris

different between soft reboot and hard reboot

Hi Guru's Can any want here could explain to me the different between soft reboot and hard reboot . Best Regards Seelan (3 Replies)
Discussion started by: seelan3
3 Replies

3. Solaris

Determine last reboot when wtmp broken

Hi - How can I determine the time my system was last booted when my "wtmp" file is broken? (It is being cleaned out incorrectly, I'mm working on that issue) ie uptime shows invalid details and who -b shows "nothing at all" is there a shutdown log somewhere that may indicat the last re-boot? (3 Replies)
Discussion started by: Andrek
3 Replies

4. Solaris

Pre-requsite for patches.......

Hi all....... I want to download some patches.......Is there any pre-requsite is taken before downloading a patch........... (1 Reply)
Discussion started by: sudhansu
1 Replies

5. Debian

How to determine if a package needs a reboot?

Hi, Anyone got a clue? is there some tool for it? couldnt find it in apt get, anyway i hope so cos i must build a patch management tool for work:P Greetz. (10 Replies)
Discussion started by: X-ion
10 Replies

6. AIX

Pre-checks

AIX Guys!!! What pre-checks would you do on a 5.3 server before TL/SP/APAR installation? Bala (2 Replies)
Discussion started by: balaji_prk
2 Replies

7. AIX

Pre Login Screen

Is it possible to have the user press enter to acknowledge a message before typing in his or her login name and password? I need to add this functionality to the CDE login, ssh, and ibm 3151 console on AIX 5.3. (0 Replies)
Discussion started by: prichard
0 Replies

8. Shell Programming and Scripting

Getting required fields from a test file in required fromat in unix

My data is something like shown below. date1 date2 aaa bbbb ccccc date3 date4 dddd eeeeeee ffffffffff ggggg hh I want the output like this date1date2 aaa eeeeee I serached in the forum but didn't find the exact matching solution. Please help. (7 Replies)
Discussion started by: rdhanek
7 Replies

9. Shell Programming and Scripting

how can i get the first day of the pre month

how can i get the first day of the pre month in Bash (3 Replies)
Discussion started by: qjlongs
3 Replies

10. Solaris

Reboot required on Server, Just confirm my settings.

Hi Guys, I need to reboot one Server as the newly inserted disk is not getting detected in system , I have also confirmed with Sun Support and finally it was the reboot which was required after doing all troubleshooting stuff. So I have disassembled the mirror and kept working disk's single... (3 Replies)
Discussion started by: manalisharmabe
3 Replies
doctools::toc::import::doctoc(n)				Documentation tools				  doctools::toc::import::doctoc(n)

__________________________________________________________________________________________________________________________________________________

NAME
doctools::toc::import::doctoc - doctoc import plugin SYNOPSIS
package require Tcl 8.4 package require doctools::toc::import::doctoc ?0.1? package require doctools::toc::parse package require doctools::toc::structure package require doctools::msgcat package require doctools::tcl::parse package require fileutil package require logger package require snit package require struct::list package require struct::set package require struct::stack package require struct::tree package require treeql import string configuration _________________________________________________________________ DESCRIPTION
This package implements the doctools table of contents import plugin for the parsing of doctoc markup. This is an internal package of doctools, for use by the higher level management packages handling tables of contents, especially doc- tools::toc::import, the import manager. Using it from a regular interpreter is possible, however only with contortions, and is not recommended. The proper way to use this func- tionality is through the package doctools::toc::import and the import manager objects it provides. API
The API provided by this package satisfies the specification of the doctoc import plugin API version 2. import string configuration This command takes the string and parses it as doctoc markup encoding a table of contents, in the context of the specified configu- ration (a dictionary). The result of the command is the canonical serialization of that table of contents, in the form specified in section ToC serialization format. [DOCTOC] NOTATION OF TABLES OF CONTENTS The doctoc format for tables of contents, also called the doctoc markup language, is too large to be covered in single section. The inter- ested reader should start with the document [1] doctoc language introduction and then proceed from there to the formal specifications, i.e. the documents [1] doctoc language syntax and [2] doctoc language command reference. to get a thorough understanding of the language. TOC SERIALIZATION FORMAT
Here we specify the format used by the doctools v2 packages to serialize tables of contents as immutable values for transport, comparison, etc. We distinguish between regular and canonical serializations. While a table of contents may have more than one regular serialization only exactly one of them will be canonical. regular serialization [1] The serialization of any table of contents is a nested Tcl dictionary. [2] This dictionary holds a single key, doctools::toc, and its value. This value holds the contents of the table of contents. [3] The contents of the table of contents are a Tcl dictionary holding the title of the table of contents, a label, and its ele- ments. The relevant keys and their values are title The value is a string containing the title of the table of contents. label The value is a string containing a label for the table of contents. items The value is a Tcl list holding the elements of the table, in the order they are to be shown. Each element is a Tcl list holding the type of the item, and its description, in this order. An alternative descrip- tion would be that it is a Tcl dictionary holding a single key, the item type, mapped to the item description. The two legal item types and their descriptions are reference This item describes a single entry in the table of contents, referencing a single document. To this end its value is a Tcl dictionary containing an id for the referenced document, a label, and a longer textual descrip- tion which can be associated with the entry. The relevant keys and their values are id The value is a string containing the id of the document associated with the entry. label The value is a string containing a label for this entry. This string also identifies the entry, and no two entries (references and divisions) in the containing list are allowed to have the same label. desc The value is a string containing a longer description for this entry. division This item describes a group of entries in the table of contents, inducing a hierarchy of entries. To this end its value is a Tcl dictionary containing a label for the group, an optional id to a document for the whole group, and the list of entries in the group. The relevant keys and their values are id The value is a string containing the id of the document associated with the whole group. This key is optional. label The value is a string containing a label for the group. This string also identifies the entry, and no two entries (references and divisions) in the containing list are allowed to have the same label. items The value is a Tcl list holding the elements of the group, in the order they are to be shown. This list has the same structure as the value for the keyword items used to describe the whole table of contents, see above. This closes the recusrive definition of the structure, with divisions holding the same type of elements as the whole table of contents, including other divisions. canonical serialization The canonical serialization of a table of contents has the format as specified in the previous item, and then additionally satisfies the constraints below, which make it unique among all the possible serializations of this table of contents. [1] The keys found in all the nested Tcl dictionaries are sorted in ascending dictionary order, as generated by Tcl's builtin command lsort -increasing -dict. BUGS, IDEAS, FEEDBACK This document, and the package it describes, will undoubtedly contain bugs and other problems. Please report such in the category doctools of the Tcllib SF Trackers [http://sourceforge.net/tracker/?group_id=12883]. Please also report any ideas for enhancements you may have for either package and/or documentation. KEYWORDS
deserialization, doctoc, doctools, import, table of contents, toc CATEGORY
Text formatter plugin COPYRIGHT
Copyright (c) 2009 Andreas Kupries <andreas_kupries@users.sourceforge.net> doctools2toc 0.1 doctools::toc::import::doctoc(n)
All times are GMT -4. The time now is 10:50 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy