Open
Conversation
- **Auto Restart Service**: - Allows users to configure automatic restarts for the Marzban service. - Provides options to set the restart time (hour and minute), remove the configuration, or exit the menu. - Validates user inputs for hour (0-23) and minute (0-59). - Updates the system's crontab with the restart schedule and ensures proper cleanup of old entries. - Automatically restarts the cron service to apply changes.
parsa-fathi
changed the title
parsa-fathi
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Auto Restart Service for Marzban
This PR introduces an automated restart feature for the Marzban service, designed to improve performance and memory management.
Key Changes:
Why This Matters:
Based on observed behavior, regular restarts of the Marzban container significantly reduce RAM usage over time, preventing memory leaks and maintaining stable performance. This is particularly useful for long-running instances where resource accumulation can degrade service reliability.