-
Notifications
You must be signed in to change notification settings - Fork 16
permission issues when writing to logs #163
Comments
Hi @VijayalakshmiVJ any updates on this? |
Hey Naved,
I didn't realize I had this issue too. I seem to have missed reading this
mail. I apologize! Iam uploading the other issue for review today. I have a
big project submission this Sunday. I'll get cracking at this issue on
Sunday after that and ensure we have a solution latest by Monday/Tuesday. I
apologise again..:(
Regards,
VJ
…On Fri, Apr 13, 2018, 10:55 AM Naved Ansari ***@***.***> wrote:
Hi @VijayalakshmiVJ <https://github.com/VijayalakshmiVJ> any updates on
this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#163 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AgT5CFt-mBn_JO_-QISb96uqsFd4rIkEks5toLx4gaJpZM4S_Ks_>
.
|
I debugged the issue of file rollover as mentioned,
I know its not the best way to go about it but it does the work. Regards, |
I think the best solution is to actually separate the client and the server, and then the |
As bmi server runs as root for now, as a quick fix we can force it to set permissions to the log files upon create/rollover. |
We open the permissions of
/var/log/bmi/ims.log
so non-root users can also run bmi commands. But quite often, the permissions change and people are unable to run bmi commands.@VijayalakshmiVJ
The text was updated successfully, but these errors were encountered: