Re: [RADIATOR] Expiration Date Bug ?

2013-09-23 Thread Heikki Vatiainen
On 09/21/2013 12:23 AM, Kennyen Choo wrote: > Yes, convert the date format to 3 characters did help to resolve the > issue but why is Radiator try to perform the convertion if the date/time > format is incorrect? Good to hear it was solved. This needs to be fixed in Radiator so that invalid forma

Re: [RADIATOR] Expiration Date Bug ?

2013-09-20 Thread Heikki Vatiainen
On 09/20/2013 07:49 AM, Kennyen Choo wrote: > I'm using Expiration attribute with format "October 20 2013 00:00:00" > but suprisingly the Radiator converted it to "1358611200" instead of the > correct value which is "1382198400". Try converting the dates from full month name to three letter abbre

Re: [RADIATOR] Expiration Date Bug ?

2013-09-20 Thread Kennyen Choo
Thanks for your prompt response. Yes, convert the date format to 3 characters did help to resolve the issue but why is Radiator try to perform the convertion if the date/time format is incorrect? On Fri, Sep 20, 2013 at 12:49 PM, Kennyen Choo wrote: > Hello, > > I am using RADIATOR 4.10 on x86

RE: (RADIATOR) Expiration

2002-08-14 Thread Dave Kitabjian
sing it along to the database.   Let me know!   Dave :) -Original Message-From: Radius Admin [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 13, 2002 10:11 AMTo: Dave Kitabjian; [EMAIL PROTECTED]Subject: Re: (RADIATOR) Expiration Dave,   I am now using this:   AcctSQLSt

Re: (RADIATOR) Expiration

2002-08-13 Thread Radius Admin
To: Radius Admin ; [EMAIL PROTECTED] Sent: Tuesday, August 13, 2002 2:30 AM Subject: RE: (RADIATOR) Expiration There are a whole mess of date formatting options in the manual:       http://www.open.com.au/radiator/ref.html#pgfId=290952   Let me know how you make out!

RE: (RADIATOR) Expiration

2002-08-12 Thread Dave Kitabjian
Title: Message There are a whole mess of date formatting options in the manual:       http://www.open.com.au/radiator/ref.html#pgfId=290952   Let me know how you make out!   Dave   TABLE 2. DateFormat special characters Specifier Is replaced at run-time by:

Re: (RADIATOR) Expiration through shadow file

2001-02-26 Thread Hugh Irvine
Hello Richard - > > Just wondering whether anyone has successfully managed to get Radiator > using the shadow file's account expiry field as the Expiration check item > for Radiator? > The Expiration check item works with an explicit date as a check item. Have a look at section 13.1.4 in the R

Re: (RADIATOR) expiration date

2001-01-28 Thread Hugh Irvine
Hello Hakim - On Saturday 27 January 2001 20:25, Hakim Tass wrote: > hello everyone!!! > > I want to set the expiration by date. > > i.e when the user connects say on the 1st of the month he should be > disconnected on the 30th of the month. > Basically session-timeout by date. > I tried setting

RE: [platypus-users] Re: (RADIATOR) Expiration date passed!

1999-12-31 Thread admin
From: Granville Barker <[EMAIL PROTECTED]> To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Copies to: [EMAIL PROTECTED] Subject: RE: [platypus-users] Re: (RADIATOR) Expiration date passed! Date s

RE: [platypus-users] Re: (RADIATOR) Expiration date passed!

1999-12-30 Thread Granville Barker
After working with John, I determined that Radiator is using the MasterAccounts view as well as the SubAccounts view in some cases to authenticate users. Anyone running Radiator with Platypus may need the attached SQL Script to head off any Y2K issues. -- Granville Barker Platypus Support begi

Re: (RADIATOR) Expiration date passed!

1999-12-30 Thread John Vorstermans
Sorry for the repost. Not all the message went through the first time. Hi Hugh. Updating AuthRADIUS.pm made no diffderence. I ran the following select statement mSQL: select DateAdd(Day, ma.extension, maExpireDate), DateAdd(Day, sa.extension, saExpireDate), sa.AccountID, sa.AccountType, sa.pa

Re: (RADIATOR) Expiration date passed!

1999-12-30 Thread John Vorstermans
Hi Hugh. Updating AuthRADIUS.pm made no diffderence. I ran the following select statement mSQL: select DateAdd(Day, ma.extension, maExpireDate), DateAdd(Day, sa.extension, saExpireDate), sa.AccountID, sa.AccountType, sa.password, sa.login, sa.shell, sa.TimeLeft, sa.LoginLimit ,sa.LoginLimit fro

RE: (RADIATOR) Expiration date passed!

1999-12-30 Thread Platypus
John, Your subaccounts view will need to be recreated. Please look at the attached zip file. -- Granville Barker Platypus Support Hi Hugh. Updating AuthRADIUS.pm made no diffderence. I ran the following select statement mSQL: select DateAdd(Day, ma.extension, maExpireDate), DateAdd(Day, sa

Re: (RADIATOR) Expiration date passed!

1999-12-30 Thread Hugh Irvine
Hello John - On Fri, 31 Dec 1999, John Vorstermans wrote: > Hi. > > I have a strange problem that started happening as the clock rolled over to > Dec 31 1999. All my users started to get "Access rejected, Expiration date > passed " from my Radiator AuthEmerald which is talking to a mSQL data

Re: (RADIATOR) expiration not working?

1999-03-16 Thread Mike McCauley
On Mar 10, 12:59pm, C Thompson wrote: > Subject: (RADIATOR) expiration not working? > I tried setting an expiration on a user at the top of the 'users' file. > > I have my DEFAULT user at the end of the file. > > I have a default realm that looks in the 'users' file (AuthBy FILE) and a > dummy rea