You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I vote to remove that function because there is no appropriated use case for it. It simply execute sync on the shell to make sure the file system is "synced" (flushed).
Checking via grep it seems to be used only in tools.shutdown():
The shutdown command on shell itself is designed to make sure the shutdown is clean and healthy. This includes a synced/valid state of the file system.
Don't forget to remove the unit tests, too.
The text was updated successfully, but these errors were encountered:
Was used in shutdown() only. Shutodwn cause an unmount which itself cause synfs on OS level. No need for BIT to do it explicit. Behavior of BIT do not change.
Additionally minor PEP8 improvements.
Close#1685
dw4102
pushed a commit
to dw4102/backintime
that referenced
this issue
May 4, 2024
Was used in shutdown() only. Shutodwn cause an unmount which itself cause synfs on OS level. No need for BIT to do it explicit. Behavior of BIT do not change.
Additionally minor PEP8 improvements.
Closebit-team#1685
Finish rpmbuild & specfile creation
feat: RPM package building support
backintime/common/tools.py
Lines 1539 to 1547 in d33f35e
I vote to remove that function because there is no appropriated use case for it. It simply execute
sync
on the shell to make sure the file system is "synced" (flushed).Checking via grep it seems to be used only in
tools.shutdown()
:backintime/common/tools.py
Lines 2223 to 2241 in d33f35e
The
shutdown
command on shell itself is designed to make sure the shutdown is clean and healthy. This includes a synced/valid state of the file system.Don't forget to remove the unit tests, too.
The text was updated successfully, but these errors were encountered: