Status of sysstat.service showing active(exited)

up vote
0
down vote

favorite

When I see status of sysstat is see the following,

● sysstat.service - Resets System Activity Logs
Loaded: loaded (/usr/lib/systemd/system/sysstat.service; enabled; 
vendor preset: enabled)
Active: active (exited) since Wed 2018-11-28 11:46:45 EST; 4s ago
Process: 4159 ExecStart=/usr/lib64/sa/sa1 --boot (code=exited, 
status=0/SUCCESS)
Main PID: 4159 (code=exited, status=0/SUCCESS)

Nov 28 11:46:45 localhost systemd[1]: Starting Resets System 
Activity Logs...
Nov 28 11:46:45 localhost systemd[1]: Started Resets System 
Activity Logs.

Also couldn’t find any pid specified above.

Question is, why this happens?

edited Nov 28 at 20:32

asked Nov 28 at 16:54

muhammad

526514

Deleted assumption as wrong assumption is pointless.
– muhammad
Nov 28 at 20:32

Oneshot run, after which the regular performance capture is via cron, e.g. /etc/cron.d/sysstat
– steve
Nov 28 at 22:32

add a comment |

up vote
0
down vote

favorite

When I see status of sysstat is see the following,

● sysstat.service - Resets System Activity Logs
Loaded: loaded (/usr/lib/systemd/system/sysstat.service; enabled; 
vendor preset: enabled)
Active: active (exited) since Wed 2018-11-28 11:46:45 EST; 4s ago
Process: 4159 ExecStart=/usr/lib64/sa/sa1 --boot (code=exited, 
status=0/SUCCESS)
Main PID: 4159 (code=exited, status=0/SUCCESS)

Nov 28 11:46:45 localhost systemd[1]: Starting Resets System 
Activity Logs...
Nov 28 11:46:45 localhost systemd[1]: Started Resets System 
Activity Logs.

Also couldn’t find any pid specified above.

Question is, why this happens?

edited Nov 28 at 20:32

asked Nov 28 at 16:54

muhammad

526514

Deleted assumption as wrong assumption is pointless.
– muhammad
Nov 28 at 20:32

Oneshot run, after which the regular performance capture is via cron, e.g. /etc/cron.d/sysstat
– steve
Nov 28 at 22:32

add a comment |

up vote
0
down vote

favorite

When I see status of sysstat is see the following,

● sysstat.service - Resets System Activity Logs
Loaded: loaded (/usr/lib/systemd/system/sysstat.service; enabled; 
vendor preset: enabled)
Active: active (exited) since Wed 2018-11-28 11:46:45 EST; 4s ago
Process: 4159 ExecStart=/usr/lib64/sa/sa1 --boot (code=exited, 
status=0/SUCCESS)
Main PID: 4159 (code=exited, status=0/SUCCESS)

Nov 28 11:46:45 localhost systemd[1]: Starting Resets System 
Activity Logs...
Nov 28 11:46:45 localhost systemd[1]: Started Resets System 
Activity Logs.

Also couldn’t find any pid specified above.

Question is, why this happens?

edited Nov 28 at 20:32

asked Nov 28 at 16:54

muhammad

526514

When I see status of sysstat is see the following,

● sysstat.service - Resets System Activity Logs
Loaded: loaded (/usr/lib/systemd/system/sysstat.service; enabled; 
vendor preset: enabled)
Active: active (exited) since Wed 2018-11-28 11:46:45 EST; 4s ago
Process: 4159 ExecStart=/usr/lib64/sa/sa1 --boot (code=exited, 
status=0/SUCCESS)
Main PID: 4159 (code=exited, status=0/SUCCESS)

Nov 28 11:46:45 localhost systemd[1]: Starting Resets System 
Activity Logs...
Nov 28 11:46:45 localhost systemd[1]: Started Resets System 
Activity Logs.

Also couldn’t find any pid specified above.

Question is, why this happens?

systemd init sysvinit

edited Nov 28 at 20:32

asked Nov 28 at 16:54

muhammad

526514

edited Nov 28 at 20:32

asked Nov 28 at 16:54

muhammad

526514

edited Nov 28 at 20:32

asked Nov 28 at 16:54

muhammad

526514

asked Nov 28 at 16:54

muhammad

526514

asked Nov 28 at 16:54

muhammad

526514

Deleted assumption as wrong assumption is pointless.
– muhammad
Nov 28 at 20:32

Oneshot run, after which the regular performance capture is via cron, e.g. /etc/cron.d/sysstat
– steve
Nov 28 at 22:32

add a comment |

Deleted assumption as wrong assumption is pointless.
– muhammad
Nov 28 at 20:32

Oneshot run, after which the regular performance capture is via cron, e.g. /etc/cron.d/sysstat
– steve
Nov 28 at 22:32

Deleted assumption as wrong assumption is pointless.
– muhammad
Nov 28 at 20:32

Oneshot run, after which the regular performance capture is via cron, e.g. /etc/cron.d/sysstat
– steve
Nov 28 at 22:32

add a comment |

1 Answer
1

active

oldest

votes

up vote
2
down vote

accepted

Your assumption is wrong. sysstat is a "oneshot" type service, meaning it executes once and then it exits:

$ cat /usr/lib/systemd/system/sysstat.service

#... elided ...

[Service]
Type=oneshot
RemainAfterExit=yes
User=root
ExecStart=/usr/lib64/sa/sa1 --boot

#... elided ...

... which explains why there is no PID -- because there is no process any more.

The documentation for systemd services says, in part:

Behavior of oneshot is similar to simple; however, it is expected that the process has to exit before systemd starts follow-up units.

answered Nov 28 at 17:22

Jeff Schaller

37.2k1052121

add a comment |

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',
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
);

);

draft saved

draft discarded

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f484720%2fstatus-of-sysstat-service-showing-activeexited%23new-answer', 'question_page');

);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

up vote
2
down vote

accepted

Your assumption is wrong. sysstat is a "oneshot" type service, meaning it executes once and then it exits:

$ cat /usr/lib/systemd/system/sysstat.service

#... elided ...

[Service]
Type=oneshot
RemainAfterExit=yes
User=root
ExecStart=/usr/lib64/sa/sa1 --boot

#... elided ...

... which explains why there is no PID -- because there is no process any more.

The documentation for systemd services says, in part:

Behavior of oneshot is similar to simple; however, it is expected that the process has to exit before systemd starts follow-up units.

answered Nov 28 at 17:22

Jeff Schaller

37.2k1052121

add a comment |

up vote
2
down vote

accepted

Your assumption is wrong. sysstat is a "oneshot" type service, meaning it executes once and then it exits:

$ cat /usr/lib/systemd/system/sysstat.service

#... elided ...

[Service]
Type=oneshot
RemainAfterExit=yes
User=root
ExecStart=/usr/lib64/sa/sa1 --boot

#... elided ...

... which explains why there is no PID -- because there is no process any more.

The documentation for systemd services says, in part:

Behavior of oneshot is similar to simple; however, it is expected that the process has to exit before systemd starts follow-up units.

answered Nov 28 at 17:22

Jeff Schaller

37.2k1052121

add a comment |

up vote
2
down vote

accepted

Your assumption is wrong. sysstat is a "oneshot" type service, meaning it executes once and then it exits:

$ cat /usr/lib/systemd/system/sysstat.service

#... elided ...

[Service]
Type=oneshot
RemainAfterExit=yes
User=root
ExecStart=/usr/lib64/sa/sa1 --boot

#... elided ...

... which explains why there is no PID -- because there is no process any more.

The documentation for systemd services says, in part:

Behavior of oneshot is similar to simple; however, it is expected that the process has to exit before systemd starts follow-up units.

answered Nov 28 at 17:22

Jeff Schaller

37.2k1052121

Your assumption is wrong. sysstat is a "oneshot" type service, meaning it executes once and then it exits:

$ cat /usr/lib/systemd/system/sysstat.service

#... elided ...

[Service]
Type=oneshot
RemainAfterExit=yes
User=root
ExecStart=/usr/lib64/sa/sa1 --boot

#... elided ...

... which explains why there is no PID -- because there is no process any more.

The documentation for systemd services says, in part:

Behavior of oneshot is similar to simple; however, it is expected that the process has to exit before systemd starts follow-up units.

answered Nov 28 at 17:22

Jeff Schaller

37.2k1052121

answered Nov 28 at 17:22

Jeff Schaller

37.2k1052121

answered Nov 28 at 17:22

Jeff Schaller

37.2k1052121

answered Nov 28 at 17:22

Jeff Schaller

37.2k1052121

add a comment |

draft saved

draft discarded

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.

Some of your past answers have not been well-received, and you're in danger of being blocked from answering.

Please pay close attention to the following guidance:

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.

draft saved

draft discarded

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

搜尋此網誌

mjhjmtu