Reputation
Top tag
Next privilege 125 Rep.
Vote down
Badges
5
Newest
 Student
Impact
~133 people reached

  • 0 posts edited
  • 0 helpful flags
  • 6 votes cast
Dec
19
awarded  Student
Dec
19
accepted Is it safe for different nginx servers to share logs?
Dec
19
comment Is it safe for different nginx servers to share logs?
I think I know what you mean here. The whole thing is complicated by the fact that one nginx instance may have multiple processes. But from your answer and comments above it looks nginx takes care of logging from different processes as long as they belong to the same nginx instance.
Dec
17
comment Is it safe for different nginx servers to share logs?
@AlexeyTen Depending on configuration it can be one nginx master process with several worker processes and I think the log is written by the worker processes? If so then why it isn't possible for concurrent logging from different worker processes to conflict with each other? Do these worker processes use any forms of synchronization?
Dec
17
comment Is it safe for different nginx servers to share logs?
@MichaelHampton Hi what do you mean by this? They listen on different ports with different schemes and can possibly serve different contents, use different authentication, etc.
Dec
17
awarded  Editor
Dec
17
revised Is it safe for different nginx servers to share logs?
added 214 characters in body
Dec
17
asked Is it safe for different nginx servers to share logs?
Nov
22
awarded  Scholar
Nov
22
accepted Why dir contents get deleted with chattr +a?
Nov
22
comment Why dir contents get deleted with chattr +a?
That thread is interesting. I guess I have to use a wrapper but the world is probably better if we don't need two processes for every safe rm.
Nov
22
comment Why dir contents get deleted with chattr +a?
I thought I could get some light shed upon by more details of rm and chattr. From your answer it turns out that chattr doesn't seem to be the correct path towards the solution. Actually the solution only requires a tiny check in rm preorder traversal. But it's a core util and I'm wondering about any implications given by its change.
Nov
22
comment Why dir contents get deleted with chattr +a?
You can answer no when rm gives you the notice so that you stay safe. It doesn't give me a notice in this case. In short, I want to prevent a mis-deletion. Details are put as a comment to another answer.
Nov
22
comment Why dir contents get deleted with chattr +a?
Thank you and I think most of the stuff here are good and in-point. But actually I want to be able to freely add/modify/delete files in base. What I want to avoid is a recursive deletion of base by mistake. Setting base as write-protected lets rm -r base give a notice. That's good but also means I cannot add/modify/delete files in base. Setting base with chattr +i has a similar effect. Setting base with chattr +a gives more freedom but rm regretfully doesn't care about this option until the last step.
Nov
22
comment Why dir contents get deleted with chattr +a?
Remember that rm -r asks you whether to descend a into write-protected directory? Nice. I expected that it would notice base is deletion-protected in its preorder traversal and give a notice. Then I looked at its source code and found it's not the case. I cried.
Nov
21
asked Why dir contents get deleted with chattr +a?
Sep
24
awarded  Autobiographer
Nov
14
awarded  Supporter