Skip to content

Conversation

@tbzatek
Copy link

@tbzatek tbzatek commented Dec 16, 2019

Elogind ships with the libelogind library that is built upon libsystemd sources. Symbol names, header file naming and most of its original functionality is preserved.

https://github.com/elogind/elogind

Closes #17

Elogind ships with the libelogind library that is built upon
libsystemd sources. Symbol names, header file naming and most
of its original functionality is preserved.

https://github.com/elogind/elogind
@tbzatek
Copy link
Author

tbzatek commented Dec 16, 2019

Quick and dirty patch. Nearly untested. It compiles, executes and reacts on usid commands.

$ usid version
USID_PROTOCOL=1
USID_MAJOR=0
USID_MINOR=0
USID_RELEASE=2
SID_PROTOCOL=1
SID_MAJOR=0
SID_MINOR=0
SID_RELEASE=2
$ usid active
USID_BRIDGE_STATUS=active

I'm getting lots of errors like

<command/20543/scan> scan-next phase failed.
<command/20543/scan> Failed to execute command

though they might be unrelated to this change.

@tbzatek
Copy link
Author

tbzatek commented Dec 16, 2019

# sid -f -v
^C<sid> Event loop failed.: Unknown error 1419826320.

@prajnoha
Copy link
Member

I'm getting lots of errors like

<command/20543/scan> scan-next phase failed.
<command/20543/scan> Failed to execute command

though they might be unrelated to this change.

Yes, that's expected for now - this is because of missing modules to handle specific device types (I should probably change/add better message here so it's more clear what's wrong).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Consider making dependency on systemd optional

2 participants