Hi,
We are in feature freeze for 3.0. The configuration format and behaviour for
3.0 will be stable between now and the final release (as it was with
release_3_0_0_rc0).
If you are planning on deploying 3.0 and have an existing 2.x.x configuration
you were planning to migrate when the
On 9 Sep 2013, at 08:44, Stefan Winter stefan.win...@restena.lu wrote:
Hi,
We are in feature freeze for 3.0. The configuration format and behaviour for
3.0 will be stable between now and the final release (as it was with
release_3_0_0_rc0).
If you are planning on deploying 3.0 and
Hi,
mv raddb raddb-noinst
mkdir raddb
touch raddb/all.mk
make install
do 'mkdir raddb/mods-config'
you've 'messed around' with the configuration directory which assumes
that mods-config exists... i guess that could be fixed to make dir
directory first if it doesnt exist.
alan
-
List
Hi,
mv raddb raddb-noinst
mkdir raddb
touch raddb/all.mk
make install
do 'mkdir raddb/mods-config'
you've 'messed around' with the configuration directory which assumes
that mods-config exists... i guess that could be fixed to make dir
directory first if it doesnt exist.
The idea
Hi,
Because that all.mk file for the rlm_perl module installs example perl
scripts in mod-config, the same with rlm_python and rlm_ruby.
I guess we'll have to come up with a proper fix.
Does the file need to be created by the rlm's make install? The
example scripts could be put into
On 09/09/13 14:04, Stefan Winter wrote:
Hi,
mv raddb raddb-noinst
mkdir raddb
touch raddb/all.mk
make install
do 'mkdir raddb/mods-config'
you've 'messed around' with the configuration directory which assumes
that mods-config exists... i guess that could be fixed to make dir
directory first
Stefan Winter wrote:
The idea is that make install is not supposed to touch my production
config in any way. I don't want it to generously add directories without
me knowing.
Honestly, the simplest might be to edit Make.inc, at the top where it
defines raddbdir and modconfdir:
ifeq
On 9 Sep 2013, at 14:24, Alan DeKok al...@deployingradius.com wrote:
Stefan Winter wrote:
The idea is that make install is not supposed to touch my production
config in any way. I don't want it to generously add directories without
me knowing.
There's also:
#!/bin/sh
make clean
if ! git
On Mon, Sep 09, 2013 at 03:18:06PM +0100, Arran Cudbard-Bell wrote:
This negates problems caused by installing over the top of a
previous installation, which IMHO is always an extremely bad
idea with any unpackaged software.
...or even packaged software.
FWIW, I put all freeradius config in
On 09/06/2013 04:31 PM, stefan.pae...@diamond.ac.uk wrote:
I shall try a RHEL6/CentOS6 compatible build tomorrow or Monday.
Shouldn't be a problem. John D, I'll update my tag, you guys will probably do
the same.
FYI: rc1 is packaged and built for Fedora in rawhide (unreleased
latest). At
I shall try a RHEL6/CentOS6 compatible build tomorrow or Monday.
Shouldn't be a problem. John D, I'll update my tag, you guys will probably do
the same.
Regards
Stefan
From: freeradius-users-bounces+stefan.paetow=diamond.ac...@lists.freeradius.org
11 matches
Mail list logo