Sponsored Content
The Lounge What is on Your Mind? Junior engineer attending a senior engineering interview. Post 303029595 by Circuits on Tuesday 29th of January 2019 11:03:09 AM
Old 01-29-2019
Thanks for the input guys I appreciate that.
 

2 More Discussions You Might Find Interesting

1. AIX

Junior SA Tasks?

I've been given more responsibility at work and was basically told to take junior system admin responsibilities over our aix box. The catch is, I need to learn on my own. I know basics, but what are some task that I could perform on a daily basis for starters? We have a support group, but not so... (2 Replies)
Discussion started by: NycUnxer
2 Replies

2. UNIX for Dummies Questions & Answers

Information on Network engineer and Unix Systems Engineer

Hi, I'm exploring a few different careers( Unix System's Admin, Network Engineer, and Unix System's Engineer). I asked in another thread about System's Admin, so I have some more info on that already. I'm not finding very much info on Network Engineers or Unix System Engineers though. Can you guys... (0 Replies)
Discussion started by: hpicracing
0 Replies
libgii.conf(5)								GGI							    libgii.conf(5)

NAME
libgii.conf - LibGII configuration file format DESCRIPTION
/etc/ggi/libgii.conf is the configuration file that defines what input module are available and where libgii is supposed to find them. It consists of lines defining target locations (mapping a target name a function name) and target aliases (fake targets that actually calls other target with a specific set of parameters). The format is common to all GGI libraries. It is defined by libgg. See ggLoadConfig(3) for additional information on file inclusions and other generic options. EXAMPLES
These examples show how to use the generic configuration mechanism proposed by LibGG with LibGII. The first example defines three input modules (or targets) for which initialization function is found in three different dynamic libraries (.so files), under the default LibGII input symbol: GIIdlinit: input-stdin input/stdin.so input-x input/x.so input-xwin input/xwin.so In the second example, the two inputs are implemented in a single dynamic library, but they each have their own initialization functions in this library. Their name is separated from the path by a :. input-x input/x.so:GIIdl_x input-xwin input/x.so:GIIdl_xwin The third example defines only one real target input-x, located in shared object input/x.so under the symbol GIIdl_x. input-xwin is an alias that will resolve to target input-x with the option string -be-xwin to be passed to the target function (GIIdl_x in input/x.so). input-x input/x.so:GIIdl_x alias input-xwin input-x:-be-xwin The last examples defines two inputs, with two possible location for their implementation. The first two lines are the same as in example 2. The other two states that these two inputs can also be found (if the previous fail) as a built-in modules. The /gii-builtins path points to the LibGII built-in symbol namespace. In this case both input would be found in this namespace under the default symbol GIIdlinit. The initialization function will be given the requested target name to know which implementation to use. input-x input/x.so:GIIdl_x input-xwin input/x.so:GIIdl_xwin input-x /gii-builtins input-xwin /gii-builtins SEE ALSO
ggLoadConfig(3) libgii-1.0.x 2006-12-30 libgii.conf(5)
All times are GMT -4. The time now is 05:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy