Elog command line problem, posted by Razvan Gornea on Tue May 28 09:16:18 2013
|
I'm trying to use the command line to post automatically entries from a web based calendar. I run elogd behind SSL with user/pass configuration. I created an account for the calendar and used the following command line.
[gornea@lheppc63 ~]
$ elog -v -s -a Subject=Test -a Type=Notice -a Category=Planning -h svn.lhep.unibe.ch -p 443 -l "LHEP EXO General" -u calendar ******** "SORRY for SPAMMING! Testing automated posts from command line"
It seems like all parameters are OK but for some reason the connection gets closed. Anybody has an idea why? The SSL certificate is not valid and on the web page users have first to accept it. Can this explain the problem? Is there a flag for elog command line to instruct it to ignore SSL warnings? Thanks a lot!
Command line output:
Successfully connected to host svn.lhep.unibe.ch, port 443
Request sent to host:
POST /LHEP+EXO+General/ HTTP/1.0
Content-Type: multipart/form-data; boundary=---------------------------16B1637A4CDBB4E6448003F4
Host: lheppc63.lhep.unibe.ch
User-Agent: ELOG
Content-Length: 1105
Content sent to host:
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="cmd"
Submit
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="unm"
calendar
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="upwd"
Z28yQjUyIQ==
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="exp"
LHEP EXO General
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="encoding"
ELCode
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="Subject"
Test
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="Type"
Notice
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="Category"
Planning
---------------------------16B1637A4CDBB4E6448003F4
Content-Disposition: form-data; name="Text"
SORRY for SPAMMING! Testing automated posts from command line
---------------------------16B1637A4CDBB4E6448003F4
Response received:
HTTP/1.1 302 Found
Server: ELOG HTTP 2.9.2-2455
Location: https://svn.lhep.unibe.ch/LHEP+EXO+General/
Connection: Close
<html>redir</html>
Message successfully transmitted, ID=
[gornea@lheppc63 ~]
$
|
|
Admin delete option, posted by Hal Proctor on Wed May 22 22:24:14 2013
|
How can I show the Delete option for Admins?
So I have a logbook with the following config:
[Elog]
Admin User = me, otherguy
Deny Change Config File = otherguy
Restrict edit = 1
Restrict edit time = 4
Menu commands = List, New, Edit, Reply,Last Day, Find, Config, Help |
|
some menu commands formed with broken links, posted by Ken Ludington on Tue May 7 22:15:37 2013
|
On many of my logbooks when I specify the menu commands to appear i will get one, usually 'List', which has a
link not back to the logbook itself but to the root of the elog web server i.e. http:/hostname.domain:8080
But nothing will respond without the logbook name after the port number. This also seems to be happening to the
"back" submit button. I can't seem to figure out how to address it. Suggestions? |
Re: some menu commands formed with broken links, posted by Garret Delaronde on Fri May 10 17:24:55 2013
|
> On many of my logbooks when I specify the menu commands to appear i will get one, usually 'List', which has a
> link not back to the logbook itself but to the root of the elog web server i.e. http:/hostname.domain:8080
> But nothing will respond without the logbook name after the port number. This also seems to be happening to the
> "back" submit button. I can't seem to figure out how to address it. Suggestions?
Can you show us your config? I had this issue when i was initially trying to integrate elog with apache. |
|
Re: some menu commands formed with broken links, posted by Ken Ludington on Fri May 10 19:26:50 2013
|
Here's the global section and the logbook section for one of the logbooks affected. Of note, the 'demo' logbook works
fine and does not have this issue.
[global]
port = 8080
SMTP host = localhost
Welcome title = Welcome
Top group 2012 = 2011, 2010, 2009, 2008, 2007, WINTER
[WINTER]
;*****Look and Feel*****
Page title = Winter Weather
List page title = Winter Weather
Edit page title = Winter Weather
Theme = default
CSS = default.css
Comment = Winter Weather
Title image =
;*****Email*****
Use Email From = me@me.com
Suppress Email to users = 1
Display Email recipients = 0
Email Encoding = 4
Suppress Email on edit = 1
;*****Settings*****
Entries per page = 30
;Reverse sort = 1
Expand default = 2
Display mode = SUMMARY
Mode command = 0
Time format = %d%B%Y-%H:%M
Summary lines = 15
Show top groups = 0
Message height = 8
Message width = 38
Default encoding = 1
Mode commands = 0
Suppress default = 2
Resubmit default = 2
Back to main = 1
RSS Title = $entry time - $Event
;*****MENU*****
List Menu commands = New, Find
Menu commands = List, New, Edit, Find, Reply, Delete |
|
Re: some menu commands formed with broken links, posted by Stefan Ritt on Fri May 17 15:26:50 2013
|
> Top group 2012 = 2011, 2010, 2009, 2008, 2007, WINTER
Your usage of "Top group" is strange. Top groups should only be used for independent groups of logbooks, more like you were running one dedicated sever fore
a group of logbooks. Further, you defined logbooks (2008, 2009, ...) which do not exist in your config. Why don't you just remove the "Top group" line from your
config? If you want to group different logbooks, just use the "group" command as written in the docs.
/Stefan |
|
Kerberos on Windows server, posted by Hal Proctor on Mon May 13 16:44:05 2013
|
Does anyone have a success story with kerberos on windows? |
|
Re: Kerberos on Windows server, posted by Hal Proctor on Thu May 16 16:29:16 2013
|
| Hal Proctor wrote: |
|
Does anyone have a success story with kerberos on windows?
|
Anyone? Bueller? |
|
Multi Language based on logged on user?, posted by Hal Proctor on Thu May 16 15:41:34 2013
|
Can ELog support different languages based on the logged on user? |
|
Auto-Generate new logbook daily, posted by Ryan Blakeslee on Fri Apr 26 22:29:50 2013
|
Hello,
I am currently using ELOG as a daily logbook for work performed for customers. This is a critical tool and process for 1. Showing customers work history 2. having a searchable knowledge base for future reference.
Currently, I will create a new log entry, assign the customer using a custom ROPTION in my elog.conf. This process all works fine, mostly, except I run into the following obstacles (that are all human related.)
1. Many days, there are no log entries to be created for a PARTICULAR customer, and other days there are no long entries to be created for ANY customer.
2. Many days when there is a log entry to be created, it's created by me much later then when the work was performed. For example, I do a bunch of work Tuesday and Wednesday, but I don't have time to enter all my entries until Thursday.
2A. In this case, I have to manually go back and edit the log entries with text-editor to adjust the times, dates, and such.
2B. In this case, I have log files with a file-name of THURSDAY (042513a.log) for work entries done on Tues and Wed, so I have to go back and rename the log files for consistency sake (mv 042513a.log 042313a.log). ** I know this is not a requirement of the program, but I like to have the log filenames consistent with the dates contained in them.
All these I admit are human error -- but as a small business owner, I just can't always get to the log entries every day.
To overcome this, the manual solution would: at the beginning of each day, create a new log entry -- regardless of work to be performed and updated later. This would serve as sort of a place holder.
However, I can't commit myself to always create a log entry for every day either. Again, human error.
Is what I would like to be able to do is create a new log entry, every single day, automatically. I would then have a growing log dir of daily log entries (files) for ever day of the week, most blank but some would then contain data that I enter later-- either at the end-of-day or on a day I have downtime and can commit to administrative work.
My thought is I could probably schedule a cron job do to this, but i'm not completely sure how I would go about auto-populating the incremental ID's, dates, etc. Second, I don't know if there is a way to do this within ELOG itself, or if there is a built-in mechanism that already covers this.
Has anyone run into this, or solved this problem, or can someone kindly point me in the right direction or how I can implement the daily auto creation of logs?
Thank you very much in advance!
|
|
Re: Auto-Generate new logbook daily, posted by Stefan Ritt on Sat Apr 27 11:53:41 2013
|
| Ryan Blakeslee wrote: |
|
Hello,
I am currently using ELOG as a daily logbook for work performed for customers. This is a critical tool and process for 1. Showing customers work history 2. having a searchable knowledge base for future reference.
Currently, I will create a new log entry, assign the customer using a custom ROPTION in my elog.conf. This process all works fine, mostly, except I run into the following obstacles (that are all human related.)
1. Many days, there are no log entries to be created for a PARTICULAR customer, and other days there are no long entries to be created for ANY customer.
2. Many days when there is a log entry to be created, it's created by me much later then when the work was performed. For example, I do a bunch of work Tuesday and Wednesday, but I don't have time to enter all my entries until Thursday.
2A. In this case, I have to manually go back and edit the log entries with text-editor to adjust the times, dates, and such.
2B. In this case, I have log files with a file-name of THURSDAY (042513a.log) for work entries done on Tues and Wed, so I have to go back and rename the log files for consistency sake (mv 042513a.log 042313a.log). ** I know this is not a requirement of the program, but I like to have the log filenames consistent with the dates contained in them.
All these I admit are human error -- but as a small business owner, I just can't always get to the log entries every day.
To overcome this, the manual solution would: at the beginning of each day, create a new log entry -- regardless of work to be performed and updated later. This would serve as sort of a place holder.
However, I can't commit myself to always create a log entry for every day either. Again, human error.
Is what I would like to be able to do is create a new log entry, every single day, automatically. I would then have a growing log dir of daily log entries (files) for ever day of the week, most blank but some would then contain data that I enter later-- either at the end-of-day or on a day I have downtime and can commit to administrative work.
My thought is I could probably schedule a cron job do to this, but i'm not completely sure how I would go about auto-populating the incremental ID's, dates, etc. Second, I don't know if there is a way to do this within ELOG itself, or if there is a built-in mechanism that already covers this.
Has anyone run into this, or solved this problem, or can someone kindly point me in the right direction or how I can implement the daily auto creation of logs?
Thank you very much in advance!
|
Actually I would not worry with the 042313a.log files. In a future version of elog they might be replaced by a database or so. I see two options:
- Add an attribute of date/time type. You do that with "Type <attribute> = datetime". Then you can assign a certain date or time to each entry you do. That means you can tag an entry with the date of yesterday or so. If you make that date then the main database key (via "List display") it basically replaces your "internal" date.
- You can do automatic entries with the "elog" utility coming with the distribution and described here. This you can even run from a cron job. If you submit a new entry from elog, you get automatically the incremented IDs etc. You can use some default values for the attributes, which you can change later.
|
|
Re: Auto-Generate new logbook daily, posted by David Pilgram on Sat Apr 27 13:21:38 2013
|
| Stefan Ritt wrote: |
|
| Ryan Blakeslee wrote: |
|
Hello,
I am currently using ELOG as a daily logbook for work performed for customers. This is a critical tool and process for 1. Showing customers work history 2. having a searchable knowledge base for future reference.
Currently, I will create a new log entry, assign the customer using a custom ROPTION in my elog.conf. This process all works fine, mostly, except I run into the following obstacles (that are all human related.)
1. Many days, there are no log entries to be created for a PARTICULAR customer, and other days there are no long entries to be created for ANY customer.
2. Many days when there is a log entry to be created, it's created by me much later then when the work was performed. For example, I do a bunch of work Tuesday and Wednesday, but I don't have time to enter all my entries until Thursday.
2A. In this case, I have to manually go back and edit the log entries with text-editor to adjust the times, dates, and such.
2B. In this case, I have log files with a file-name of THURSDAY (042513a.log) for work entries done on Tues and Wed, so I have to go back and rename the log files for consistency sake (mv 042513a.log 042313a.log). ** I know this is not a requirement of the program, but I like to have the log filenames consistent with the dates contained in them.
All these I admit are human error -- but as a small business owner, I just can't always get to the log entries every day.
To overcome this, the manual solution would: at the beginning of each day, create a new log entry -- regardless of work to be performed and updated later. This would serve as sort of a place holder.
However, I can't commit myself to always create a log entry for every day either. Again, human error.
Is what I would like to be able to do is create a new log entry, every single day, automatically. I would then have a growing log dir of daily log entries (files) for ever day of the week, most blank but some would then contain data that I enter later-- either at the end-of-day or on a day I have downtime and can commit to administrative work.
My thought is I could probably schedule a cron job do to this, but i'm not completely sure how I would go about auto-populating the incremental ID's, dates, etc. Second, I don't know if there is a way to do this within ELOG itself, or if there is a built-in mechanism that already covers this.
Has anyone run into this, or solved this problem, or can someone kindly point me in the right direction or how I can implement the daily auto creation of logs?
Thank you very much in advance!
|
Actually I would not worry with the 042313a.log files. In a future version of elog they might be replaced by a database or so. I see two options:
- Add an attribute of date/time type. You do that with "Type <attribute> = datetime". Then you can assign a certain date or time to each entry you do. That means you can tag an entry with the date of yesterday or so. If you make that date then the main database key (via "List display") it basically replaces your "internal" date.
- You can do automatic entries with the "elog" utility coming with the distribution and described here. This you can even run from a cron job. If you submit a new entry from elog, you get automatically the incremented IDs etc. You can use some default values for the attributes, which you can change later.
|
Purists look away now.
I have the same issues regarding "catching up" of entries. So what I do is use the date command to reset the computer's time back to the time that the entry [i]should[/i] have been made. Say I need to put an entry for last Thursday (today is Saturday 27th),
Firstly I set the clock back by
date 04252200
(I use a time of 22:00 or later as code for a retro-made entry, the date being the important point for me).
Then any entry will have the correct time (sic) and date entry within the file, and the file the expected format of 130425a.log
After Thursday's batch of entries, I then simply reset the clock for the next entry/ies or indeed back to real time.
Mind you, my log files have the format yymmdda.log, whereas you state yours are mmddyya.log, which strikes me as a very high degree of flexibility!
---
Nice to meet someone else who gets down to the bare ascii and knows how to edit the xxxxxxa.log files! |
|
Re: Auto-Generate new logbook daily, posted by Stefan Ritt on Sat Apr 27 15:30:28 2013
|
| David Pilgram wrote: |
|
Mind you, my log files have the format yymmdda.log, whereas you state yours are mmddyya.log, which strikes me as a very high degree of flexibility!
|
Sure, its YYMMDDa.log, I was wrong. That format has been chosen so that the normal (ASCII-) sorting shows the files in proper order. |
|
Re: Auto-Generate new logbook daily, posted by Andreas Luedeke on Mon Apr 29 10:17:54 2013
|
| David Pilgram wrote: |
|
| Stefan Ritt wrote: |
|
| Ryan Blakeslee wrote: |
|
Hello,
I am currently using ELOG as a daily logbook for work performed for customers. This is a critical tool and process for 1. Showing customers work history 2. having a searchable knowledge base for future reference.
Currently, I will create a new log entry, assign the customer using a custom ROPTION in my elog.conf. This process all works fine, mostly, except I run into the following obstacles (that are all human related.)
1. Many days, there are no log entries to be created for a PARTICULAR customer, and other days there are no long entries to be created for ANY customer.
2. Many days when there is a log entry to be created, it's created by me much later then when the work was performed. For example, I do a bunch of work Tuesday and Wednesday, but I don't have time to enter all my entries until Thursday.
2A. In this case, I have to manually go back and edit the log entries with text-editor to adjust the times, dates, and such.
2B. In this case, I have log files with a file-name of THURSDAY (042513a.log) for work entries done on Tues and Wed, so I have to go back and rename the log files for consistency sake (mv 042513a.log 042313a.log). ** I know this is not a requirement of the program, but I like to have the log filenames consistent with the dates contained in them.
All these I admit are human error -- but as a small business owner, I just can't always get to the log entries every day.
To overcome this, the manual solution would: at the beginning of each day, create a new log entry -- regardless of work to be performed and updated later. This would serve as sort of a place holder.
However, I can't commit myself to always create a log entry for every day either. Again, human error.
Is what I would like to be able to do is create a new log entry, every single day, automatically. I would then have a growing log dir of daily log entries (files) for ever day of the week, most blank but some would then contain data that I enter later-- either at the end-of-day or on a day I have downtime and can commit to administrative work.
My thought is I could probably schedule a cron job do to this, but i'm not completely sure how I would go about auto-populating the incremental ID's, dates, etc. Second, I don't know if there is a way to do this within ELOG itself, or if there is a built-in mechanism that already covers this.
Has anyone run into this, or solved this problem, or can someone kindly point me in the right direction or how I can implement the daily auto creation of logs?
Thank you very much in advance!
|
Actually I would not worry with the 042313a.log files. In a future version of elog they might be replaced by a database or so. I see two options:
- Add an attribute of date/time type. You do that with "Type <attribute> = datetime". Then you can assign a certain date or time to each entry you do. That means you can tag an entry with the date of yesterday or so. If you make that date then the main database key (via "List display") it basically replaces your "internal" date.
- You can do automatic entries with the "elog" utility coming with the distribution and described here. This you can even run from a cron job. If you submit a new entry from elog, you get automatically the incremented IDs etc. You can use some default values for the attributes, which you can change later.
|
Purists look away now.
I have the same issues regarding "catching up" of entries. So what I do is use the date command to reset the computer's time back to the time that the entry [i]should[/i] have been made. Say I need to put an entry for last Thursday (today is Saturday 27th),
Firstly I set the clock back by
date 04252200
(I use a time of 22:00 or later as code for a retro-made entry, the date being the important point for me).
Then any entry will have the correct time (sic) and date entry within the file, and the file the expected format of 130425a.log
After Thursday's batch of entries, I then simply reset the clock for the next entry/ies or indeed back to real time.
Mind you, my log files have the format yymmdda.log, whereas you state yours are mmddyya.log, which strikes me as a very high degree of flexibility!
---
Nice to meet someone else who gets down to the bare ascii and knows how to edit the xxxxxxa.log files!
|
Just my two cent:
I would strongly recomment NOT to go back and forth with the system time.
In some cases this can cause you severe problems with your control system.
Stefans suggestion works fine for our operations logbook: I've just introduced an attribute "When" and sort my entries according to this attribute.
The line in the config:
Start page = ?rsort=When
takes care that this sorting is the default.
The advantage of this approach is in addition, that you keep track of both dates:
the date when the work had been performed and
the date when you've actually entered the information.
Sometimes that turns out to be useful to me to figure out what I did and when ;-)
As to editing the bare ascii: I do this a lot, even with sed scripts.
But there is a disclaimer: you can crash elogd with corrupted entries and you may have a hard time figuring out why it crashes.
For example accidentally deleting a digit in a cross reference can create a loop that causes elogd to get non-responsive without error: try to find that!
I would strongly advise not to build any user application build on editing the ascii files. Just use it for system administration.
Andreas
--
He who knows others is wise.
He who knows himself is enlightened.
-- Lao Tsu
 ⇄
