14.10.2020 15:23, Thomas HUMMEL пишет:
>
>
> On 14/10/2020 13:24, Andrei Borzenkov wrote:
>> On Wed, Oct 14, 2020 at 11:42 AM Thomas HUMMEL
>> wrote:
>>>
>>> Hello,
>>>
>>> thanks for your answer. It's getting clearer.
>>>
>>> Still : why would the user crond runs on behalf of needs to be
Hi Michal,
Thanks a lot for the information. This is helpful :)
On Wed, Oct 14, 2020 at 4:55 PM Michal Sekletar wrote:
> On Wed, Oct 14, 2020 at 11:21 AM Srijan Sivakumar
> wrote:
>
>> Hello there SMEs,
>>
>> I'm contributing to glusterfs project and found the service to be in the
>> state of
On 14/10/2020 13:24, Andrei Borzenkov wrote:
On Wed, Oct 14, 2020 at 11:42 AM Thomas HUMMEL wrote:
Hello,
thanks for your answer. It's getting clearer.
Still : why would the user crond runs on behalf of needs to be allowed
in access.conf to access the systemd-user service ?
My
On Wed, Oct 14, 2020 at 11:21 AM Srijan Sivakumar
wrote:
> Hello there SMEs,
>
> I'm contributing to glusterfs project and found the service to be in the
> state of
> *Active: active (running) (thawing) *sometimes.
>
> Now, I tried looking up what is the thawing state but couldn't get
> anything
On Wed, Oct 14, 2020 at 11:42 AM Thomas HUMMEL wrote:
>
> Hello,
>
> thanks for your answer. It's getting clearer.
>
> Still : why would the user crond runs on behalf of needs to be allowed
> in access.conf to access the systemd-user service ?
> My understanding is that the user@.service creation
Hello there SMEs,
I'm contributing to glusterfs project and found the service to be in the
state of
*Active: active (running) (thawing) *sometimes.
Now, I tried looking up what is the thawing state but couldn't get anything
concrete on it. Wondering if I could get some help from the actual devs
Hello,
thanks for your answer. It's getting clearer.
Still : why would the user crond runs on behalf of needs to be allowed
in access.conf to access the systemd-user service ?
My understanding is that the user@.service creation needs this
service type (or just the systemd --user creation ?)
