forked from rockstor/rockstor-core
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[openSUSE] adapt to shellinabox package differences rockstor#2006
A recently available OBS shells.repo hosted shellinabox package had breaking differences from our prior epel CentOS pacakge. The following code changes were made to support both packages concurrently: - Move to re-configure service on every service enable and black format the associated file: shellinaboxd_service.py, with minor refactoring. - Remove build time 'initial' config file instantiation, along with the prior listed change this establishes a single point, within code, where our desired configuration is written. This also ensures we overwrite package default config prior to initial service start. - Establish distro specific configuration options: the proposed openSUSE shells repo package has a different certificates location. - Go with both package defaults re user/group for running the shellinabox deamon. - Account for differing default configuration file names. - Account for differing systemd service file names by normalising on our existing 'shellinaboxd' and establishing this if not found during the initrock.py script run by rockstor-pre.service. - Improve comments in prep_db.py pertaining to shellinaboxd + black format. - Remove unused status() and associated import from shell.py. - Pass systemd service name to shell.py to reduce hardcoded instances. - Move shell.py to string.format + black formatting. - Fix existing bug where shellinabox config file options had no closing quote and carriage return.
- Loading branch information
Showing
7 changed files
with
112 additions
and
79 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file was deleted.
Oops, something went wrong.
This file contains 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
This file contains 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
This file contains 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
This file contains 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