diff options
| author | Ryo Fujita <rfujita@redhat.com> | 2008-07-25 13:47:04 +0200 |
|---|---|---|
| committer | Rainer Gerhards <rgerhards@adiscon.com> | 2008-07-25 13:47:04 +0200 |
| commit | e39f202c75af187f96a1af07e60892a63e45cd3f (patch) | |
| tree | e2d45ded15960172161fe39aab3277d43aa16657 /module-template.h | |
| parent | 9b59581a6f7d161c7aafbc3300689337939bb382 (diff) | |
| download | rsyslog-e39f202c75af187f96a1af07e60892a63e45cd3f.tar.gz rsyslog-e39f202c75af187f96a1af07e60892a63e45cd3f.tar.bz2 rsyslog-e39f202c75af187f96a1af07e60892a63e45cd3f.zip | |
fixed a number of typos
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
Diffstat (limited to 'module-template.h')
| -rw-r--r-- | module-template.h | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/module-template.h b/module-template.h index d5e142b4..94fa1914 100644 --- a/module-template.h +++ b/module-template.h @@ -343,7 +343,7 @@ static rsRetVal queryEtryPt(uchar *name, rsRetVal (**pEtryPoint)())\ /* modInit() * This has an extra parameter, which is the specific name of the modInit * function. That is needed for built-in modules, which must have unique - * names in order to link statically. Please note that this is alwaysy only + * names in order to link statically. Please note that this is always only * the case with modInit() and NO other entry point. The reason is that only * modInit() is visible form a linker/loader point of view. All other entry * points are passed via rsyslog-internal query functions and are defined @@ -397,7 +397,7 @@ finalize_it:\ /* modExit() * This is the counterpart to modInit(). It destroys a module and makes it ready for * unloading. It is similiar to freeInstance() for the instance data. Please note that - * this entry point needs to free any module-globale data structures and registrations. + * this entry point needs to free any module-global data structures and registrations. * For example, the CfSysLineHandlers a module has registered need to be unregistered * here. This entry point is only called immediately before unloading of the module. So * it is likely to be destroyed. HOWEVER, the caller may decide to keep the module cached. |