Re: UNC Pfade, posted by Michael on Thu Oct 20 07:53:31 2022
|
So there is no way to save the file on the network?! :(
Can i install the elog on a windows server? i tried it yesterday, but i think i missed something, couse i only could open the elog on the server and not with a client pc.
| Stefan Ritt wrote: |
|
UNCs are not officially supported by elog, but your operating system might map them if you're lucky, just try. It is however not recommended to do so, since network drives can sometimes be slow during network congestion and the response of elog will then suffer.
Stefan
| Michael wrote: |
|
Hallo,
gibt es eine Möglichkeit das subdir auf ein Netzlaufwerk zu legen?
\\server\freigabe\...
Der Freigabepfad wird leider immer unter C:\... angelegt
Vielen Dank
|
|
|
|
Re: UNC Pfade, posted by Antonio Bulgheroni on Thu Oct 20 08:37:23 2022
|
I'm running ELOG on a windows server 2016. Just installed the windows installer and worked out of the box.
Have you checked the firewall?
| Michael wrote: |
|
So there is no way to save the file on the network?! :(
Can i install the elog on a windows server? i tried it yesterday, but i think i missed something, couse i only could open the elog on the server and not with a client pc.
| Stefan Ritt wrote: |
|
UNCs are not officially supported by elog, but your operating system might map them if you're lucky, just try. It is however not recommended to do so, since network drives can sometimes be slow during network congestion and the response of elog will then suffer.
Stefan
| Michael wrote: |
|
Hallo,
gibt es eine Möglichkeit das subdir auf ein Netzlaufwerk zu legen?
\\server\freigabe\...
Der Freigabepfad wird leider immer unter C:\... angelegt
Vielen Dank
|
|
|
|
Re: Type date and conditional attributes, posted by Stefan Ritt on Sat Mar 6 12:47:34 2004 
|
> BUG#1
Has been fixed. New version under CVS.
> BUG#2
> In single entry view, elog returns an unformatted date value for "Type =
> date" attributes - even when it has been manually entered with the date picker.
Can't reproduce that. Used your config, got the display attached. |
|
Re: Type date and conditional attributes, posted by Ralph Bearpark on Mon Mar 8 09:52:14 2004
|
> > BUG#1
>
> Has been fixed. New version under CVS.
Thanks for that, Stefan.
> > BUG#2
> > In single entry view, elog returns an unformatted date value for "Type =
> > date" attributes - even when it has been manually entered with the date picker.
>
> Can't reproduce that. Used your config, got the display attached.
Nor can I in the new version. Forgive me if I don't investigate further. ;-) |
|
Re: Type <attribute> = Date - Issue, posted by David Pilgram on Fri Sep 7 19:08:27 2012
|
| Garret Delaronde wrote: |
|
I haven't found anything in the forums about this. Apologies if its a duplicate.
I am fairly familiar with ELog, use it for multiple purposes on 5 different Virtual Servers at work.
Currently looking to do some updates to one of the instances with the Date Type setting.
We have 17,000 entries all which have had manual entries for a Date Attribute for the last year and 8 months.
Due to regular entry errors on part of our contractors using it, (Eg: using "Aug" instead of "08", or using "-" instead of "/"), I want to change over to using the date type attribute (Type <attribute> = Date).
However the problem i found, the moment i save this in the config, and go to the list of entries, the date has changed on all of the entries to 12/31/1969. Which is BAD for our operation. So after removing the Type Date Setting the dates go back to normal.
Is there anyway to retain those dates so they display as they are and then only new entries would fall under the new date type setting?
Syntax manual didn't help much for this issue.
|
Hi Garret,
Why cannot you just use $entry time ? It uses the date that the entry was made which appears as the first line of every elog entry -
[Sorry for mis-post, just discovered cannot put the 'dollar at' control set in an entry]
MID: 12458
Date: Fri, 07 Sep 2012 17:22:06 +0100
In reply to: 12453
You can use 'Time format = ' to get the date to display in the format you like. You will see I have posted an issue about 'Date format = '. I mention this because in trying to understand what was happening, I too had a case where all the dates were showing as the same in a thread. I suspect your 12/31/1969 was due to the entries as being read were non-existant or blank.
Of course I may have mis-understood your requirements.
|
|
Re: Type <attribute> = Date - Issue, posted by Garret Delaronde on Mon Sep 10 17:18:03 2012
|
| David Pilgram wrote: |
|
| Garret Delaronde wrote: |
|
I haven't found anything in the forums about this. Apologies if its a duplicate.
I am fairly familiar with ELog, use it for multiple purposes on 5 different Virtual Servers at work.
Currently looking to do some updates to one of the instances with the Date Type setting.
We have 17,000 entries all which have had manual entries for a Date Attribute for the last year and 8 months.
Due to regular entry errors on part of our contractors using it, (Eg: using "Aug" instead of "08", or using "-" instead of "/"), I want to change over to using the date type attribute (Type <attribute> = Date).
However the problem i found, the moment i save this in the config, and go to the list of entries, the date has changed on all of the entries to 12/31/1969. Which is BAD for our operation. So after removing the Type Date Setting the dates go back to normal.
Is there anyway to retain those dates so they display as they are and then only new entries would fall under the new date type setting?
Syntax manual didn't help much for this issue.
|
Hi Garret,
Why cannot you just use $entry time ? It uses the date that the entry was made which appears as the first line of every elog entry -
[Sorry for mis-post, just discovered cannot put the 'dollar at' control set in an entry]
MID: 12458
Date: Fri, 07 Sep 2012 17:22:06 +0100
In reply to: 12453
You can use 'Time format = ' to get the date to display in the format you like. You will see I have posted an issue about 'Date format = '. I mention this because in trying to understand what was happening, I too had a case where all the dates were showing as the same in a thread. I suspect your 12/31/1969 was due to the entries as being read were non-existant or blank.
Of course I may have mis-understood your requirements.
|
Tried using the Time format setting, however I only want the time to be selected, so when i enter the datetime type it shows the date and time.
If there was a way to just have the time to be drop down menus vs the date and time all together, I would find that helpful.
As for the "$entry time" suggestion, it only serves to log the exact time the entry was made into elog. Where as I want it to be manually set.
In this example we've created an sql script to pull information from an oracle database, which then creates an elog entry.
We have multiple fields which are populated and locked so only admin can edit them.
Our contractor then edits the entry with a date / time / location, and a few other things.
the Date and Time are separate attributes. We'd prefer to keep it like that just because of the other scripts that run on the elog entries, (pulls day by day reports and formats and calculates summaries in excel automatically).
Any other suggestions would be helpful.
Thanks for your reply. |
|
Re: Type <attribute> = Date - Issue, posted by Andreas Luedeke on Wed Sep 12 10:50:40 2012
|
| Garret Delaronde wrote: |
|
I haven't found anything in the forums about this. Apologies if its a duplicate.
I am fairly familiar with ELog, use it for multiple purposes on 5 different Virtual Servers at work.
Currently looking to do some updates to one of the instances with the Date Type setting.
We have 17,000 entries all which have had manual entries for a Date Attribute for the last year and 8 months.
Due to regular entry errors on part of our contractors using it, (Eg: using "Aug" instead of "08", or using "-" instead of "/"), I want to change over to using the date type attribute (Type <attribute> = Date).
However the problem i found, the moment i save this in the config, and go to the list of entries, the date has changed on all of the entries to 12/31/1969. Which is BAD for our operation. So after removing the Type Date Setting the dates go back to normal.
Is there anyway to retain those dates so they display as they are and then only new entries would fall under the new date type setting?
Syntax manual didn't help much for this issue.
|
The problem is, that the existing entries have a string content for this specific attribute.
An attribute with a "date" type content should contain a integer number, which represents the seconds of the epoch (starting with zero on 1-Jan-1970 at 00:00:00).
What you need to do is writing a script that reads all *a.log files in the logbook directory and converts lines of the type:
<attribute>: <text>
to lines like
<attribute>: $(date -d "<text>" +%s)
Unfortunately elog does not provide you with such a tool.
But since you have to write it now anyway now, you could submit your code to this forum 
Andreas |
|
Re: Two different attributes with the same list, posted by Stefan Ritt on Wed Jan 17 12:49:25 2007
|
| deletoille wrote: | In this picture of my project, All the attributes included in the red circle are the same except the names of the attribute “Equipement Incriminé” and “Equipement impacté”.
“Equipement Incriminé” and “Equipement impacté” have the same list.
The displayed list for the both attributes is the multiple conditions result coming from the choice of “groupe incriminé or impacté, sous ensemble, selection, and localisation”.
So if I have to program the list twice, it will be twice bigger.
Do I need to program the same list twice for the two attributes or is there a simple command to say that the two precedent attributes are equal?
|
I don't understand your problem. The picture you attached, was this some ELOG output (it looks very different than the usual one...)? Do mean you have two attributes with the same "Options <attribute> = ...,..,.." list? With "multiple conditions" you mean that you do a search in ELOG with a condition one one attribute, but in the filter list both attributes having the same option list are shown. Is this correct? What section of the configuration file are you talking about?
Best regards
Stefan |
|