Re: bug in cfg file, posted by Stefan Ritt on Wed Jun 4 15:26:15 2003
|
> When you take the elogd.cfg file and the menu commands = <list> and guest
> menu commands = <list>, the config menu for edit the elogd.cfg stops
> working, yet if I change the URL manually, I can still get to the file and
|
Bug Found, posted by nickc1 on Mon Jun 16 17:44:49 2003
|
Ive just been alerted to a bug with email notifications in Elog.
Basically if your log book contains a space then the URL that is sent in
|
|
Re: Bug Found, posted by Stefan Ritt on Tue Jun 17 12:52:34 2003
|
> Correct Way prior to 2.3.8
>
> http://192.168.0.1:99/Provisioning%20Request/35
|
|
Re: Bug Found, posted by nickc1 on Fri Jun 20 10:40:43 2003
|
> > Correct Way prior to 2.3.8
> >
> > http://192.168.0.1:99/Provisioning%20Request/35
|
|
Re: Bug Found, posted by Stefan Ritt on Mon Jun 23 10:53:55 2003
|
> Im using the plain RPM from 2.3.8, i uninstalled the 2.3.7 RPM before this
> upgrade, the only thing I kept was my own stylesheets and the config file.
>
|
runtime error under Mac OS X 10.2, posted by Joseph Giaime on Mon Jun 30 00:11:09 2003
|
I have been trying to build and run elog under Mac OS X 10.2.6, without sucess. I
understand that this is not one of the 'supported' platforms, but I hope that there is someone
here who might know the work-around to my problem.
|
|
Re: runtime error under Mac OS X 10.2, posted by Sridhar Anandakrishnan on Mon Jun 30 02:12:24 2003
|
Joe,
Run the command
|
|
Re: runtime error under Mac OS X 10.2, posted by Recai Oktas on Mon Jun 30 02:41:33 2003
|
Seems a stack problem. I don't have an OS X box to validate my guess. I've
made a Google search with the keywords: EXC_BAD_ACCESS stack "os x"
|