Sponsored Content
Operating Systems Solaris Cacaoadm - common agent container Post 302756989 by Joseph_TKLee on Thursday 17th of January 2013 12:36:55 AM
Old 01-17-2013
Reason is the process sometimes consumes 100% cpu usage.
Is it okay to restart during business hours?
 

10 More Discussions You Might Find Interesting

1. Solaris

LDOM vrs Container

Does anyone know the difference between a Logical Domain and a Container ? Both seem to be virtualisation technologies from Sun. Also I know a Domain can have containers within it but I don't see the point (4 Replies)
Discussion started by: jimthompson
4 Replies

2. Solaris

Solaris 8 Container Error

Log File: /var/tmp/server1.install.18730.log Source: /vmpool/tmp/server1.flar Installing: This may take several minutes... Postprocessing: This may take several minutes... Postprocess: ERROR: p2v module S40_setup_preload failed: 0 Postprocess: ERROR: Postprocessing failed. ... (0 Replies)
Discussion started by: cornsnap
0 Replies

3. Solaris

Solaris 6 container support

Is solaris 6 container support available ? Say, If I have a machine with Solaris 10 operating system.. Can i install Solaris 6 container on this machine, so that the machine will have Solaris 6 virtual environment... Does sun support Solaris 6 container ? Any ideas over this ? (1 Reply)
Discussion started by: shafi2all
1 Replies

4. Solaris

Swap issue on Container

Dear all, Kindly need your advice on swap issue on my container, SunOS 5.10. We have allocated swap 20GB and memory 8 GB. We have some application installed on the container. A few days ago we experienced a very slow system response...even for command like ls, df -k, etc.. I tried to... (8 Replies)
Discussion started by: sprout009
8 Replies

5. Solaris

Solaris 10 container graceful shutdown?

Hi, I've got a UPS connected to my Solaris 10 machine and I'm planning to run containers/zones on there. At the moment if the UPS agent sends the signal to the solaris machine to shutdown, all the apps shutdown gracefully and then the host goes down. If I setup containers for the apps, does... (9 Replies)
Discussion started by: fastexit
9 Replies

6. Solaris

solaris zones vs container..

kindly share what are difference b/w solaris zones and containers.... (8 Replies)
Discussion started by: Rajesh_Apple
8 Replies

7. UNIX for Advanced & Expert Users

mdadm container! How does it work

Hi everyone, I am not sure if I understand how mdadm --create /dev/md0 --level=container works? A device called /dev/md0 appears in /proc/mdstat but I am not sure how to use that device? I have 2 blank drives with 1 500GB partition on each. I would like to setup mirroring, but not in the... (0 Replies)
Discussion started by: hytron
0 Replies

8. Programming

how to check the value in stl container during debug

Hi, guys. I am working on a project right now. But when I debug my code, I can't see the values in stl container, e.g vector, map. Can anyone help me, please. I am really frustrated:wall:. I am using code::blocks IDE, by the way. Thanks in advance...... (0 Replies)
Discussion started by: tefino
0 Replies

9. Solaris

Container

Hi, Can any one let me know in detail what is container and how it is different from zones. and also any process to create a container (6 Replies)
Discussion started by: chetansingh23
6 Replies

10. Ubuntu

Ping a container LXC

Hello, Please, I try to do ping 10.0.3.8 (ip of LXC container) from VMB but it didn't work ! Have you an idea please ? Here is an explanation of what I want do: (red arrow) http://imgur.com/2IzJvXO imgur: the simple image sharer Thanks a lot. Best Regards. (0 Replies)
Discussion started by: chercheur111
0 Replies
supervisor_bridge(3erl) 				     Erlang Module Definition					   supervisor_bridge(3erl)

NAME
supervisor_bridge - Generic Supervisor Bridge Behaviour. DESCRIPTION
A behaviour module for implementing a supervisor_bridge, a process which connects a subsystem not designed according to the OTP design principles to a supervision tree. The supervisor_bridge sits between a supervisor and the subsystem. It behaves like a real supervisor to its own supervisor, but has a different interface than a real supervisor to the subsystem. Refer to OTP Design Principles for more informa- tion. A supervisor_bridge assumes the functions for starting and stopping the subsystem to be located in a callback module exporting a pre- defined set of functions. The sys module can be used for debugging a supervisor_bridge. Unless otherwise stated, all functions in this module will fail if the specified supervisor_bridge does not exist or if bad arguments are given. EXPORTS
start_link(Module, Args) -> Result start_link(SupBridgeName, Module, Args) -> Result Types SupBridgeName = {local,Name} | {global,Name} Name = atom() Module = atom() Args = term() Result = {ok,Pid} | ignore | {error,Error} Pid = pid() Error = {already_started,Pid} | term() Creates a supervisor_bridge process, linked to the calling process, which calls Module:init/1 to start the subsystem. To ensure a synchronized start-up procedure, this function does not return until Module:init/1 has returned. If SupBridgeName={local,Name} the supervisor_bridge is registered locally as Name using register/2 . If SupBridgeName={global,Name} the supervisor_bridge is registered globally as Name using global:register_name/2 . If no name is provided, the supervisor_bridge is not registered. If there already exists a process with the specified SupBridgeName the function returns {error,{already_started,Pid}} , where Pid is the pid of that process. Module is the name of the callback module. Args is an arbitrary term which is passed as the argument to Module:init/1 . If the supervisor_bridge and the subsystem are successfully started the function returns {ok,Pid} , where Pid is is the pid of the supervisor_bridge. If Module:init/1 returns ignore , this function returns ignore as well and the supervisor_bridge terminates with reason normal . If Module:init/1 fails or returns an error tuple or an incorrect value, this function returns {error,Term} where Term is a term with information about the error, and the supervisor_bridge terminates with reason Term . CALLBACK FUNCTIONS
The following functions should be exported from a supervisor_bridge callback module. EXPORTS
Module:init(Args) -> Result Types Args = term() Result = {ok,Pid,State} | ignore | {error,Error} Pid = pid() State = term() Error = term() Whenever a supervisor_bridge is started using supervisor_bridge:start_link/2,3 , this function is called by the new process to start the subsystem and initialize. Args is the Args argument provided to the start function. The function should return {ok,Pid,State} where Pid is the pid of the main process in the subsystem and State is any term. If later Pid terminates with a reason Reason , the supervisor bridge will terminate with reason Reason as well. If later the super- visor_bridge is stopped by its supervisor with reason Reason , it will call Module:terminate(Reason,State) to terminate. If something goes wrong during the initialization the function should return {error,Error} where Error is any term, or ignore . Module:terminate(Reason, State) Types Reason = shutdown | term() State = term() This function is called by the supervisor_bridge when it is about to terminate. It should be the opposite of Module:init/1 and stop the subsystem and do any necessary cleaning up. The return value is ignored. Reason is shutdown if the supervisor_bridge is terminated by its supervisor. If the supervisor_bridge terminates because a a linked process (apart from the main process of the subsystem) has terminated with reason Term , Reason will be Term . State is taken from the return value of Module:init/1 . SEE ALSO
supervisor(3erl) , sys(3erl) Ericsson AB stdlib 1.17.3 supervisor_bridge(3erl)
All times are GMT -4. The time now is 09:57 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy