Sponsored Content
Full Discussion: Rolling Back an Update
Operating Systems Linux Rolling Back an Update Post 302637295 by Brandon9000 on Tuesday 8th of May 2012 04:45:45 PM
Old 05-08-2012
The product exists. I am adding a new feature to the Linux version of the product. I am doing a Linux version of patch management. I had been trying to figure out rollbacks and thought somebody could offer advice.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Rolling back time

Hi all, Have a small problem. Back in October the pervious sys-admin (of a client's company) made the necessary adjustments to the system clock for daylight savings (Sydney time - +11 GMT). As far as I can gather, they just amended the time - NO TIMEZONE !?! Is there an effective and safe... (5 Replies)
Discussion started by: Cameron
5 Replies

2. AIX

back to back printing in UNIX

Hi , Can you suggest me how to back to back printing in UNIX? Is there any way? Kindly advise. Regards Vijaya Amirtha Raj (3 Replies)
Discussion started by: amirthraj_12
3 Replies

3. Shell Programming and Scripting

log rolling

Hi, I'm thinking of running a script via cron (every hour) to do the log rolling. The file is "file.txt" and there going to be 10 files rolling (file.txt.n). The file is being written constantly by an application. The script will do the following: 1. cat file.txt > file.txt.0 2. cat... (0 Replies)
Discussion started by: chaandana
0 Replies

4. IP Networking

Back-to-Back Connection using HBAs

Hi every body, Is it possible to connect two servers Back-to-Back (Point-to-Point) using HBA adapters & using Fiber. Note it is direct connection & there is no switches between the servers. I'm concern about using HBA adapters, it is possible or not. Thanks in advance. :) (3 Replies)
Discussion started by: aldowsary
3 Replies

5. AIX

rolling back Technology Level

Hi, is it possible to roll back currently updated Technology level ? what are steps required? Regards, Manoj (2 Replies)
Discussion started by: manoj.solaris
2 Replies

6. UNIX for Dummies Questions & Answers

Rolling back SQL transaction

Can some one help me related to .sql file issue. I have a .sqlfile and tried to read the file thru unix. In the .sqlfile I have error rows as well and when error comes I dont want to proceed further and need to roll back all the transactions. sample .sql file below insert into test... (2 Replies)
Discussion started by: sri_aue
2 Replies

7. UNIX for Dummies Questions & Answers

Middled Rolling average

Dear Help, The input file is below --- 13 2238422.00000 101083.00000 0.89024 0.00416 0.00467 14 2238318.00000 101090.00000 0.89100 0.00416 0.00467 15 2238209.00000 101100.00000 0.90964 0.00424 0.00466 16 2238104.00000 101104.00000 0.97568 0.00463 0.00475 17 2237991.00000 101113.00000... (8 Replies)
Discussion started by: Indra2011
8 Replies

8. What is on Your Mind?

SEO Update: Back On Page 1 for Google SERPs (between #6 and #8)

Well, good news... Just checked a number of browsers set to the US region of Google , NCR https://www.google.com/ncr unix.com was back on the first page, between #6 and #8. Will be interesting to see if we can make it back to our highest #4 ranking in 2019. Google Webmaster Tools... (4 Replies)
Discussion started by: Neo
4 Replies
wsreg_unregister(3WSREG)			    Product Install Registry Library Functions				  wsreg_unregister(3WSREG)

NAME
wsreg_unregister - remove a component from the product install registry SYNOPSIS
cc [flag ...] file ...-lwsreg [library ...] #include <wsreg.h> int wsreg_unregister(const Wsreg_component *comp); DESCRIPTION
The wsreg_unregister() function removes the component specified by comp from the product install registry. The component will only be removed if the comp argument has a matching uuid, instance, and version. Usually, the component retrieved through a call to wsreg_get(3WSREG) before being passed to the wsreg_unregister() function. If the component has required components, the respective dependent components will be updated to reflect the change. A component that has dependent components cannot be unregistered until the dependent components are uninstalled and unregistered. RETURN VALUES
Upon successful completion, a non-zero return value is returned. If the component could not be unregistered, 0 is returned. EXAMPLES
Example 1: Unregister a component. The following example demonstrates how to unregister a component. #include <stdio.h> #include <wsreg.h> int main(int argc, char **argv) { char *uuid = "d6cf2869-1dd1-11b2-9fcb-080020b69971"; char *location = "/usr/local/example1_component"; Wsreg_query *query = NULL; Wsreg_component *comp = NULL; /* Initialize the registry */ wsreg_initialize(WSREG_INIT_NORMAL, NULL); /* Query for the component */ query = wsreg_query_create(); wsreg_query_set_id(query, uuid); wsreg_query_set_location(query, location); comp = wsreg_get(query); if (comp != NULL) { /* The query succeeded. The component has been found. */ Wsreg_component **dependent_comps; dependent_comps = wsreg_get_dependent_components(comp); if (dependent_comps != NULL) { /* * The component has dependent components. The * component cannot be unregistered. */ wsreg_free_component_array(dependent_comps); printf("The component cannot be uninstalled because " "it has dependent components "); } else { /* * The component does not have dependent components. * It can be unregistered. */ if (wsreg_unregister(comp) != 0) { printf("wsreg_unregister succeeded "); } else { printf("unregister failed "); } } /* Be sure to free the component */ wsreg_free_component(comp); } else { /* The component is not currently registered. */ printf("The component was not found in the registry "); } wsreg_query_free(query); } USAGE
Components should be unregistered before uninstallation. If the component cannot be unregistered, uninstallation should not be performed. A component cannot be unregistered if other registered components require it. A call to wsreg_get_dependent_components() can be used to determine if this situation exists. See wsreg_add_dependent_component(3WSREG). A successful unregistration of a component will result in all components required by the unregistered component being updated in the prod- uct install registry to remove the dependency. Also, child components will be updated so the unregistered component is no longer regis- tered as their parent. When unregistering a product, the product should first be unregistered, followed by the unregistration of its first feature and then the unregistration and uninstallation of the components that comprise that feature. Be sure to use this top-down approach to avoid removing a component that belongs to a product or feature that is required by a separate product. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |MT-Level |Unsafe | +-----------------------------+-----------------------------+ SEE ALSO
wsreg_add_dependent_component(3WSREG), wsreg_get(3WSREG), wsreg_initialize(3WSREG), wsreg_register(3WSREG), attributes(5) SunOS 5.10 22 Sep 2000 wsreg_unregister(3WSREG)
All times are GMT -4. The time now is 04:53 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy