I'm trying to enable sql queries to a log file. I'm using freeradius 3.10 and the only thing I read I need to do is to uncomment the line "logfile = ${logdir}/sqllog.sql" on the file "/usr/local/etc/raddb/mods-enabled/sql", but it's not working. Is that OK? Thanks. -- *LUCAS DIAZ | DPTO. REDES* _______________________________________________________ Istilart 255 | Tel.: 02983 513040 C.P. B7500EGE | Tres Arroyos | Bs As | Argentina * *www.eternet.cc <http://www.eternet.cc/> | *ETERNET SISTEMAS *
On Jan 8, 2016, at 2:05 PM, Lucas Diaz <lucasdiaz@eternet.cc> wrote:
I'm trying to enable sql queries to a log file. I'm using freeradius 3.10 and the only thing I read I need to do is to uncomment the line "logfile = ${logdir}/sqllog.sql" on the file "/usr/local/etc/raddb/mods-enabled/sql", but it's not working. Is that OK?
I think that was fixed after 3.0.10 was released. Alan DeKok.
Ok, but is there another version after 3.0.10, stable at least? Or you're meaning 3.1.x branch? Thanks. *LUCAS DIAZ | DPTO. REDES* _______________________________________________________ Istilart 255 | Tel.: 02983 513040 C.P. B7500EGE | Tres Arroyos | Bs As | Argentina * *www.eternet.cc <http://www.eternet.cc/> | *ETERNET SISTEMAS * On 01/08/2016 04:58 PM, Alan DeKok wrote:
On Jan 8, 2016, at 2:05 PM, Lucas Diaz <lucasdiaz@eternet.cc> wrote:
I'm trying to enable sql queries to a log file. I'm using freeradius 3.10 and the only thing I read I need to do is to uncomment the line "logfile = ${logdir}/sqllog.sql" on the file "/usr/local/etc/raddb/mods-enabled/sql", but it's not working. Is that OK? I think that was fixed after 3.0.10 was released.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On Jan 11, 2016, at 7:36 AM, Lucas Diaz <lucasdiaz@eternet.cc> wrote:
Ok, but is there another version after 3.0.10, stable at least? Or you're meaning 3.1.x branch?
I mean the v3.0.x development branch. We don't release 3.0.10, and then 3.0.11 the next day. The code which will become 3.0.11 is in the v3.0.x development branch. This is how software development works. Alan DeKok.
Alan DeKok wrote:
On Jan 11, 2016, at 7:36 AM, Lucas Diaz <lucasdiaz@eternet.cc> wrote:
Ok, but is there another version after 3.0.10, stable at least? Or you're meaning 3.1.x branch?
I mean the v3.0.x development branch. We don't release 3.0.10, and then 3.0.11 the next day.
The code which will become 3.0.11 is in the v3.0.x development branch. This is how software development works.
Hmm, during the last months lurking here I noticed more and more postings recommending to get a fix from the v3.0.x development branch. Personally I consider it to be a bit error-prone and it also solves the issue just for a particular user asking for it. Other users will probably hit the same issue(s). How about a bit more of release-early-release-often? (E.g. I'm willing to update the openSUSE development package right after your 3.0.11 release.) Ciao, Michael.
Lucas, if you want latest bleeding edge packages from some application, common practice is nightly build based on your desired branch. But support will be challenging :). r. On 01/11/2016 03:09 PM, Michael Ströder wrote:
Alan DeKok wrote:
On Jan 11, 2016, at 7:36 AM, Lucas Diaz <lucasdiaz@eternet.cc> wrote:
Ok, but is there another version after 3.0.10, stable at least? Or you're meaning 3.1.x branch?
I mean the v3.0.x development branch. We don't release 3.0.10, and then 3.0.11 the next day.
The code which will become 3.0.11 is in the v3.0.x development branch. This is how software development works.
Hmm, during the last months lurking here I noticed more and more postings recommending to get a fix from the v3.0.x development branch. Personally I consider it to be a bit error-prone and it also solves the issue just for a particular user asking for it. Other users will probably hit the same issue(s).
How about a bit more of release-early-release-often? (E.g. I'm willing to update the openSUSE development package right after your 3.0.11 release.)
Ciao, Michael.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On Jan 11, 2016, at 9:09 AM, Michael Ströder <michael@stroeder.com> wrote:
Hmm, during the last months lurking here I noticed more and more postings recommending to get a fix from the v3.0.x development branch. Personally I consider it to be a bit error-prone and it also solves the issue just for a particular user asking for it. Other users will probably hit the same issue(s).
How about a bit more of release-early-release-often? (E.g. I'm willing to update the openSUSE development package right after your 3.0.11 release.)
We should release 3.0.11 this week. The only remaining issue I'm aware of is on Arran ran into. I'd also like to pull in Herwin's Python fixes. But that's really it, I think. Alan DeKok.
Hi, Just downloaded the 3.0.x dev branch and tried running fakeroot dpkg-buildpackage -b -uc from the unpacked source dir. Unfortunately I get .... dh_installdirs install -d debian/freeradius /usr/local/src/freeradius-server-3.0.x-110116/debian/freeradius.dirs: 1: /usr/local/src/freeradius-server-3.0.x-110116/debian/freeradius.dirs: usr/lib/freeradius: not found /usr/local/src/freeradius-server-3.0.x-110116/debian/freeradius.dirs: 2: /usr/local/src/freeradius-server-3.0.x-110116/debian/freeradius.dirs: var/log/freeradius: not found On 11 January 2016 at 14:16, Alan DeKok <aland@deployingradius.com> wrote:
On Jan 11, 2016, at 9:09 AM, Michael Ströder <michael@stroeder.com> wrote:
Hmm, during the last months lurking here I noticed more and more postings recommending to get a fix from the v3.0.x development branch. Personally I consider it to be a bit error-prone and it also solves the issue just for a particular user asking for it. Other users will probably hit the same issue(s).
How about a bit more of release-early-release-often? (E.g. I'm willing to update the openSUSE development package right after your 3.0.11 release.)
We should release 3.0.11 this week. The only remaining issue I'm aware of is on Arran ran into.
I'd also like to pull in Herwin's Python fixes. But that's really it, I think.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On Mon, Jan 11, 2016 at 02:55:07PM -0500, Alan DeKok wrote:
On Jan 11, 2016, at 9:58 AM, Alex Sharaz <alex.sharaz@york.ac.uk> wrote:
Hi, Just downloaded the 3.0.x dev branch and tried running
fakeroot dpkg-buildpackage -b -uc
Does:
$ make deb
work?
Works fine here with a clean 3.0.x (4acd54d3e22e11). But then, "fakeroot dpkg-buildpackage -b -uc" also does on a clean source tree. Matthew -- Matthew Newton, Ph.D. <mcn4@le.ac.uk> Systems Specialist, Infrastructure Services, I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom For IT help contact helpdesk extn. 2253, <ithelp@le.ac.uk>
Hi,
usr/lib/freeradius: not found Could this var/log/freeradius: not found And this have anything to do with it? ( Missing leading “/“ )
Regards, K
On 11 Jan 2016, at 14:58, Alex Sharaz <alex.sharaz@york.ac.uk> wrote:
Hi, Just downloaded the 3.0.x dev branch and tried running
fakeroot dpkg-buildpackage -b -uc
from the unpacked source dir. Unfortunately I get
.... dh_installdirs install -d debian/freeradius /usr/local/src/freeradius-server-3.0.x-110116/debian/freeradius.dirs: 1: /usr/local/src/freeradius-server-3.0.x-110116/debian/freeradius.dirs: usr/lib/freeradius: not found /usr/local/src/freeradius-server-3.0.x-110116/debian/freeradius.dirs: 2: /usr/local/src/freeradius-server-3.0.x-110116/debian/freeradius.dirs: var/log/freeradius: not found
On 11 January 2016 at 14:16, Alan DeKok <aland@deployingradius.com> wrote:
On Jan 11, 2016, at 9:09 AM, Michael Ströder <michael@stroeder.com> wrote:
Hmm, during the last months lurking here I noticed more and more postings recommending to get a fix from the v3.0.x development branch. Personally I consider it to be a bit error-prone and it also solves the issue just for a particular user asking for it. Other users will probably hit the same issue(s).
How about a bit more of release-early-release-often? (E.g. I'm willing to update the openSUSE development package right after your 3.0.11 release.)
We should release 3.0.11 this week. The only remaining issue I'm aware of is on Arran ran into.
I'd also like to pull in Herwin's Python fixes. But that's really it, I think.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On Jan 11, 2016, at 9:09 AM, Michael Ströder <michael@stroeder.com> wrote:
Alan DeKok wrote:
On Jan 11, 2016, at 7:36 AM, Lucas Diaz <lucasdiaz@eternet.cc> wrote:
Ok, but is there another version after 3.0.10, stable at least? Or you're meaning 3.1.x branch?
I mean the v3.0.x development branch. We don't release 3.0.10, and then 3.0.11 the next day.
The code which will become 3.0.11 is in the v3.0.x development branch. This is how software development works.
Hmm, during the last months lurking here I noticed more and more postings recommending to get a fix from the v3.0.x development branch. Personally I consider it to be a bit error-prone and it also solves the issue just for a particular user asking for it. Other users will probably hit the same issue(s).
How about a bit more of release-early-release-often? (E.g. I'm willing to update the openSUSE development package right after your 3.0.11 release.)
We could just do away with software versions entirely. If there is *ANY* difference in the number of known defects between your magic, tagged, blessed commits, and the commits that have been pushed to the main branch, you're doing software development wrong. The reason why will still have versions is largely psychological. People like to see a monotonically increasing number, it gives them a feeling of progress. They ignore the fact that running a version behind the current branch head, almost always ensures they're running software with known defects that have already been fixed. They ignore the fact that only testing *after* a version has been released, increases dramatically, the length of time defects are present in the code base and the effort required to track down defects. If you actually want to help the project, and not just be a passive consumer of the code we write, ignore the release tags entirely, setup a build script for v3.0.x, apply the latest build every Tuesday morning to a test server, and report any issues you find. Yes, it will require extra effort, you'll likely want your *own* logic tests to ensure your service functions correctly, but the end result will be a higher quality service for your users, and higher quality code in FreeRADIUS. -Arran Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS development team FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2
Hi,
How about a bit more of release-early-release-often?
for every single little thing? we'd be on 3.0.3423 or somesuch by now! ;-) granted there are supposed to be no feature changes in 3.0.x traibn - just bug fixes and security fixes but still things happen - not enough people test the HEAD to ensure things are all fine..but its there and accessible for use (unlike other software that hides and it given public release randomly). if there were too many releases there'd by more complaints (!) alan
Very good, I'll use that. Thanks. *LUCAS DIAZ | DPTO. REDES* _______________________________________________________ Istilart 255 | Tel.: 02983 513040 C.P. B7500EGE | Tres Arroyos | Bs As | Argentina * *www.eternet.cc <http://www.eternet.cc/> | *ETERNET SISTEMAS * On 01/11/2016 10:29 AM, Alan DeKok wrote:
On Jan 11, 2016, at 7:36 AM, Lucas Diaz <lucasdiaz@eternet.cc> wrote:
Ok, but is there another version after 3.0.10, stable at least? Or you're meaning 3.1.x branch? I mean the v3.0.x development branch. We don't release 3.0.10, and then 3.0.11 the next day.
The code which will become 3.0.11 is in the v3.0.x development branch. This is how software development works.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
participants (9)
-
A.L.M.Buxey＠lboro.ac.uk -
Alan DeKok -
Alex Sharaz -
Arran Cudbard-Bell -
Krzysztof Grobelak -
Lucas Diaz -
Matthew Newton -
Michael Ströder -
riki