summaryrefslogtreecommitdiffstats
path: root/runtime
diff options
context:
space:
mode:
authorRainer Gerhards <rgerhards@adiscon.com>2008-07-25 13:52:08 +0200
committerRainer Gerhards <rgerhards@adiscon.com>2008-07-25 13:52:08 +0200
commit480125e16ce0cdd63d9ee0b47565789984c217e0 (patch)
treeb0adc873ac98cda42bf77f841bdba59aeec61fd0 /runtime
parent8ed5da5dc4c3b146e4636dd8b44fe62df4d90c80 (diff)
parentb829284f37add946ac810b125e3bededa1206c96 (diff)
downloadrsyslog-480125e16ce0cdd63d9ee0b47565789984c217e0.tar.gz
rsyslog-480125e16ce0cdd63d9ee0b47565789984c217e0.tar.xz
rsyslog-480125e16ce0cdd63d9ee0b47565789984c217e0.zip
Merge branch 'beta'
Diffstat (limited to 'runtime')
-rw-r--r--runtime/module-template.h4
1 files changed, 2 insertions, 2 deletions
diff --git a/runtime/module-template.h b/runtime/module-template.h
index 53f5543a..eb39b587 100644
--- a/runtime/module-template.h
+++ b/runtime/module-template.h
@@ -348,7 +348,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
@@ -402,7 +402,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.