[prev in list] [next in list] [prev in thread] [next in thread] 

List:       uwsgi
Subject:    Re: [uWSGI] how to  deal with the limit 64 of uwsgi signal number?
From:       "Roberto De Ioris" <roberto () unbit ! it>
Date:       2015-12-24 9:34:10
Message-ID: 9cec3669da4574eee05a7f9f21eb9d78.squirrel () manage ! unbit ! it
[Download RAW message or body]


> hello:
>
>
>     I use uwsgi filemon to monitor file change,  I only need monitor two
> or three file but my worker number are very many.
>
>
>     for some reason, I need add lazy-app option and It seems that workers
> can't share the signal, and every worker need register the signal two
> or three times.
>
>
>     so worker number * signal number > 64 and uwsgi report error. so I try
> to find way to deal with this situation:
>
>
>     1  can I register the signal in master, so worker can share the signal
> when I use lazy-app option?
>     2  can I execute some python code when I touch file ( not using signal
> because of the limit 64)? I find the touch-hook option, but I can't
> find a way to define a custom hook using python code
>     maybe I can define a mule and in the mule use some sub/pub or
> pyinotify to monitor file, but I wonder are there some eaiser ways?
>    thanks_______________________________________________
> uWSGI mailing list
> uWSGI@lists.unbit.it
> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
>


Hi, that limit is a (now) useless heritage from past versions. We can
absolutely remove it. Btw, use the --shared-pyimport <file> option to load
code in the master (independently by the lazy options)

-- 
Roberto De Ioris
http://unbit.com
_______________________________________________
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
[prev in list] [next in list] [prev in thread] [next in thread]