Uploaded image for project: 'Product Technical Learning'
  1. Product Technical Learning
  2. PTL-7766

RH415-18: Instructors: be aware of systemd timers and sockets

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Not a Bug
    • Icon: Minor Minor
    • RH415 - RHEL7.5 1 20180830
    • RH415
    • None
    • en-US (English)

      URL:
      Reporter RHNID:
      Section: -
      Language: en-US (English)
      Workaround:

      Description: This Instructor Hint is just a general comment to instructors that a number of systems in this course use systemd features you may be less familiar with. 

      1) The tangd service is started on-demand by systemd acting as a superserver when clients connect to port 80/TCP.  Systemd is acting on behalf of tangd much like the old xinetd service did for its services.  This is implemented through systemd socket files. This has led to some interesting confusion in labs, see RH415-7.

      2) The insights-client command is no longer run as a Cron job on clients, but as a systemd insights-client.timer unit which implicitly calls the insights-client.service unit.  If you show this to folks, note that one advantage is that it runs daily + a random offset of 0-4 hours as the note in the book mentions.  So if you go looking for the automatic run in Cron and can't find it, you're looking in the wrong place.   

      systemd.socket(5) and systemd.timer(5) man pages have some useful background if you want details on how these functions work, but that's more than is needed for this course.

            rht-sbonnevi Steven Bonneville
            rht-sbonnevi Steven Bonneville
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: