> Try putting those exact 2 lines in acct_users file instead. > That should make them work as intended. =)
ooohhhh you mean that little config file there hidden right at the start of the ls DOH!!! :-) Thanks to both you and Thor for that solution. The scripts seem to be triggering ok now, but am getting the following in radius.log... appears to be once for each time the script gets called... Tue Dec 28 16:14:12 2004 : Error: Thread 2 failed waiting for semaphore: Interrupted system call: Exiting However, I've found an old message in the archives from Thor which I believe addresses that particular issue. Cheers, >>>>> Mike <<<<< > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Nate M > Sent: Tuesday, December 28, 2004 2:20 PM > To: [email protected] > Subject: RE: Exec-Program > Importance: Low > > > - Nathan Miller > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > [mailto:freeradius- > > [EMAIL PROTECTED] On Behalf Of Mike Cisar > > Sent: Tuesday, December 28, 2004 12:49 PM > > To: [email protected] > > Subject: Exec-Program > > > > Another simple one (hopefully)... this server is running on > FreeRadius > > 0.9.0 (new server coming in 3 weeks will have newest version of > > FreeRadius, for now this version is what I have to work with). > > > > To summarize what I am trying to accomplish... > > - When an accounting start packet is received I need to pass that > > username and user's IP address to the "startscript" > > - When an accounting stop packet is received I need to pass that > > username and user's IP address to the "stopscript" > > > > With the goal of allowing the IP address (and user) access > to certain > > resources only when they are logged in (so I will have to pass that > > info to the script eventually... baby steps... get > freeradius to call > > the scripts first, then worry about perfecting them :-) ... > > > > for testing purposes, based on some vague examples I found whilst > > Googling, I have tried the following in the users file (below my > > outright deny access lines but above everything else of > substance in > > the file). Users are able to log on and off as normal, but the > > scripts don't seem to trigger (running with -xx I get no > errors, nor > > any reference to either script mentioned). > > > > DEFAULT Acct-Status-Type == "Start" > > Exec-Program = "/usr/local/bin/stopscript" > > DEFAULT Acct-Status-Type == "Stop" > > Exec-Program = "/usr/local/bin/startscript" > > > > The scripts are both owner/group to the radius user, have > read/execute > > permissions, and otherwise work when executed manually when su'd to > > the radius user. > > > > Is there something that needs to be configured in radiusd.conf in > > addition for this to work, perhaps some compile-time option? > > > > I get the impression that the above method may have been > superceded by > > doing such things via exec stanzas in radiusd.conf, but I > wasn't able > > to Google up any examples of that particular scenario that were a > > close enough fit to what I am trying to do. > > > > Any examples, pointers to docs, hints or other means to > that end, in > > whatever manner is currently accepted as being preferred > are appreciated. > > > > Thanks, > > >>>>> Mike <<<<< > > > > > > - > > List info/subscribe/unsubscribe? See > > http://www.freeradius.org/list/users.html > > > - > List info/subscribe/unsubscribe? See > http://www.freeradius.org/list/users.html > - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