Detect language » English
|
|
Re: Auto-Generate new logbook daily, posted by Ryan Blakeslee on Tue May 7 04:57:37 2013
|
| Andreas Luedeke wrote: |
|
| David Pilgram wrote: |
|
| Stefan Ritt wrote: |
|
| Ryan Blakeslee wrote: |
|
Hello,
I am currently using ELOG as a daily logbook for work performed for customers. This is a critical tool and process for 1. Showing customers work history 2. having a searchable knowledge base for future reference.
Currently, I will create a new log entry, assign the customer using a custom ROPTION in my elog.conf. This process all works fine, mostly, except I run into the following obstacles (that are all human related.)
1. Many days, there are no log entries to be created for a PARTICULAR customer, and other days there are no long entries to be created for ANY customer.
2. Many days when there is a log entry to be created, it's created by me much later then when the work was performed. For example, I do a bunch of work Tuesday and Wednesday, but I don't have time to enter all my entries until Thursday.
2A. In this case, I have to manually go back and edit the log entries with text-editor to adjust the times, dates, and such.
2B. In this case, I have log files with a file-name of THURSDAY (042513a.log) for work entries done on Tues and Wed, so I have to go back and rename the log files for consistency sake (mv 042513a.log 042313a.log). ** I know this is not a requirement of the program, but I like to have the log filenames consistent with the dates contained in them.
All these I admit are human error -- but as a small business owner, I just can't always get to the log entries every day.
To overcome this, the manual solution would: at the beginning of each day, create a new log entry -- regardless of work to be performed and updated later. This would serve as sort of a place holder.
However, I can't commit myself to always create a log entry for every day either. Again, human error.
Is what I would like to be able to do is create a new log entry, every single day, automatically. I would then have a growing log dir of daily log entries (files) for ever day of the week, most blank but some would then contain data that I enter later-- either at the end- of-day or on a day I have downtime and can commit to administrative work.
My thought is I could probably schedule a cron job do to this, but i'm not completely sure how I would go about auto-populating the incremental ID's, dates, etc. Second, I don't know if there is a way to do this within ELOG itself, or if there is a built-in mechanism that already covers this.
Has anyone run into this, or solved this problem, or can someone kindly point me in the right direction or how I can implement the daily auto creation of logs?
Thank you very much in advance!
|
Actually I would not worry with the 042313a.log files. In a future version of elog they might be replaced by a database or so. I see two options:
- Add an attribute of date/time type. You do that with "Type <attribute> = datetime". Then you can assign a certain date or time to each entry you do. That means you can tag an entry with the date of yesterday or so. If you make that date then the main database key (via "List display") it basically replaces your "internal" date.
- You can do automatic entries with the "elog" utility coming with the distribution and described here. This you can even run from a cron job. If you submit a new entry from elog, you get automatically the incremented IDs etc. You can use some default values for the attributes, which you can change later.
|
Purists look away now.
I have the same issues regarding "catching up" of entries. So what I do is use the date command to reset the computer's time back to the time that the entry [i]should[/i] have been made. Say I need to put an entry for last Thursday (today is Saturday 27th),
Firstly I set the clock back by
date 04252200
(I use a time of 22:00 or later as code for a retro-made entry, the date being the important point for me).
Then any entry will have the correct time (sic) and date entry within the file, and the file the expected format of 130425a.log
After Thursday's batch of entries, I then simply reset the clock for the next entry/ies or indeed back to real time.
Mind you, my log files have the format yymmdda.log, whereas you state yours are mmddyya.log, which strikes me as a very high degree of flexibility!
---
Nice to meet someone else who gets down to the bare ascii and knows how to edit the xxxxxxa.log files!
|
Just my two cent:
I would strongly recomment NOT to go back and forth with the system time.
In some cases this can cause you severe problems with your control system.
Stefans suggestion works fine for our operations logbook: I've just introduced an attribute "When" and sort my entries according to this attribute.
The line in the config:
Start page = ?rsort=When
takes care that this sorting is the default.
The advantage of this approach is in addition, that you keep track of both dates:
the date when the work had been performed and
the date when you've actually entered the information.
Sometimes that turns out to be useful to me to figure out what I did and when ;-)
As to editing the bare ascii: I do this a lot, even with sed scripts.
But there is a disclaimer: you can crash elogd with corrupted entries and you may have a hard time figuring out why it crashes.
For example accidentally deleting a digit in a cross reference can create a loop that causes elogd to get non-responsive without error: try to find that!
I would strongly advise not to build any user application build on editing the ascii files. Just use it for system administration.
Andreas
--
He who knows others is wise.
He who knows himself is enlightened.
-- Lao Tsu
⇄
Detect language » English
|
Hello Andreas, Stephan and David,
Thank you so much for the very insightful feedback -- it's very much appreciated!
I took all of the tips and created a solution that encompasses most of the feedback, and I think it solves my problem nicely while adhering to my desire to keep log filenames in order as well as limiting the risk with moving/renaming, etc.
1. First, I have created a cron job that runs daily at 12:01AM, which runs the following command (This will create a new entry as a place-holder at 12:01AM every day)
CODE:
elog -h localhost -p 8080 -l Daily -a Customer=CRON -a Subject="Daily Log - System Generated" -a Hours=New -a TravelHrs="0" -a Author=CRON -a Type="System Generated" -a Status="New" -a "Locale=localhost" -v "Auto-generated log entry."
2. Second, I added the "When" attribute, per Andreas' suggestion.
3. Last, I added the recommended sort command to my .cfg which will exclude the auto-generated logs from showing up and cluttering my view; essentially making them invisible. I sort by type to exclude the system generated types.
Now, -- to go back in time and enter my "catch-up" data, I'll use the 'Find' in my menu, and find by type = system generated. That will pull up all the auto-generated entries. I'll then open whatever day(s) log(s) and edit them, chose the "when" to be the actual day the log entry is for, and enter the data.
I think this is a perfect solution - thanks so much! PS - Nice to meet you too David -glad to know someone else out there thinks like I do! :-)
|
|
Re: Auto-Generate new logbook daily, posted by David Pilgram on Tue May 7 11:54:23 2013
|
| Ryan Blakeslee wrote: |
|
| Andreas Luedeke wrote: |
|
| David Pilgram wrote: |
|
| Stefan Ritt wrote: |
|
| Ryan Blakeslee wrote: |
|
Hello,
I am currently using ELOG as a daily logbook for work performed for customers. This is a critical tool and process for 1. Showing customers work history 2. having a searchable knowledge base for future reference.
Currently, I will create a new log entry, assign the customer using a custom ROPTION in my elog.conf. This process all works fine, mostly, except I run into the following obstacles (that are all human related.)
1. Many days, there are no log entries to be created for a PARTICULAR customer, and other days there are no long entries to be created for ANY customer.
2. Many days when there is a log entry to be created, it's created by me much later then when the work was performed. For example, I do a bunch of work Tuesday and Wednesday, but I don't have time to enter all my entries until Thursday.
2A. In this case, I have to manually go back and edit the log entries with text-editor to adjust the times, dates, and such.
2B. In this case, I have log files with a file-name of THURSDAY (042513a.log) for work entries done on Tues and Wed, so I have to go back and rename the log files for consistency sake (mv 042513a.log 042313a.log). ** I know this is not a requirement of the program, but I like to have the log filenames consistent with the dates contained in them.
All these I admit are human error -- but as a small business owner, I just can't always get to the log entries every day.
To overcome this, the manual solution would: at the beginning of each day, create a new log entry -- regardless of work to be performed and updated later. This would serve as sort of a place holder.
However, I can't commit myself to always create a log entry for every day either. Again, human error.
Is what I would like to be able to do is create a new log entry, every single day, automatically. I would then have a growing log dir of daily log entries (files) for ever day of the week, most blank but some would then contain data that I enter later-- either at the end- of-day or on a day I have downtime and can commit to administrative work.
My thought is I could probably schedule a cron job do to this, but i'm not completely sure how I would go about auto-populating the incremental ID's, dates, etc. Second, I don't know if there is a way to do this within ELOG itself, or if there is a built-in mechanism that already covers this.
Has anyone run into this, or solved this problem, or can someone kindly point me in the right direction or how I can implement the daily auto creation of logs?
Thank you very much in advance!
|
Actually I would not worry with the 042313a.log files. In a future version of elog they might be replaced by a database or so. I see two options:
- Add an attribute of date/time type. You do that with "Type <attribute> = datetime". Then you can assign a certain date or time to each entry you do. That means you can tag an entry with the date of yesterday or so. If you make that date then the main database key (via "List display") it basically replaces your "internal" date.
- You can do automatic entries with the "elog" utility coming with the distribution and described here. This you can even run from a cron job. If you submit a new entry from elog, you get automatically the incremented IDs etc. You can use some default values for the attributes, which you can change later.
|
Purists look away now.
I have the same issues regarding "catching up" of entries. So what I do is use the date command to reset the computer's time back to the time that the entry [i]should[/i] have been made. Say I need to put an entry for last Thursday (today is Saturday 27th),
Firstly I set the clock back by
date 04252200
(I use a time of 22:00 or later as code for a retro-made entry, the date being the important point for me).
Then any entry will have the correct time (sic) and date entry within the file, and the file the expected format of 130425a.log
After Thursday's batch of entries, I then simply reset the clock for the next entry/ies or indeed back to real time.
Mind you, my log files have the format yymmdda.log, whereas you state yours are mmddyya.log, which strikes me as a very high degree of flexibility!
---
Nice to meet someone else who gets down to the bare ascii and knows how to edit the xxxxxxa.log files!
|
Just my two cent:
I would strongly recomment NOT to go back and forth with the system time.
In some cases this can cause you severe problems with your control system.
Stefans suggestion works fine for our operations logbook: I've just introduced an attribute "When" and sort my entries according to this attribute.
The line in the config:
Start page = ?rsort=When
takes care that this sorting is the default.
The advantage of this approach is in addition, that you keep track of both dates:
the date when the work had been performed and
the date when you've actually entered the information.
Sometimes that turns out to be useful to me to figure out what I did and when ;-)
As to editing the bare ascii: I do this a lot, even with sed scripts.
But there is a disclaimer: you can crash elogd with corrupted entries and you may have a hard time figuring out why it crashes.
For example accidentally deleting a digit in a cross reference can create a loop that causes elogd to get non-responsive without error: try to find that!
I would strongly advise not to build any user application build on editing the ascii files. Just use it for system administration.
Andreas
--
He who knows others is wise.
He who knows himself is enlightened.
-- Lao Tsu
⇄
Detect language » English
|
Hello Andreas, Stephan and David,
Thank you so much for the very insightful feedback -- it's very much appreciated!
I took all of the tips and created a solution that encompasses most of the feedback, and I think it solves my problem nicely while adhering to my desire to keep log filenames in order as well as limiting the risk with moving/renaming, etc.
1. First, I have created a cron job that runs daily at 12:01AM, which runs the following command (This will create a new entry as a place-holder at 12:01AM every day)
CODE:
elog -h localhost -p 8080 -l Daily -a Customer=CRON -a Subject="Daily Log - System Generated" -a Hours=New -a TravelHrs="0" -a Author=CRON -a Type="System Generated" -a Status="New" -a "Locale=localhost" -v "Auto-generated log entry."
2. Second, I added the "When" attribute, per Andreas' suggestion.
3. Last, I added the recommended sort command to my .cfg which will exclude the auto-generated logs from showing up and cluttering my view; essentially making them invisible. I sort by type to exclude the system generated types.
Now, -- to go back in time and enter my "catch-up" data, I'll use the 'Find' in my menu, and find by type = system generated. That will pull up all the auto-generated entries. I'll then open whatever day(s) log(s) and edit them, chose the "when" to be the actual day the log entry is for, and enter the data.
I think this is a perfect solution - thanks so much! PS - Nice to meet you too David -glad to know someone else out there thinks like I do! :-)
|
Hi Ryan,
Glad you've got your solution. Sadly, won't work for me, as my 'catching up' is often as replies to some existing threads, rather than just the need to have the day's work under the day's date. But useful to know for the future.
As for the computer time switching, I am aware of the issues, it's a stand-alone linux box, I've found elog to be surprisingly tolerant, everything's backed up. The introduction of a 'When' attribute had better be on new logbooks or introduced at end of year (esp during quiet time) so that existing books don't fail to find what I'm looking for in searches.
As for ascii coding the yymmdda.log file, and the infinate loops, been there, got the tee-shirt. In all bar one case I've found and corrected the problem, although in one case I became convinced it had to be a 'hidden' character because deleteing and retyping the entry letter by letter cured the issue. |
|
Re: Auto-Generate new logbook daily, posted by Andreas Luedeke on Mon May 13 22:31:37 2013
|
| David Pilgram wrote: |
|
[...]
As for the computer time switching, I am aware of the issues, it's a stand-alone linux box, I've found elog to be surprisingly tolerant, everything's backed up. The introduction of a 'When' attribute had better be on new logbooks or introduced at end of year (esp during quiet time) so that existing books don't fail to find what I'm looking for in searches.
[...]
|
Yes, adding a new attribute in a logbook is not straight forward.
But it is doable: that is one of the things that I write SED scripts for. You just need to add the attribute in all old entries, and in this specific case you can use the entry time to initialise the "when" attribute.
Of course I would only do that on a copy of my data and run a separate elogd server on that data to see if anything is screwed up :-)
Cheers
Andreas
⇄
Detect language » English
|
|
admin user access admin page, not config page, posted by Szu-Ching Peckner on Tue Sep 18 17:57:47 2012
|
We have multiple logbooks. Each user is admin user for his/her own logbook.
I want user be able to modify config file, but no access to user setting, such as see user list, change password, new user, remove user.
[logbook1]
Admin user = user1
Login user = user1, user2
Allow Config = user1
List Menu commands = Admin, Config
user1 click on Admin, it opens config file, when user1 click on save, user1 is brought to Config page, which has select user list on top, Change password, Remove user, New user buttons on bottom. Is there a way that admin user has access to config file, but no access to user info at all (not even presented to them). Is there a way after user1 click save, page doesn't go to that config page?
I could put
Deny Change password =
Deny Remove user
Deny New user
so when user1 click on those buttons, user1 will get command not allowed. However I would rather have user1 not even see that page.
|
|
Re: admin user access admin page, not config page, posted by Garret Delaronde on Fri May 10 17:37:24 2013
|
| Szu-Ching Peckner wrote: |
|
We have multiple logbooks. Each user is admin user for his/her own logbook.
I want user be able to modify config file, but no access to user setting, such as see user list, change password, new user, remove user.
[logbook1]
Admin user = user1
Login user = user1, user2
Allow Config = user1
List Menu commands = Admin, Config
user1 click on Admin, it opens config file, when user1 click on save, user1 is brought to Config page, which has select user list on top, Change password, Remove user, New user buttons on bottom. Is there a way that admin user has access to config file, but no access to user info at all (not even presented to them). Is there a way after user1 click save, page doesn't go to that config page?
I could put
Deny Change password =
Deny Remove user
Deny New user
so when user1 click on those buttons, user1 will get command not allowed. However I would rather have user1 not even see that page.
|
If they have admin rights, the add user button cannot be removed as far as I know.
But even if they can add a user, they only have ability to add a user to the single logbook they are an admin on so they wouldn't be able to add users to other peoples logbooks.
Not sure it helps but that's about all I can really speak to. |
|
Blockying user access, posted by Gian Henriques on Fri Apr 26 18:39:11 2013
|
How can I block access to some tools (like edit, erase, config...) for each user? I want only admin users can edit, erase , etc.
I want know too, how can I erase configuration of SMTP? I make a test with the "elogd -t" command and now every time I create a new entry in my log book I receve the mensage of error to send email, cause I don't configure a SMTP host. |
|
Re: Blockying user access, posted by Garret Delaronde on Fri Apr 26 19:48:01 2013
|
| Gian Henriques wrote: |
|
How can I block access to some tools (like edit, erase, config...) for each user? I want only admin users can edit, erase , etc.
I want know too, how can I erase configuration of SMTP? I make a test with the "elogd -t" command and now every time I create a new entry in my log book I receve the mensage of error to send email, cause I don't configure a SMTP host.
|
Hello, you can use the "Deny" flag in the config file for each logbook.
Deny <function> = <user>
Example: Deny Edit = Gian
simply add as many deny functions as you would like. Its a bit of work if you have a lot of logbooks but its the easiest solution.
Hope that helps.
Elog Syntax guide is helpful for this stuff too. |
|
Re: Blockying user access, posted by Gian Henriques on Wed May 8 19:17:09 2013
|
| Garret Delaronde wrote: |
|
| Gian Henriques wrote: |
|
How can I block access to some tools (like edit, erase, config...) for each user? I want only admin users can edit, erase , etc.
I want know too, how can I erase configuration of SMTP? I make a test with the "elogd -t" command and now every time I create a new entry in my log book I receve the mensage of error to send email, cause I don't configure a SMTP host.
|
Hello, you can use the "Deny" flag in the config file for each logbook.
Deny <function> = <user>
Example: Deny Edit = Gian
simply add as many deny functions as you would like. Its a bit of work if you have a lot of logbooks but its the easiest solution.
Hope that helps.
Elog Syntax guide is helpful for this stuff too.
|
Thanks for help. It work's.
But I want to know if I can block a logbook from a user. For example I have a logbook named "Store". I want only users of the vendors have access to this log. How can I do it?
I didn't find this in manual. |
|
Re: Blockying user access, posted by Gian Henriques on Wed May 8 23:15:34 2013
|
| Gian Henriques wrote: |
|
| Garret Delaronde wrote: |
|
| Gian Henriques wrote: |
|
How can I block access to some tools (like edit, erase, config...) for each user? I want only admin users can edit, erase , etc.
I want know too, how can I erase configuration of SMTP? I make a test with the "elogd -t" command and now every time I create a new entry in my log book I receve the mensage of error to send email, cause I don't configure a SMTP host.
|
Hello, you can use the "Deny" flag in the config file for each logbook.
Deny <function> = <user>
Example: Deny Edit = Gian
simply add as many deny functions as you would like. Its a bit of work if you have a lot of logbooks but its the easiest solution.
Hope that helps.
Elog Syntax guide is helpful for this stuff too.
|
Thanks for help. It work's.
But I want to know if I can block a logbook from a user. For example I have a logbook named "Store". I want only users of the vendors have access to this log. How can I do it?
I didn't find this in manual.
|
The only way I find for this trouble is using the "Login user". But we have something best? |
|
Re: Blockying user access, posted by Garret Delaronde on Fri May 10 17:21:50 2013
|
| Gian Henriques wrote: |
|
| Gian Henriques wrote: |
|
| Garret Delaronde wrote: |
|
| Gian Henriques wrote: |
|
How can I block access to some tools (like edit, erase, config...) for each user? I want only admin users can edit, erase , etc.
I want know too, how can I erase configuration of SMTP? I make a test with the "elogd -t" command and now every time I create a new entry in my log book I receve the mensage of error to send email, cause I don't configure a SMTP host.
|
Hello, you can use the "Deny" flag in the config file for each logbook.
Deny <function> = <user>
Example: Deny Edit = Gian
simply add as many deny functions as you would like. Its a bit of work if you have a lot of logbooks but its the easiest solution.
Hope that helps.
Elog Syntax guide is helpful for this stuff too.
|
Thanks for help. It work's.
But I want to know if I can block a logbook from a user. For example I have a logbook named "Store". I want only users of the vendors have access to this log. How can I do it?
I didn't find this in manual.
|
The only way I find for this trouble is using the "Login user". But we have something best?
|
I haven't found a specific way to block viewing a log book.
I use the top groups settings to keep users in the logbooks they only need access to.
Example
Top Group = Logbook Group1, Logbook Group 2
Group Logbook Group 1 = Logbook1, Logbook2
Group Logbook Group 2 = Logbook3, Logbook4
Then only assign users for logbook1 and logbook2 that you wish to view those logbooks only. They would have to go to the specific top group url in order to view the logbooks.
Then you can go to http://elogurl/(top group)/
And essentially just have the users view the only logbooks they are assigned to. |
|