configure options
Hello, wouldn't it be useful to publish all configure options ( like modules options ) in WIKI ? I am trying to build debian packages for my machines with only those modules I need. And at the moment I don't have a clue how to deactivate the modules I don't need. Regards, E:S
"Seferovic Edvin" <edvin.seferovic@kolp.at> wrote:
wouldn't it be useful to publish all configure options ( like modules options ) in WIKI ?
Yes.
I am trying to build debian packages for my machines with only those modules I need. And at the moment I don't have a clue how to deactivate the modules I don't need.
Many modules don't even have "configure" scripts. The solution is to either delete the source directory (src/modules/rlm_foo), or to delete the resulting rlm_foo.so files. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
wouldn't it be useful to publish all configure options ( like modules options ) in WIKI ?
Yes.
I am trying to build debian packages for my machines with only those modules I need. And at the moment I don't have a clue how to deactivate the modules I don't need.
Many modules don't even have "configure" scripts. The solution is to either delete the source directory (src/modules/rlm_foo), or to delete the resulting rlm_foo.so files.
I wanted to deactivate mysql module ( rlm_sql ). But since I built debian package, I was able to install only the freeradius and freeradius-ldap which are needed for my setup. Something like this would be sure usefull if it were possible to enable/disable it in configure script. Thank you for your answer Alan ! Regards, E:S
On Sun 22 Oct 2006 04:43, Seferovic Edvin wrote:
Hello,
wouldn't it be useful to publish all configure options ( like modules options ) in WIKI ?
Yes. Thats a great idea. At present there is several hundred pages in the wiki, and most of them were put there by either myself or Keven (Hi Kevin :-) We would appreciate your help :-) Cheers -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc
Sure. How can I help? English is not my native language, but I don't see that as a problem. The only problem I see ( at the moment ) is that I am not familiar with all modules of freeradius and their configure options ( Alan notices that some of them don't even have configure options etc ). I have a few successfull freeradius installations behind myself and I wrote a similar patch Jonathan de Grave published at the mailing list recently ( mine has a hardcoded attribute ;) ). I would appreciate some feedback on the topic "how can I contribute to freeradius project". Regards, E:S -----Original Message----- From: Peter Nixon [mailto:listuser@peternixon.net] Sent: Montag, 23. Oktober 2006 09:52 To: edvin.seferovic@kolp.at; FreeRadius users mailing list Subject: Re: configure options On Sun 22 Oct 2006 04:43, Seferovic Edvin wrote:
Hello,
wouldn't it be useful to publish all configure options ( like modules options ) in WIKI ?
Yes. Thats a great idea. At present there is several hundred pages in the wiki, and most of them were put there by either myself or Keven (Hi Kevin :-) We would appreciate your help :-) Cheers -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc
Seferovic Edvin wrote:
Sure. How can I help? English is not my native language, but I don't see that as a problem. The only problem I see ( at the moment ) is that I am not familiar with all modules of freeradius and their configure options ( Alan notices that some of them don't even have configure options etc ).
I have a few successfull freeradius installations behind myself and I wrote a similar patch Jonathan de Grave published at the mailing list recently ( mine has a hardcoded attribute ;) ).
I would appreciate some feedback on the topic "how can I contribute to freeradius project".
Regards,
E:S
I would say the best place to start would be with what you know. You don't have to cover every single option in the first version of the wiki page, as long as you note that the list is not complete. Build the page up as your knowledge builds up. People will make corrections where they need to be made, if you're not sure of something, check it to the best of your ability, ask the list, etc. Other people will contribute their knowledge, too. -- James Wakefield, Unix Administrator, Information Technology Services Division Deakin University, Geelong, Victoria 3217 Australia. Phone: 03 5227 8690 International: +61 3 5227 8690 Fax: 03 5227 8866 International: +61 3 5227 8866 E-mail: james.wakefield@deakin.edu.au Website: http://www.deakin.edu.au
participants (4)
-
Alan DeKok -
James Wakefield -
Peter Nixon -
Seferovic Edvin