starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-14 14:23:32 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

systemctl enable --now #7187

New Issue
Closed
opened 2025-12-29 20:20:17 +01:00 by adam · 3 comments
adam commented 2025-12-29 20:20:17 +01:00
Owner
Copy Link

Originally created by @PenelopeFudd on GitHub (Nov 1, 2022).

Change Type

Addition

Area

Installation/upgrade

Proposed Changes

On https://docs.netbox.dev/en/stable/installation/4-gunicorn/ , the commands

sudo systemctl start netbox netbox-rq
sudo systemctl enable netbox netbox-rq

Could be simplified to

sudo systemctl enable --now netbox netbox-rq
Originally created by @PenelopeFudd on GitHub (Nov 1, 2022). ### Change Type Addition ### Area Installation/upgrade ### Proposed Changes On https://docs.netbox.dev/en/stable/installation/4-gunicorn/ , the commands ``` sudo systemctl start netbox netbox-rq sudo systemctl enable netbox netbox-rq ``` Could be simplified to ``` sudo systemctl enable --now netbox netbox-rq ```
adam added the type: documentation label 2025-12-29 20:20:17 +01:00
adam closed this issue 2025-12-29 20:20:17 +01:00
adam commented 2025-12-29 20:20:18 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Nov 2, 2022):

Not every version of Linux supports the now flag, notibly a large number of CentOS 7 boxes (it is EoL I believe but it is still very much out there).

I think we can add it as a option, but I think preserving the current functionality makes more sense currently.

Important caveat with this:

The start or stop operation is only carried out when the respective enable or disable operation has been successful.

@DanSheps commented on GitHub (Nov 2, 2022): Not every version of Linux supports the now flag, notibly a large number of CentOS 7 boxes (it is EoL I believe but it is still very much out there). I think we can add it as a option, but I think preserving the current functionality makes more sense currently. Important caveat with this: > The start or stop operation is only carried out when the respective enable or disable operation has been successful.
adam commented 2025-12-29 20:20:18 +01:00
Author
Owner
Copy Link

@PenelopeFudd commented on GitHub (Nov 2, 2022):

Huh. TIL! :-)

I'm having difficulty thinking of a situation where it's not possible to enable/disable yet it is possible to start/stop. Would that be if it's already been enabled/disabled (e.g. "you can't disable that, it's already disabled"), or maybe if the service file has been deleted? In those cases, I'm not sure how systemd would know how to start or stop the service, the required definitions would have been deleted from memory. Or at least, that's how I'm imagining it, I haven't tested it.

The more I read the installation instructions, the more I like them; they're solid. In fact, they're good enough that they could be turned into an interactive shell script without much difficulty. Initially, anyway. :-)

@PenelopeFudd commented on GitHub (Nov 2, 2022): Huh. TIL! :-) I'm having difficulty thinking of a situation where it's not possible to enable/disable yet it is possible to start/stop. Would that be if it's already been enabled/disabled (e.g. "you can't disable that, it's already disabled"), or maybe if the service file has been deleted? In those cases, I'm not sure how systemd would know how to start or stop the service, the required definitions would have been deleted from memory. Or at least, that's how I'm imagining it, I haven't tested it. The more I read the installation instructions, the more I like them; they're solid. In fact, they're good enough that they could be turned into an interactive shell script without much difficulty. Initially, anyway. :-)
adam commented 2025-12-29 20:20:19 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 13, 2022):

Thanks for the suggestion, but I'm going to close this as it doesn't seem to be a necessary change, and including it apparently might cause problems for some users.

@jeremystretch commented on GitHub (Dec 13, 2022): Thanks for the suggestion, but I'm going to close this as it doesn't seem to be a necessary change, and including it apparently might cause problems for some users.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label type: documentation
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7187
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?