# RHN check in time

**URL:** <https://forums.suse.com/t/rhn-check-in-time/33463>\
**Category:** SUSE Multi Linux Manager\
**Created:** [January 31, 2019, 8:32pm UTC](https://forums.suse.com/t/rhn-check-in-time/33463 "2019-01-31T20:32:33Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![cisaksen](https://avatars.discourse-cdn.com/v4/letter/c/49beb7/32.png) [@cisaksen](https://forums.suse.com/u/cisaksen)\
**Post date:** [January 31, 2019, 8:32pm UTC](https://forums.suse.com/t/rhn-check-in-time/33463/1 "2019-01-31T20:32:33Z")

</div>

We are running suma 3.2 and sles & sled 12 & 15. The file /etc/sysconfig/rhn/rhnsd has the rhn checkin time set to \<INTERVAL=240 default\> . We change it to 60 minutes. But every so often we notice that something is changing it back to 240 and creating the rpmsave file that contains the 60.

Is there anything we can do to stop this ? It’s getting to be a pain to have to keep changing it back to 60. We want our server to check in every hour for schedule tasks. Whether they be patches, remote commands or reboots. 4 hours is too big a window.

Thanks

---

<div class="post-metadata">

**Author:** ![kwk](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/kwk/32/11997_2.png) [@kwk](https://forums.suse.com/u/kwk)\
**Post date:** [February 1, 2019, 9:50am UTC](https://forums.suse.com/t/rhn-check-in-time/33463/2 "2019-02-01T09:50:21Z")

</div>

[QUOTE=cisaksen;56432]We are running suma 3.2 and sles & sled 12 & 15. The file /etc/sysconfig/rhn/rhnsd has the rhn checkin time set to \<INTERVAL=240 default\> . We change it to 60 minutes. But every so often we notice that something is changing it back to 240 and creating the rpmsave file that contains the 60.  
[/QUOTE]  
This is a packaging bug and would qualify for a support request.

> [@cisaksen;56432](#):
>
> Is there anything we can do to stop this ? It’s getting to be a pain to have to keep changing it back to 60. We want our server to check in every hour for schedule tasks. Whether they be patches, remote commands or reboots. 4 hours is too big a window.

You can either use ‘osad’ or switch to Salt.

---

<div class="post-metadata">

**Author:** ![barryrailton](https://avatars.discourse-cdn.com/v4/letter/b/439d5e/32.png) [@barryrailton](https://forums.suse.com/u/barryrailton)\
**Post date:** [February 6, 2019, 10:56pm UTC](https://forums.suse.com/t/rhn-check-in-time/33463/3 "2019-02-06T22:56:13Z")

</div>

Don’t have a solution but as a workaround you could try making the file non-writable with something like “chmod -w /etc/sysconfig/rhn/rhnsd”.

---

<div class="post-metadata">

**Author:** ![David1](https://avatars.discourse-cdn.com/v4/letter/d/73ab20/32.png) [@David1](https://forums.suse.com/u/David1)\
**Post date:** [August 31, 2020, 9:51pm UTC](https://forums.suse.com/t/rhn-check-in-time/33463/4 "2020-08-31T21:51:21Z")

</div>

I wouldn’t do that **chmod** - could cause problems for **zypper** / **rpm** (or just plain not work), and it’s a crude way to approach this need.  
Of course, the new package (in SLES v15, anyway) is **mgr-demon** , and that config file now has no effect. Instead, the scheduling is handled _via_ a **systemd** Timer.  
I don’t like the default 4 hour timing, either. So I wrote an RPM **mgr-daemon-company** , that deploys a new Timer file. Since the original Timer file is owned by the **mgr-daemon** package, my RPM can’t deploy the same file, so my file has a different name. Using the **Triggers** functionality of RPM, a _sym-link_ is created and maintained from the original filename to my file. So if an updated **mgr-daemon** RPM is installed, the **Trigger** function will make sure my version of the Timer file gets linked.