fimopatassou

Danke! Damit der Hinweis nicht so einschüchternd wirkt, könnte man ergänzen dass die niedrigeren Sicherheitseinstellungen nur bei Installation und erstem Start des Dienstes und des Programms nötig sind. Zumindest bei mir konnte ich danach wieder die Default-Einstellung aktivieren ("Mac App Store und verifizierte Entwickler"), und brickd und brickv tun es.

Hallo,

ich hatte eben dasselbe Problem mit neu runtergeladenen brickd und brickv unter Mountain Lion... Leider findet sich in der Installationsanweisung für Mac OS noch kein Hinweis auf den funktionierenden Workaround.

Den Kontextmenüeintrag "Öffnen mit Installationsprogramm" habe ich nicht gefunden. Es hilft aber, in den Systemeinstellungen unter "Sicherheit" vorübergehend die Einstellung "Programme aus folgenden Quellen erlauben" auf den Wert "Keine Einschränkungen" zu setzen.

Könnt Ihr das bitte fixen (indem die Downloads signiert werden) oder entsprechend beschreiben?

works fine now!

Thank you for the excellent support.

In my understanding, use of "fork" is unnecessary / forbidden when using Mac OS' launchctl/launchd, so I believe the current implementation is totally correct. Seems that starting a process via launchctl makes it a "real daemon" by definition.

I double checked the installed files in /usr/libexec, and brickd_macosx.py is exactly the same file as the downloaded source.

==> installation package is fine and correctly installed.

Then I downloaded the source files of brickd1.0.2, and I am able to start brickd with

sudo python brickd_macosx.py

It still fails when started with

sudo launchctl start com.tinkerforge.brickd

(Version 1.0.2 and 1.0.3)

==> The problem appears only when started via launchctl, independent of the fix you provided yesterday

Is there any further analysis I can perform? Logging etc?

regarding the installed version of brickd: I found the app in

/usr/libexec/brickd.app

Finder says it is version 1.0.3

All files within the app directory have a current timestamp

--> installation seems to be fine...

yes, I did all of that (and repeated it now). Is there a way to check which version of brickd is currently installed on my system?

macintosh-2:brickd christian$ ps -ef |grep brickd

    0  2851    1  0 10:28pm ??        0:00.23 python brickd_macosx.py

  501  2891  320  0 10:53pm ttys000    0:00.00 grep brickd

macintosh-2:brickd christian$ sudo kill 2851

Password:

macintosh-2:brickd christian$ rm /var/log/brickd.log

rm: /var/log/brickd.log: Permission denied

macintosh-2:brickd christian$ sudo rm /var/log/brickd.log

macintosh-2:brickd christian$ sudo launchctl start com.tinkerforge.brickd

macintosh-2:brickd christian$ ps -ef |grep brickd

  501  2907  320  0 10:54pm ttys000    0:00.00 grep brickd

macintosh-2:brickd christian$ cat /var/log/brickd.log

The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().

Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.

The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().

Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.

The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().

Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.

The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().

Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.

The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().

Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.

The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().

Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.

macintosh-2:brickd christian$

Thank you for the really fast fix...

I downloaded both "brickd_1.0.3.dmg" and "brickd_latest.dmg". Installation completed successfully, but brickd was still not running, with the same error message in /var/log/brickd.log ("The process has forked and you cannot....")

Then, I downloaded the source and was able to start brickd with

    sudo python brickd_macosx.py

After this, Brick Viewer could connect to brickd.

Might be a problem in the installation package? Or do I need to uninstall before installing the newer version of brickd?

Hi,

I just downloaded brickd & brickv for Mac OS.

brickd won't start. In /var/log/brickd.log:

The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().

Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.

Mac OS 10.7.3

Can you please help... Thanks and regards

fimopatassou