Sponsored Content
Full Discussion: SSI or not??
Special Forums UNIX and Linux Applications High Performance Computing SSI or not?? Post 302677539 by navic on Thursday 26th of July 2012 09:00:56 AM
Old 07-26-2012
No input at all on this?
 

2 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

the unix answer to SSI?

On websites I build one thing I like to use is SSI to make it easier for the owner of the site to update parts of it him/herself. So the text of a page is keep in a simple .txt file, which the main page calls. Unix does not support this (I'm told), is there a similar system I can use with UNIX?... (1 Reply)
Discussion started by: garrettcarr
1 Replies

2. UNIX for Dummies Questions & Answers

SSI related Unix In (link) support needed

I have multiple web sites and have SSI all working fine! but I want a script that allows me to place a SSI script (or .html) on any web site within my server - One problem, SSI is limited to files located within the file structure - I want to access a file outside, (but still on my server) I found... (1 Reply)
Discussion started by: johnzule
1 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 04:21 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy