/etc/subsync parms definitions ?

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Pulling Parms from Config File

Hello all, I'm working on a general script for something at work. I'm an up-and-comer backup for a Shell Scripter this company has had for 35 years lol. Anyway, I have a config file I'm trying to pull Variables from as the Config File is used for multiple scripts. Does the below make sense and...

2. Programming

Where are the library function definitions located?

Hi friends, I hope everyone is doing fine. I have this confusion, hope you can help me out with it. The header files contain only function prototypes. Where are the function definitions located. For example, if I would like to see how printf works, where can I see its definition, stdio.h only...

3. Solaris

Does changing default password parms affect existing accounts in /etc/shadow?

Are the default password setting parameters (that are in /etc/login.defs) only used when a new local account is created on a server? It looks to me like a 'useradd userid1' command will look to the /etc/login.defs file to get default values for MINWEEKS MAXWEEKS and PASSLENGTH. If the parms are...

4. Shell Programming and Scripting

bashscript for learning definitions

Hi, I am a german lawstudent and have to learn a few hundred definitions and laws in the next months. I thought it would be cool to have a little helper, a bashscript which is working with flat textfiles. I found one in the archlinuxforum which was almost perfect...almost. It is on some point based...

5. UNIX for Dummies Questions & Answers

Definitions/explanations

Just wondering: Can anyone tell me what is meant by the term 'interactive shell" or 'built-in commands' - for example, if I type 'man set' I get a page listing all the 'built in commands' but no explanation of what they are as a concept or what they do. And while I'm here: I was wondering as...

6. UNIX for Dummies Questions & Answers

Shell and commandline interpreter-definitions

What is the difference between the(a) shell and the (a) command-line interpreter? Here we're talking about the complete dummy question, but could someone point me right. (yes, have written scripts in for instance bash shell, and and grepp-ed my way around ....:eek:

7. Shell Programming and Scripting

Missing alias definitions after involve another shell

I setup alias on my .bash_profile. It works very will until I did another sh on command prompt. I typed alias on new shell and all the definitions did not carry over. How to correct this? Thanks in advance.

8. Shell Programming and Scripting

function definitions file for bc

Hello, All :) ...I just figured out how to setup a function definitions file for bc...I was going to create lots more functions for it, but I'll bet that a huge file with tons of definitions has already been written...? Thanx in advance for any replies, Pudnik

9. UNIX for Advanced & Expert Users

SUN OS - UDP parms

Hi there, Does anyone know of a place that will give details for each of the following UDP parms? I've found documentation on there size limits but not what they will do or affect if changed. udp_xmit_hiwat udp_xmit_lowat udp_recv_hiwat udp_max_buf ...

10. Linux

Termcap Definitions

Hi. How do I enter and escape from graphics mode on RedHat Linux to capture escape sequences. I'm trying to edit the system termcap.

LEARN ABOUT OSF1

dlclose

dlclose(3)						     Library Functions Manual							dlclose(3)

NAME

       dlclose - Close a dlopen() object

SYNOPSIS

       #include <dlfcn.h>

       int dlclose(void *handle)

PARAMETERS

       A pointer to a global symbol object that is returned from a call to dlopen().

DESCRIPTION

       The dlclose function is used to inform the system that the object referenced by a handle returned from a previous dlopen() invocation is no
       longer needed by the application.

       The use of dlclose() reflects a statement of intent on the part of the process, but does not create any requirements on the dynamic library
       loader,	such as removal of the code or symbols referenced by handle. Once an object has been closed using dlclose(), an application should
       assume that its symbols are no longer available to dlsym(). All objects loaded automatically as a result of invoking dlopen() on the refer-
       enced object are also closed.

       The dlclose function deallocates the address space for the library corresponding to handle.  The results are undefined if any user function
       continues to call a symbol resolved in the address space of a library that has since been deallocated by dlclose.

       The dlclose operation will not remove an object to which references have been relocated, until or unless all such references  are  removed.
       For  instance,  an object that had been loaded with a dlopen() operation specifying the RTLD_GLOBAL flag might provide a target for dynamic
       relocations performed in the processing of other objects - in such environments, an application may assume that no relocation,  once  made,
       will be undone or remade unless the object requiring the relocation has itself been removed.

RETURN VALUE

       If  the referenced object was successfully closed, dlclose() returns 0. If the object could not be closed or if handle does not refer to an
       open object, dlclose() returns a non-zero value.  More detailed diagnostic information will be available through dlerror().

ERRORS

       No errors are defined.

NOTES

       The dlopen and dlclose routines might dynamically change the resolution of certain symbols referenced by a program or  its  shared  library
       dependencies.  The dlopen routine might resolve symbols that were previously unresolved, and dlclose might cause resolved symbols to become
       unresolved or to be reresolved to a different symbol definition.

       A portable application will employ a handle returned from a dlopen() invocation only within a given scope bracketed  by	the  dlopen()  and
       dlclose()  operations.	The  dynamic  library  loader  is  free  to use reference counting or other techniques such that multiple calls to
       dlopen() referencing the same object may return the same object for handle. The dynamic library loader is also free to re-use a handle. For
       these reasons, the value of a handle must be treated as an opaque object by the application, used only in calls to dlsym() and dlclose().

RELATED INFORMATION

       dlerror(3), dlopen(3), dlsym(3).  delim off

																	dlclose(3)

AIX