attribute of type "datetime" sorted incorrectly, posted by Kees Bol on Wed Jul 27 16:46:44 2005 
|
In order to enter different logdates we created the attribute 'Logdate' as follows:
...
Attributes = Logdate, Author, Type, Subject
Type Logdate = datetime
Preset Logdate = $date
List Display = ID, Logdate, Author, Type, Subject
Start page = ?rsort=Logdate
Time format = "%d-%b-%y %H:%M"
Date format = %d-%b-%y
...
However some unexpected things happen:
1) when sorting on Logdate the sorting is incorrect
2) I expected some kind of fieldchecking when filling this field, however you can enter any text.
What goes wrong here?
Thanks |
Re: attribute of type "datetime" sorted incorrectly, posted by Kees Bol on Thu Jul 28 09:46:40 2005
|
| Stefan Ritt wrote: |
| Kees Bol wrote: | | What goes wrong here? |
The wrong sorting is a mystery to me. I redid what you have, and entered exactly the same entries, and got following:
As you can see, the sorting is quite different. What happens if you reload the page, what if you restart elogd?
As for the missing validity check for the date field, all what was missing was the year check. I added that. |
Stefan, I think it has something to do with version 2.57-1. Yesterday evening I installed V2.60 and there was a big difference. All entries of Logdate were changed in 1-jan-70 and when entering/editing an entry I now get the calendar and clock. So everything, including sorting, looks good now.
Thanks |
|
"full" only changes color, posted by Kees Bol on Mon Aug 1 11:58:43 2005
|
Hi,
I have the strange problem that when changing to "full"-diplaymode the output looks the same as with "summary", only the color is different. The texts don't appear.
Any idea what can cause this behaviour?
thanks
Kees Bol |
|
Re: "full" only changes color, posted by Kees Bol on Tue Aug 2 10:25:32 2005
|
| Stefan Ritt wrote: |
| Kees Bol wrote: | I have the strange problem that when changing to "full"-diplaymode the output looks the same as with "summary", only the color is different. The texts don't appear.
Any idea what can cause this behaviour? |
Can you send me your elogd.cfg ?
Have you made sure that the entries do contain some text? The behaviour you describe usually happens if you have entries without any text. |
Well, I guess that causes it. In the summary-view there is no visible text.
I thougt when choosing the full-view the text would appear along with the other attributes.
My config-file is:
================================================================
Theme = default
Attributes = Author, Type, Subject
Required Attributes = Type, Subject
Preset Author = $long_name
Locked Attributes = Author
Options Type = Question, Configuration, Problem, Info, Other
List Display = ID, Date, Author, Type, Subject
Thread display = $Subject, posted by $Author on $Date
Menu commands = Back, New, Edit, Delete, Reply, Find, Last 10, Change password, Logout, Help
Quick filter = Date, Type
Summary lines = 0
Start page = ?rsort=Date
; alleen eigen messages editen
Restrict edit = 1
====================================================================================== |
|
Re: "full" only changes color, posted by Kees Bol on Fri Aug 5 10:00:00 2005
|
| Stefan Ritt wrote: |
| Kees Bol wrote: | | I thougt when choosing the full-view the text would appear along with the other attributes. |
That's how it is supposed to be. I tried your config file, added three entries, and got the behaviour documented in the attached images. To me everything looks fine. |
Stefan, the output you see I expected to see with my logbook too but I don't.
I will upgrade to V2.6.0-beta3, perhaps that solves the problem. |
|
Re: "full" only changes color, posted by Kees Bol on Fri Aug 5 10:51:27 2005
|
| Stefan Ritt wrote: |
| Kees Bol wrote: | | I thougt when choosing the full-view the text would appear along with the other attributes. |
That's how it is supposed to be. I tried your config file, added three entries, and got the behaviour documented in the attached images. To me everything looks fine. |
Stefan, I installed V2.6.0-beta3 and there is a (unwanted) difference. The Text field now appears in the summary-view despite the config specifies:
List Display = ID, Logdate, Author, Book, Chapter, Type, Subject
so in my opinion the text-field should not show up here.
Now the full-view indeed shows the complete texts.
I also attached the complete config-file because perhaps I overlook some details.
Another point: there was some discussion about v2.6.0-beta3 being slow.
I have v2.6.0-beta and v2.6.0-beta3 running side by side on the same server and notice also a big difference in speed, beta3 being much slower. |
Re: "full" only changes color, posted by Kees Bol on Fri Aug 5 14:30:52 2005
|
| Stefan Ritt wrote: |
| Kees Bol wrote: | Stefan, I installed V2.6.0-beta3 and there is a (unwanted) difference. The Text field now appears in the summary-view despite the config specifies:
List Display = ID, Logdate, Author, Book, Chapter, Type, Subject
so in my opinion the text-field should not show up here. |
If you do not want text display in the summary view, add
Summary lines = 0
into your config file.
| Kees Bol wrote: | Another point: there was some discussion about v2.6.0-beta3 being slow.
I have v2.6.0-beta and v2.6.0-beta3 running side by side on the same server and notice also a big difference in speed, beta3 being much slower. |
This is still a mystery to me, since on all machines I try the speed is fine. I'm still waiting for some debugging analysis from users which have this problem. If I cannot reproduce it, I cannot fix it. |
After upgrading to v2.6.0-beta4 everything works fine now.
Thanks for your help |
|
Re: elogd dies after receiving second SIGHUP, posted by Paul T. Keener on Wed Jun 3 19:53:13 2009
|
> > elogd continues to run after a SIGHUP. If a second SIGHUP is received the daemon terminates.
> > This was observed on Solaris 10 (SPARC).
> > The documentation states that elogd should re-read configuration after receiving SIGHUP.
>
> I tried to reproduce this but without success. I could send many SIGHUPs without the daemon terminating. Maybe
> you modified the configuration file in between and elogd barked out because of some wrong configuration? Try to
> start the daemon interactively and see what exactly happens if you send several SIGHUPs.
The problem is that under Solaris signal handlers installed via signal() get uninstalled *before* the signal handler
is called. Thus the second time elogd receives a SIGHUP, you get the default action, which is to kill the process.
The solution is to use the POSIX sigaction() call instead of signal(). |
|