Displaying 2 results from an estimated 2 matches for "start_monitor".
2021 Jan 07
1
HCI Cluster - CentOS8 to Streams Upgrade Broken
....HostedEngine ERROR Failed to
start necessary monitors
Jan 7 09:48:06 thor journal[2375091]: ovirt-ha-agent
ovirt_hosted_engine_ha.agent.agent.Agent ERROR Traceback (most recent call
last):#012 File
"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
line 85, in start_monitor#012 response = self._proxy.start_monitor(type,
options)#012 File "/usr/lib64/python3.6/xmlrpc/client.py", line 1112, in
__call__#012 return self.__send(self.__name, args)#012 File
"/usr/lib64/python3.6/xmlrpc/client.py", line 1452, in __request#012
verbose=self.__verbos...
2005 Feb 04
7
FW: Bug fix
...NITE,true){ |s|
> p s
> }
Hmm. I don''t know. I''m not sure if I wanna remember the
ChangeNotify::INFINITE constant - the default behaviour is intuitive, to
me(though the name''s more ipc-ish than filesystem). Maybe a new method
in changenotify - something like the
start_monitoring(sic) in DirectoryWatcher. (I feel the API is too much
tied with ipc as it is. True, it inherits from ipc, but I''m not sure if
someone with the general watch-for-file-system-changes use-case wants to
know that there is ipc and monitors going on behind the scenes. Just my
2 paise, and hop...