[OpenIndiana-discuss] Add inotify support to illumos-gate

Till Wegmüller toasterson at gmail.com
Thu May 25 18:06:44 UTC 2023


Hi

You will have to ask on illumos-developer mailinglist
This is the distribution mailinglist I don't know how many illumos 
advocates are lurking here at this moment.

-Till

On 24.05.23 15:37, Stephan Althaus wrote:
> On 5/12/23 10:30, Stephan Althaus wrote:
>> On 5/2/23 20:25, Till Wegmüller wrote:
>>> Hi Stephan
>>>
>>> inotify has stubbed headers that work roughly decently. Any software 
>>> should use FEN or the Native API. We add it to every programming 
>>> language we can and should also add it to mate-system-monitor or 
>>> rather make it use kstat if it tries to poll things under /proc which 
>>> it should not for us.
>>>
>>> What does mate-system-monitor use inotify for?
>>>
>>> -Till
>>>
>>> _______________________________________________
>>> openindiana-discuss mailing list
>>> openindiana-discuss at openindiana.org
>>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>>
>> Hello!
>>
>> mate-system-monitor dumps core, because of a glib::gio dependency, 
>> because gio can't find(?) a filesystem-monitor-implementation : 
>> "g-io-error-quark: Unable to find default local file monitor type".. 
>> (see below)
>>
>> It would be nice if we could solve the problem before we announce the 
>> new release ISO images.
>>
>> How can we achieve this? i am willing to help, but, because of my 
>> lacking experience i need someone who tells me what exactly to do..
>>
>>
>> Regards,
>> Stephan
>>
>>
>> $ mate-system-monitor
>> (<unknown>:11943): glibmm-CRITICAL **: 10:27:01.361:
>> unhandled exception (type Glib::Error) in signal handler:
>> domain: g-io-error-quark
>> code  : 0
>> what  : Unable to find default local file monitor type
>>
>> Segmentation Fault (core dumped)
>>
>> $ pstack core
>> core 'core' of 11943:    mate-system-monitor
>> --------------------- thread# 1 / lwp# 1 ---------------------
>>  000000000044b0a1 
>> _ZN10ProcmanApp15on_command_lineERKN4Glib6RefPtrIN3Gio22ApplicationCommandLineEEE () + 111
>>  00007fff73009ab0 
>> _ZN3Gio17Application_Class21command_line_callbackEP13_GApplicationP24_GApplicationCommandLine () + 160
>>  00007fffac4ace5f _g_cclosure_marshal_INT__OBJECTv () + 6f
>>  00007fffac79aa08 _g_closure_invoke_va () + 188
>>  00007fffac7baf92 g_signal_emit_valist () + 332
>>  00007fffac7bc17d g_signal_emit () + 7d
>>  00007fffac509933 g_application_call_command_line () + a3
>>  00007fffac50bd71 g_application_real_local_command_line () + 211
>>  00007fff73008722 
>> _ZN3Gio11Application24local_command_line_vfuncERPPcRi () + 52
>>  00007fff7300939b 
>> _ZN3Gio17Application_Class33local_command_line_vfunc_callbackEP13_GApplicationPPPcPi () + fb
>>  00007fffac50bef3 g_application_run () + 133
>>  00000000004239f1 main () + 61
>>  0000000000422d37 _start_crt () + 87
>>  0000000000422c98 _start () + 18
>> <snip>
>>
>>
>> _______________________________________________
>> openindiana-discuss mailing list
>> openindiana-discuss at openindiana.org
>> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 
> Hello!
> 
> Sorry if i am asking something wrong here, if i don't know 'the right 
> way' ...
> 
> It would be nice to have this smartos-commit (origin 2014) upstreamed to 
> illumos-gate:
> https://github.com/TritonDataCenter/illumos-joyent/commit/a9a246c0c49e192616e7499eaa2362b21fde8f5e
> 
> Is someone willing to support this - at least in a somewhat 'political' 
> manner?
> 
> Regards,
> Stephan
> 
> 
> _______________________________________________
> openindiana-discuss mailing list
> openindiana-discuss at openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss



More information about the openindiana-discuss mailing list