Menu

#44 config change

next
open
nobody
None
9
2023-03-04
2022-09-19
rno
No

if config file is modified with a text editor, or other independent ways,
and then next using/switching to worker, config is clicked,
the modif just made isn't detected ,

if changing things in the config with worker, then click save in the configuration window
a requester config file was modified after being loaded shows.

so whether I keep the earlier edited one or the recently modified one, some of the changes would be lost, to redo another time.

it's happening only if editing the config in worker directly next changing the file, since otherwise, next some unknown time, there's a config reload popup.

maybe a config file stat/mtime check could be done as soon as a click on config is made,
so the warning, and the option to reload, would be there earlier than the user changing anything in the config.

sometimes I'm changing text in the config files with programs as sed...
as program names mostly next upgrades or new install.

user could be avoiding redoing things with such a fix.

config changed with another worker instance
tested with 3.15.3 as described + config reload popup some time later
tested with 4.11.0 reload popup as soon as bringing focus to worker

config changed with a text editor, or some other program
tested with 3.15.3 as described + config reload popup some time later
tested with 4.11.0 as described + config reload popup some time later

Discussion


Log in to post a comment.

MongoDB Logo MongoDB