#96 F38: Shorter Shutdown Timer
Closed 2 years ago by pboy. Opened 2 years ago by pboy.

Related documentation and discussion

Topics to discuss

  1. Is there any advantage for Fedora Server, are there any disadvantages? Does it really make sense to treat servers and desktops the same?
    (see specifically Collin Walters)
  2. Existing timeout configuration of Server's core services
  3. Timeout configuration of other Server distributions: RHEL, CentOS, SuSE, Debian, Ubuntu
  4. Possible interdependency effect of a multitude of services terminated at the same time
  5. Can we test for possible disadvantages
  6. What exactly is the current Server configuration (there are some unclear findings).

Possible decision alternatives

  1. Follow Fedora's systemwide new default
  2. Follow Fedora's systemwide new default and add a step to the post-install Server documentation
  3. Overwrite with a more suitable default

See https://src.fedoraproject.org/rpms/fedora-release/pull-request/249 if the Server SIG wants to undo the change for their edition

@siosm Many thanks for the link. We are still discussing it. I read Collin Walters' comment in the FESCO thread, and he expressed my concerns very well and I had sympathized with his proposal. Did CoreOS already decide how to handle this? Last I read your IRC minutes it was still in discussion, if I remember correctly.

As of our IRC meeting 2023-02-15 we want to create a list of our core services in order to check their proper shutdown value status.

  • KVM/Libvirt VM's host
    • Status: timeout set to 'infinity' (nirik)
    • Details of configuration: ??
  • KVM/libvirt VM instances
    • Status: timeout set to 'infinity' (nirik)
    • Details of configuration: ??
  • Podman container host
    • Status: ??
    • Details of configuration: ??
  • Podman container instances
    • Status: ??
    • Details of configuration: ??
  • Systemd-nspawn container host
    • Status: ??
    • Details of configuration: ??
  • Systemd-nspawn container instances
    • Status: ??
    • Details of configuration: ??
  • Libvirt LXC container host
    • Status: ??
    • Details of configuration: ??
  • Libvirt LXC container instances
    • Status: ??
    • Details of configuration: ??
  • Domain Controller
    • Status: ??
    • Details of configuration: ??
  • IPA service
    • Status: set to 0 (old config for infinity) (nirik)
    • Details of configuration: ??
  • PostgreSQL database server
    • Status: set to infinity (nirik)
    • Details of configuration: ??
  • Samba file server
    • Status: no special settings (nirik)
    • Details of configuration: ??
  • NFS file server
    • Status: no special settings (nirik)
    • Details of configuration: ??
  • Apache Web server
    • Status: no special settings (nirik)
    • Details of configuration: ??
  • Web application service: Tomcat
    • Status: ??
    • Details of configuration: ??
  • Web application service: Wildfly
    • Status: ??
    • Details of configuration: ??
  • Postfix/Dovecot mail service
    • Status: no special shandling (nirik)
    • Details of configuration: ??
  • DHCP/PXE server
    • Status: ??
    • Details of configuration: ??
  • DNS resolving service
    • Status: ??
    • Details of configuration: ??
  • NTP/NTS time server
    • Status: ??
    • Details of configuration: ??

The CoreOS group has decided to revert the change thus the PR. If no-one speaks up from other groups then we will do that only for CoreOS.

Metadata Update from @pboy:
- Issue tagged with: meeting, pending activity

2 years ago

Metadata Update from @pboy:
- Issue status updated to: Closed (was: Open)

2 years ago

Metadata Update from @pboy:
- Issue untagged with: meeting

2 years ago

Log in to comment on this ticket.

Metadata