Sponsored Content
Full Discussion: Anyone using GNU BSD?
Operating Systems BSD Anyone using GNU BSD? Post 302177192 by tcb3210 on Thursday 20th of March 2008 08:56:05 AM
Old 03-20-2008
I want to have a try

I want to have a try, but in fact I know litter about it
 

4 More Discussions You Might Find Interesting

1. BSD

for linux and BSD users interested in Unix system V/bsd

for all you unix/linux interested heres an online book for free that covers the basics of BSD SysV Unix commands and applications . giving the average linux user a perspective on the differences in context of the two operating systems and for BSD users covers material as a refernce guide. ... (0 Replies)
Discussion started by: moxxx68
0 Replies

2. UNIX for Dummies Questions & Answers

BSD equivalent of GNU parted

I use GNU (parted)set to change boot flags when doing multibooting. Alas, FreeBSD does not have GNU parted, out of the box. Is there a way to set/remove flags quickly and easily from the command line in BSD? I'm still learning all the 'unique' BSD utilities. (7 Replies)
Discussion started by: uiop44
7 Replies

3. Linux

Date from GNU to BSD

Dear all, This should be simple but I cannot figure it out despite reading all the man pages. Could someone please help me translate this code (GNU date) to one that can be read by BSD date?: myDate=$(date -d "$h -$l days" +%Y/%m/%d), where h is a variable of the form DD/MM/YYYY, and l is... (3 Replies)
Discussion started by: thomchad
3 Replies

4. Shell Programming and Scripting

GNU & BSD Makefile Directives & Conditions Compatibility

Firstly, I would like to apologize if this is not the appropriate sub-forum to post about GNU/BSD makefile scripting. Though my code is in C++, because I am focusing on the makefile I thought it would go better in shell scripting. Please correct me if I am wrong. Secondly, I am not interested in... (0 Replies)
Discussion started by: AntumDeluge
0 Replies
ARES_LIBRARY_CLEANUP(3) 				     Library Functions Manual					   ARES_LIBRARY_CLEANUP(3)

NAME
ares_library_cleanup - c-ares library deinitialization SYNOPSIS
#include <ares.h> void ares_library_cleanup(void) cc file.c -lcares DESCRIPTION
The ares_library_cleanup function uninitializes the c-ares library, freeing all resources previously acquired by ares_library_init(3) when the library was initialized. This function must be called when the program using c-ares will no longer need any c-ares function. Once the program has called ares_library_cleanup(3) it shall not make any further call to any c-ares function. This function does not cancel any pending c-ares lookups or requests previously done. Program must use ares_cancel(3) for this purpose. This function is not thread safe. You have to call it once the program is about to terminate, but this call must be done once the program has terminated every single thread that it could have initiated. This is required to avoid potential race conditions in library deinitial- ization, and also due to the fact that ares_library_cleanup(3) might call functions from other libraries that are thread unsafe, and could conflict with any other thread that is already using these other libraries. Win32/64 application DLLs shall not call ares_library_cleanup(3) from the DllMain function. Doing so will produce deadlocks and other prob- lems. AVAILABILITY
This function was first introduced in c-ares version 1.7.0 along with the definition of preprocessor symbol CARES_HAVE_ARES_LIBRARY_CLEANUP as an indication of the availability of this function. Since the introduction of this function, it is absolutely mandatory to call it for any Win32/64 program using c-ares. Non-Win32/64 systems can still use c-ares version 1.7.0 without calling ares_library_cleanup(3) due to the fact that currently it is nearly a do-nothing function on non-Win32/64 platforms. SEE ALSO
ares_library_init(3), ares_cancel(3) AUTHOR
Yang Tse Copyright 1998 by the Massachusetts Institute of Technology. Copyright (C) 2004-2009 by Daniel Stenberg. 19 May 2009 ARES_LIBRARY_CLEANUP(3)
All times are GMT -4. The time now is 12:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy