Re: Execute attribute, posted by Stefan Ritt on Fri May 10 08:19:08 2019
|
I don't understand your question. There is no "inline" vs. "external" script. Using the "execute new = <command>",
you run a script on the server side. Can be powershell under Windows or bash/csh under Linux. I remember however that there has been issues under recent
windows in passing parameters to the shell. Linux certainly works fine, we usse it all the time. |
|
Re: Execute attribute, posted by Alan Grant on Fri May 10 15:01:52 2019
|
I think it was just a matter of my specific interepretation of the documentation, ie: using native OS shell commands vs any script language file
containing shell commands or any app for that matter. Nevertheless I think you've answered my questiuon so it's all good. Thanks Stefan.
|
Shell execute, posted by Alan Grant on Tue May 14 06:07:07 2019
|
I have the line in my elog config to run a Powershell script when submitting a New entry. I just send an email as a test:
Execute New = "Powershell.exe -ExecutionPolicy Bypass D:\SendEmail.ps1"
Fyi, the Powershell statement itself (Send-MailMessage -From 'MeterElog@winnipeg.ca' |
|
Windows Server 2012 - moving logs, posted by Lesley Herren on Thu May 16 01:13:31 2019
|
We are installing a new data center which will be based on Windows 2012 servers. Our current center is on Windows 2008 and will be decommissioned
this year - 2008 servers (because of the security issue) will not be allowed in the new data center. So game plan is to install latest ELOG (3.1.2)
on the 2012 server at the new data center and move the logs over from the 2008 server. I've looked through entries and do not see anything about |
|
Re: Windows Server 2012 - moving logs, posted by Stefan Ritt on Thu May 16 09:12:52 2019
|
Just stop the server. Move your elog directory to the new server (including elogd.cfg, logbook directories, ...). Then check that the elogd.cfg needs
modifications, like the URL which might have changed, then start the new server. V2.9.2 did have an old data format, which *should* be converted automatically.
But first try it out before deleting the old server. |
|
custom subject for mail info, posted by Daniel Pfuhl on Thu May 16 18:00:22 2019
|
Hello,
we are extensively using ELOG for documenting changes in our infrastructure. It is very helpful for us.
To avoid multiple documentation efforts it would be even more helpful if the subject of an ELOG entry also could be the subject of the mail which |
|
Re: Windows Server 2012 - moving logs, posted by David Pilgram on Thu May 16 21:49:06 2019
|
Hi Lesley,
Perhaps I can restate Stefan's comment. The data structure of an elog entry, or indeed the structure of daily file(s) for any particular
logbook has not changed between v2 and v3. What has changed is the directory structure. A set of sub-directories (named by calendar years) |
|
Re: Windows Server 2012 - moving logs, posted by Lesley Herren on Thu May 16 23:07:53 2019
|
Thank you Stefan - it will take a couple of months to set up (many servers being built at the new farm). I will update you on the success of the
files converting automatically.
|