El mar, 12 de ene. de 2021 a la(s) 19:04, Sam Varshavchik (mr...@courier-mta.com) escribió: > > Alexey Vlasov writes: > > > On Tue, Jan 12, 2021 at 07:01:01AM -0500, Sam Varshavchik wrote: > > > > > > Courier uses the FAM library, which handles server communications, and > > which > > > creates and manages this socket, that is not accessible to Courier or any > > > other client app. > > > > Thank you for your quick answer! > > > > Is it possible to make something like this: > > if FAM socket is broken we will try to kill it and make FAM_open() > > again and continue user's authorization? that is what I am doing now > > with my hands from bash shell. > > The FAM socket is created internally, by the library, and Courier has no > access to it.
> It's theoretically possible to run "ps" in a subprocess and kill the > gam_server process. That will result in a failed socket connection. But > that's not going to be reliable, there will likely be multiple gam_server > processes and there is no convenient way to find the right one. any trick to find the right proces? puff this problem makes me nervous! why this could be happened! is that a specific problem... FAM and gamin has a very very long history of reported bugs.. seems during the check of a large number of files for logins it slows down the entire system, using many CPU cycles if courier relies on that and solution os disabel gam.. so how will work courier? > > _______________________________________________ > Courier-imap mailing list > Courier-imap@lists.sourceforge.net > Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap _______________________________________________ Courier-imap mailing list Courier-imap@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
