This example shows how to set up an event which will be repeated for a minute
with interval of 2 seconds (will be triggered 30 times). After exceeding this
limit, the event loop will finish and all the memory resources will be freed.
-This is just example describing repeated activity, nothing usefull is done
+This is just example describing repeated activity, nothing useful is done
within foo function
@code
void *private_data)
{
- // Do something usefull
+ // Do something useful
printf("handling signal...\n");
exit(EXIT_SUCCESS);
tevent_queue_stop(fronta);
tevent_queue_start(fronta);
if (tevent_queue_running(fronta)) {
- printf ("Queue is runnning (length: %d)\n", tevent_queue_length(fronta));
+ printf ("Queue is running (length: %d)\n", tevent_queue_length(fronta));
} else {
- printf ("Queue is not runnning\n");
+ printf ("Queue is not running\n");
}
data = talloc(ev, struct juststruct);
# user-defined cascading style sheet that is included after the standard
# style sheets created by doxygen. Using this option one can overrule
# certain style aspects. This is preferred over using HTML_STYLESHEET
-# since it does not replace the standard style sheet and is therefor more
+# since it does not replace the standard style sheet and is therefore more
# robust against future updates. Doxygen will copy the style sheet file to
# the output directory.
* signal handlers have highest priority in tevent, so this signal
* handler will always be started before the other handlers
* below. Freeing the (wrapper) event context here tests that the
- * wrapper implementation correclty handles the wrapper ev going away
+ * wrapper implementation correctly handles the wrapper ev going away
* with pending events.
*/
talloc_free(ev);
}
/*
- create a event_context structure for a specific implemementation.
+ create a event_context structure for a specific implementation.
This must be the first events call, and all subsequent calls pass
this event_context as the first element. Event handlers also
receive this as their first argument.
*
* tevent_thread_call_depth_reset_from_req(struct tevent_req *req)
*
- * If the call depth is used for trace indentation, it might be usefull to
+ * If the call depth is used for trace indentation, it might be useful to
* reset the external variable to the call depth of currently processed tevent
* request, since the ext. variable can be changed after return from a function
* call that has created subrequests.
/**
* Activate call depth tracking and register external variable that will
- * be updated to the call epth of currenty processed tevent request.
+ * be updated to the call depth of currently processed tevent request.
*
* @param[in] ptr Address of external variable
*/
*
* The wrapper event context might undo something like impersonation.
*
- * This must be called after a succesful tevent_context_push_use().
+ * This must be called after a successful tevent_context_push_use().
* Any ordering violation results in calling
* the abort handler of the given tevent context.
*
* @defgroup tevent_compat The tevent compatibility functions
* @ingroup tevent
*
- * The following definitions are usueful only for compatibility with the
+ * The following definitions are useful only for compatibility with the
* implementation originally developed within the samba4 code and will be
* soon removed. Please NEVER use in new code.
*
*
* pp_im must be a pointer to an immediate event talloced on
* a context owned by the calling thread, or the NULL context.
- * Ownership of *pp_im will be transfered to the tevent library.
+ * Ownership of *pp_im will be transferred to the tevent library.
*
* pp_private can be null, or contents of *pp_private must be
* talloc'ed memory on a context owned by the calling thread
* or the NULL context. If non-null, ownership of *pp_private will
- * be transfered to the tevent library.
+ * be transferred to the tevent library.
*
* If you want to return a message, have the destination use the
* same function call to send back to the caller.