On Tue, 30 Dec 2008, UUN Hostmaster wrote: > I get no output with this command: > > # strings /usr/sbin/dkim-filter | fgrep ar.c,v
That means your code wasn't compiled with the asynchronous resolver library provided as part of the dkim-milter package. This eliminates it as your problem. That means the operating system's stock resolver is doing what you've observed. dkim-filter (actually, libdkim) is just using the system's res_search() or res_query() function and thus doesn't have any direct influence about what UDP descriptors are created or how they're used. > What does the ",v" do in this command? Note this at the top of each .c and .h file in the distribution: #ifndef lint static char dkim_filter_c_id[] = "@(#)$Id: dkim-filter.c,v 1.416 2008/11/10 07:02:28 msk Exp $"; #endif /* !lint */ For files which actually comprise part of the binary, that string inside quotes will actually appear as part of the binary (and thus, the output of "strings"). This is how one can determine which files were used to build your executable. The entire string between the "$" characters is generated by our source code control system and is updated whenever one of the files is changed, so you can tell which version and what the revision date of each file was. The ",v" suffix is added to files in the revision control system "RCS" we use. For example, "foo.c" might be the working C source file but RCS keeps a history of all changes and comments describing them in "RCS/foo.c,v". This is used to generate the ID tag automatically. That there's no "ar.c,v" shows me that your binary did not include the code found in libar/ar.c, which is the asynchronous resolver library shipped with dkim-milter. That's the detail I was seeking. > Here is the output without the ",v" > > # strings /usr/sbin/dkim-filter | fgrep ar.c > dkim-ar.c That means your binary was compiled with dkim-filter/dkim-ar.c, which is expected; that code parses "Authentication-Results" header fields, and is different from libar/ar.c. ------------------------------------------------------------------------------ _______________________________________________ dkim-milter-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss
