[Dachs-support] [bug] No DaCHS server appears to be running

Carlos Henrique Brandt carloshenriquebrandt at gmail.com
Mon Feb 28 17:25:55 CET 2022


Hi Markus,

 I think now, after re-reading your answer, I understood what is going on...


See also
> http://docs.g-vo.org/DaCHS/tutorial.html#dealing-with-rd-changes


 Right. Indeed, looks like I don't need "dachs reload" (I'm not doing
__system__ files or *-core stuff).


In the end, dachs reload just sends a signal (a SIGHUP), and
> *probably* making it equivalent to killall -HUP dachs (or so)
> wouldn't hurt.  But then the whole thing has become so questionable
> that I guess I'll just do away with the whole command and tell people
> who *really* want to have this cache dropping to killall -HUP.
>

 Yep, sounds good to me; You made your point clear; The (common) use cases
for "reload" are not there anymore.

Carlos
-- 
Smile, for no reason.
----------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.g-vo.org/pipermail/dachs-support/attachments/20220228/795d232d/attachment.htm>


More information about the Dachs-support mailing list