Re: Different way CSS files are handled, posted by Stefan Ritt on Tue Jun 9 09:39:14 2015
|
Ok, fixed again.
Andreas
Luedeke wrote:
Hi Stefan, |
Re: Different timezone settings for each elog, posted by Stefan Ritt on Wed Jun 10 18:13:50 2015
|
The elog server grabs the local timezone from the underlying OS. Under Linux, you can change the timezone using the TZ environment variable. See here: http://www.cyberciti.biz/faq/howto-linux-set-time-zone-per-user-basis/
If you need different time zones on the same server, you have to create two accounts and run two instances of elogd on these accounts. |
Re: Different timezone settings for each elog, posted by gary holman on Wed Jun 10 20:18:06 2015
|
<p> </p>
<table align="center" cellspacing="1" style="border:1px solid #486090; width:98%">
|
Re: Different timezone settings for each elog, posted by gary holman on Wed Jun 10 20:37:48 2015
|
Thanks Stefan, It looks like the group had actually contacted you directly as well (sorry for the redundant work!). Thanks for the help,
the great application and your time.
|
Re: Different timezone settings for each elog, posted by gary holman on Wed Jun 10 22:02:33 2015
|
Still no luck changing the TZ for a single elog service. I completed the following:
* I added a new user/group - central-tz-user (id 1010)
* changed user TZ to central, su as user and confirmed CDT via 'date' |
Re: Different timezone settings for each elog, posted by gary holman on Thu Jun 11 01:32:26 2015
|
Okay, I missed the obvious...
sudo -u central-tz-user (start elog)
gary |
Re: Different logbook files when running elogd as admin or normal user, posted by Stefan Ritt on Thu Jul 21 08:08:07 2016
|
I don't know why elogd uses different logbook directories depending on the user. Maybe you start it in different directories, or one user cannot
read the config file and falls back to some default. Anyhow, you can start elogd interactively wit the -v flag which tells you which logbook files are
parsed. There are no cache files or similar, everything is stored in Yymmdda.log files, you just have to search for them. |
Re: Different logbook files when running elogd as admin or normal user, posted by Antonio Bulgheroni on Thu Jul 21 09:37:47 2016
|
So I found the my log files, but this issue should probably be documented.
When running as admin my logbook files are where they should (C:\Program Files (x86)\ELOG\logbooks)
When running as local user (with no admin rights), elogd has no writing access to the logbooks directory. So it falls back to use C:\Users\[MyUserName]\AppData\Local\VirtualStore\Program |