Why I don't have a /usr/lib/systemd/system folder?
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I am trying to use systemd
for the first time after giving up on supervisord
.
Following this documentation for airflow here, my understanding is that I need to move the .service
files to /usr/lib/systemd/system
, however such directory does not exist in my system (Ubuntu 18.04.2 LTS
). Instead I have /usr/lib/systemd/system-environment-generators/
.
Should I create this system
folder myself or have I made a mistake somewhere which I need to fix otherwise?
systemd services
add a comment |
I am trying to use systemd
for the first time after giving up on supervisord
.
Following this documentation for airflow here, my understanding is that I need to move the .service
files to /usr/lib/systemd/system
, however such directory does not exist in my system (Ubuntu 18.04.2 LTS
). Instead I have /usr/lib/systemd/system-environment-generators/
.
Should I create this system
folder myself or have I made a mistake somewhere which I need to fix otherwise?
systemd services
add a comment |
I am trying to use systemd
for the first time after giving up on supervisord
.
Following this documentation for airflow here, my understanding is that I need to move the .service
files to /usr/lib/systemd/system
, however such directory does not exist in my system (Ubuntu 18.04.2 LTS
). Instead I have /usr/lib/systemd/system-environment-generators/
.
Should I create this system
folder myself or have I made a mistake somewhere which I need to fix otherwise?
systemd services
I am trying to use systemd
for the first time after giving up on supervisord
.
Following this documentation for airflow here, my understanding is that I need to move the .service
files to /usr/lib/systemd/system
, however such directory does not exist in my system (Ubuntu 18.04.2 LTS
). Instead I have /usr/lib/systemd/system-environment-generators/
.
Should I create this system
folder myself or have I made a mistake somewhere which I need to fix otherwise?
systemd services
systemd services
asked Mar 17 at 16:45
NewskoolerNewskooler
1012
1012
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
In Ubuntu the folder that holds the .service
files is /lib/systemd/system. This folder is intended to be used by .deb
packages.
Best option to place systemd
related files which are not provided by a Debian package would be /etc/systemd/system.
So should I create this folder myself or it should already exist and I have messed something up?
– Newskooler
Mar 17 at 17:00
/lib/systemd/system and /etc/systemd/system should exist already.
– Thomas
Mar 17 at 18:26
They both do, however/usr/lib/systemd/system
does not (which is my question). Why is that?
– Newskooler
Mar 17 at 18:28
1
Because in Ubuntu that path is /lib/systemd/system and not /usr/lib/systemd/system. No need to create any folder.
– Thomas
Mar 17 at 18:30
2
Add your service to /etc/systemd/system. That path is intended to placesystemd
files that are not provided by Debian packages. I cannot answer why Ubuntu did choose that path layout, but you also my want to readman systemd
.
– Thomas
Mar 17 at 18:35
|
show 3 more comments
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f506839%2fwhy-i-dont-have-a-usr-lib-systemd-system-folder%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
In Ubuntu the folder that holds the .service
files is /lib/systemd/system. This folder is intended to be used by .deb
packages.
Best option to place systemd
related files which are not provided by a Debian package would be /etc/systemd/system.
So should I create this folder myself or it should already exist and I have messed something up?
– Newskooler
Mar 17 at 17:00
/lib/systemd/system and /etc/systemd/system should exist already.
– Thomas
Mar 17 at 18:26
They both do, however/usr/lib/systemd/system
does not (which is my question). Why is that?
– Newskooler
Mar 17 at 18:28
1
Because in Ubuntu that path is /lib/systemd/system and not /usr/lib/systemd/system. No need to create any folder.
– Thomas
Mar 17 at 18:30
2
Add your service to /etc/systemd/system. That path is intended to placesystemd
files that are not provided by Debian packages. I cannot answer why Ubuntu did choose that path layout, but you also my want to readman systemd
.
– Thomas
Mar 17 at 18:35
|
show 3 more comments
In Ubuntu the folder that holds the .service
files is /lib/systemd/system. This folder is intended to be used by .deb
packages.
Best option to place systemd
related files which are not provided by a Debian package would be /etc/systemd/system.
So should I create this folder myself or it should already exist and I have messed something up?
– Newskooler
Mar 17 at 17:00
/lib/systemd/system and /etc/systemd/system should exist already.
– Thomas
Mar 17 at 18:26
They both do, however/usr/lib/systemd/system
does not (which is my question). Why is that?
– Newskooler
Mar 17 at 18:28
1
Because in Ubuntu that path is /lib/systemd/system and not /usr/lib/systemd/system. No need to create any folder.
– Thomas
Mar 17 at 18:30
2
Add your service to /etc/systemd/system. That path is intended to placesystemd
files that are not provided by Debian packages. I cannot answer why Ubuntu did choose that path layout, but you also my want to readman systemd
.
– Thomas
Mar 17 at 18:35
|
show 3 more comments
In Ubuntu the folder that holds the .service
files is /lib/systemd/system. This folder is intended to be used by .deb
packages.
Best option to place systemd
related files which are not provided by a Debian package would be /etc/systemd/system.
In Ubuntu the folder that holds the .service
files is /lib/systemd/system. This folder is intended to be used by .deb
packages.
Best option to place systemd
related files which are not provided by a Debian package would be /etc/systemd/system.
answered Mar 17 at 16:55
ThomasThomas
4,14361430
4,14361430
So should I create this folder myself or it should already exist and I have messed something up?
– Newskooler
Mar 17 at 17:00
/lib/systemd/system and /etc/systemd/system should exist already.
– Thomas
Mar 17 at 18:26
They both do, however/usr/lib/systemd/system
does not (which is my question). Why is that?
– Newskooler
Mar 17 at 18:28
1
Because in Ubuntu that path is /lib/systemd/system and not /usr/lib/systemd/system. No need to create any folder.
– Thomas
Mar 17 at 18:30
2
Add your service to /etc/systemd/system. That path is intended to placesystemd
files that are not provided by Debian packages. I cannot answer why Ubuntu did choose that path layout, but you also my want to readman systemd
.
– Thomas
Mar 17 at 18:35
|
show 3 more comments
So should I create this folder myself or it should already exist and I have messed something up?
– Newskooler
Mar 17 at 17:00
/lib/systemd/system and /etc/systemd/system should exist already.
– Thomas
Mar 17 at 18:26
They both do, however/usr/lib/systemd/system
does not (which is my question). Why is that?
– Newskooler
Mar 17 at 18:28
1
Because in Ubuntu that path is /lib/systemd/system and not /usr/lib/systemd/system. No need to create any folder.
– Thomas
Mar 17 at 18:30
2
Add your service to /etc/systemd/system. That path is intended to placesystemd
files that are not provided by Debian packages. I cannot answer why Ubuntu did choose that path layout, but you also my want to readman systemd
.
– Thomas
Mar 17 at 18:35
So should I create this folder myself or it should already exist and I have messed something up?
– Newskooler
Mar 17 at 17:00
So should I create this folder myself or it should already exist and I have messed something up?
– Newskooler
Mar 17 at 17:00
/lib/systemd/system and /etc/systemd/system should exist already.
– Thomas
Mar 17 at 18:26
/lib/systemd/system and /etc/systemd/system should exist already.
– Thomas
Mar 17 at 18:26
They both do, however
/usr/lib/systemd/system
does not (which is my question). Why is that?– Newskooler
Mar 17 at 18:28
They both do, however
/usr/lib/systemd/system
does not (which is my question). Why is that?– Newskooler
Mar 17 at 18:28
1
1
Because in Ubuntu that path is /lib/systemd/system and not /usr/lib/systemd/system. No need to create any folder.
– Thomas
Mar 17 at 18:30
Because in Ubuntu that path is /lib/systemd/system and not /usr/lib/systemd/system. No need to create any folder.
– Thomas
Mar 17 at 18:30
2
2
Add your service to /etc/systemd/system. That path is intended to place
systemd
files that are not provided by Debian packages. I cannot answer why Ubuntu did choose that path layout, but you also my want to read man systemd
.– Thomas
Mar 17 at 18:35
Add your service to /etc/systemd/system. That path is intended to place
systemd
files that are not provided by Debian packages. I cannot answer why Ubuntu did choose that path layout, but you also my want to read man systemd
.– Thomas
Mar 17 at 18:35
|
show 3 more comments
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f506839%2fwhy-i-dont-have-a-usr-lib-systemd-system-folder%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown