Bug 1111897 - transactional-update.service seems to run two instances of transactional-update
transactional-update.service seems to run two instances of transactional-update
Status: RESOLVED FIXED
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Kubic
Current
Other Other
: P5 - None : Normal (vote)
: ---
Assigned To: Ignaz Forster
E-mail List
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-10-15 16:12 UTC by Richard Brown
Modified: 2021-06-14 06:16 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Brown 2018-10-15 16:12:49 UTC
Steps to reproduce

systemctl start transactional-update.service

systemctl status transactional-update.service

Expected behaviour

1 process with the name transactional-update

Actual behaviour

2 processes with the name transactional-update

pstree -a seems to suggest that one of the processes is a child of the other, with that child spawning "tee -a /var/log/transactional-update.log", while the parent spawns "tee -a /var/log/transactional-update.log" and the appropriate "zypper" call