wluke
66 Posts
Quote from wluke on March 15, 2023, 2:59 pm
Yea, I know when starting it there's a delay, so I waited a few minutes, but it didn't seem to stop it.
Could it have been because ctdb was previously started manually perhaps?
Yea, I know when starting it there's a delay, so I waited a few minutes, but it didn't seem to stop it.
Could it have been because ctdb was previously started manually perhaps?
wluke
66 Posts
Quote from wluke on March 15, 2023, 4:00 pm
I just tried there, and waited 3 minutes and checked and ctdb was indeed stopped.
I also tried starting ctdb manually, and then once it was started, starting petasan-cifs, and then stopping petasan-cifs again. Again, ctdb was correctly stopped within a few seconds.
So, nope, I can't reproduce it. Maybe I didn't wait long enough last time, or it was delayed starting/stopping due to the large sizes in the volatile folder
I just tried there, and waited 3 minutes and checked and ctdb was indeed stopped.
I also tried starting ctdb manually, and then once it was started, starting petasan-cifs, and then stopping petasan-cifs again. Again, ctdb was correctly stopped within a few seconds.
So, nope, I can't reproduce it. Maybe I didn't wait long enough last time, or it was delayed starting/stopping due to the large sizes in the volatile folder
