[opensuse] systemd restart
How does one restart systemd without rebooting the OS? I have some OSS machines that use Samba for AD integration. Whenever Samba is updated, libwinbind* all get updated. Prior to OSS 12.3, I could just restart services that used files that had been updated and everything was good. Now, however, systemd appears to use libwinbind* and I have no idea how to get systemd to use the new libwind. I cannot figure out how to restart systemd without a system reboot. Any help is appreciated. -- --Moby They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 15/06/13 20:20, Moby escribió:
How does one restart systemd without rebooting the OS?
the init system reloads its configuration with systemctl daemon-reload I have some OSS
machines that use Samba for AD integration. Whenever Samba is updated, libwinbind* all get updated. Prior to OSS 12.3, I could just restart services that used files that had been updated and everything was good. Now, however, systemd appears to use libwinbind* and I have no idea how to get systemd to use the new libwind. I cannot figure out how to restart systemd without a system reboot. Any help is appreciated.
systemd does not use libwinbind (or links to any samba component)...Care to explain your problem better ? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/15/2013 07:40 PM, Cristian Rodríguez wrote:
El 15/06/13 20:20, Moby escribió:
How does one restart systemd without rebooting the OS?
the init system reloads its configuration with systemctl daemon-reload
I have some OSS
machines that use Samba for AD integration. Whenever Samba is updated, libwinbind* all get updated. Prior to OSS 12.3, I could just restart services that used files that had been updated and everything was good. Now, however, systemd appears to use libwinbind* and I have no idea how to get systemd to use the new libwind. I cannot figure out how to restart systemd without a system reboot. Any help is appreciated.
systemd does not use libwinbind (or links to any samba component)...Care to explain your problem better ?
Thanks for the resopnse Cristina. systemd is using libnss_winbind.so.2 which is provided by samba-winbind. I did: zypper in --force samba-winbind zypper ps and I see: PID | PPID | UID | Login | Command | Service | Files -----+------+-----+------------+--------------+--------------+------------------ 1 | 0 | 0 | root | systemd | | /lib/libnss_win-> 504 | 1 | 103 | avahi | avahi-daemon | avahi-daemon | /lib/libnss_win-> 1433 | 1 | 0 | root | winbindd | winbind | /lib/libnss_win-> . . . Doing a systemctl daemon-reload still leaves systemd showing using libnss_winbind.so.2. -- --Moby They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 15/06/13 21:57, Moby escribió:
systemd is using libnss_winbind.so.2 which is provided by samba-winbind.
You are looking it from the wrong side/perspective, libnss_winbind is loaded by glibc, which all programs use, not just systemd. You are to reboot the system. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/15/2013 09:22 PM, Cristian Rodríguez wrote:
El 15/06/13 21:57, Moby escribió:
systemd is using libnss_winbind.so.2 which is provided by samba-winbind.
You are looking it from the wrong side/perspective, libnss_winbind is loaded by glibc, which all programs use, not just systemd.
You are to reboot the system.
Thanks Cristian. That would make sense that libnss_winbind is being used by glibc, since I have modified nsswitch.conf to get users and groups from the Windows domain. On systems that I have not upgraded to OSS 12.3 and that do not use systemd, I do not run into a situation where I have to reboot after a winbind update. Those systems do show a bunch of services using deleting files, but a restart on the services is all it takes. Those systems do show winbind components in use by any process that would force me to reboot. -- --Moby They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/15/2013 09:38 PM, Moby wrote:
On 06/15/2013 09:22 PM, Cristian Rodríguez wrote:
El 15/06/13 21:57, Moby escribió:
systemd is using libnss_winbind.so.2 which is provided by samba-winbind.
You are looking it from the wrong side/perspective, libnss_winbind is loaded by glibc, which all programs use, not just systemd.
You are to reboot the system.
Thanks Cristian. That would make sense that libnss_winbind is being used by glibc, since I have modified nsswitch.conf to get users and groups from the Windows domain. On systems that I have not upgraded to OSS 12.3 and that do not use systemd, I do not run into a situation where I have to reboot after a winbind update. Those systems do show a bunch of services using deleting files, but a restart on the services is all it takes. Those systems do show winbind components in use by any process that would force me to reboot.
Apologies, the last sentence should read "Those systems do NOT show winbind components in use by any process that would force me to reboot". -- --Moby They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Sat, 15 Jun 2013 20:57:01 -0500 Moby <moby@mobsternet.com> пишет:
On 06/15/2013 07:40 PM, Cristian Rodríguez wrote:
El 15/06/13 20:20, Moby escribió:
How does one restart systemd without rebooting the OS?
the init system reloads its configuration with systemctl daemon-reload
I have some OSS
machines that use Samba for AD integration. Whenever Samba is updated, libwinbind* all get updated. Prior to OSS 12.3, I could just restart services that used files that had been updated and everything was good. Now, however, systemd appears to use libwinbind* and I have no idea how to get systemd to use the new libwind. I cannot figure out how to restart systemd without a system reboot. Any help is appreciated.
systemd does not use libwinbind (or links to any samba component)...Care to explain your problem better ?
Thanks for the resopnse Cristina.
systemd is using libnss_winbind.so.2 which is provided by samba-winbind. I did: zypper in --force samba-winbind zypper ps
and I see: PID | PPID | UID | Login | Command | Service | Files -----+------+-----+------------+--------------+--------------+------------------ 1 | 0 | 0 | root | systemd | | /lib/libnss_win-> 504 | 1 | 103 | avahi | avahi-daemon | avahi-daemon | /lib/libnss_win-> 1433 | 1 | 0 | root | winbindd | winbind | /lib/libnss_win-> . . .
Doing a systemctl daemon-reload still leaves systemd showing using libnss_winbind.so.2.
Yes. You need "systemctl daemon-reexec" which actually restarts systemd. daemon-reload just makes it to re-initialize configuration. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/15/2013 11:14 PM, Andrey Borzenkov wrote:
В Sat, 15 Jun 2013 20:57:01 -0500 Moby <moby@mobsternet.com> пишет:
On 06/15/2013 07:40 PM, Cristian Rodríguez wrote:
El 15/06/13 20:20, Moby escribió:
How does one restart systemd without rebooting the OS? the init system reloads its configuration with systemctl daemon-reload
I have some OSS
machines that use Samba for AD integration. Whenever Samba is updated, libwinbind* all get updated. Prior to OSS 12.3, I could just restart services that used files that had been updated and everything was good. Now, however, systemd appears to use libwinbind* and I have no idea how to get systemd to use the new libwind. I cannot figure out how to restart systemd without a system reboot. Any help is appreciated. systemd does not use libwinbind (or links to any samba component)...Care to explain your problem better ?
Thanks for the resopnse Cristina.
systemd is using libnss_winbind.so.2 which is provided by samba-winbind. I did: zypper in --force samba-winbind zypper ps
and I see: PID | PPID | UID | Login | Command | Service | Files -----+------+-----+------------+--------------+--------------+------------------ 1 | 0 | 0 | root | systemd | | /lib/libnss_win-> 504 | 1 | 103 | avahi | avahi-daemon | avahi-daemon | /lib/libnss_win-> 1433 | 1 | 0 | root | winbindd | winbind | /lib/libnss_win-> . . .
Doing a systemctl daemon-reload still leaves systemd showing using libnss_winbind.so.2.
Yes. You need "systemctl daemon-reexec" which actually restarts systemd. daemon-reload just makes it to re-initialize configuration.
Thanks Andrey - yep, that did it. systemctl daemon-rexec restart systemd without a system reboot. -- --Moby They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Andrey Borzenkov -
Cristian Rodríguez -
Moby