clixon_backend not running.

[clicon]

clixon_backend not running.

[olofhagsand]

I understand. I will change so that the char for getopt is signed. NP. Are there other problems on ARM?

[olofhagsand]

I havent tested on ARM.

• Try clixon_cli or clixon_restconf (same result?)
• Run in gdb with -F. (configure --enable-debug)
• Valgrind?

[shubhtrix]

Ya found the problem!!!

See on ARM "char" behaves as a "unsigned char" so under "/apps/backend/backend_main.c" we have a while loop under main inside that you defined char c; for getopt . So on ARM machine this char c gets a value after all the short-options c updates with a value of 255 oxff which never terminates the while loop with -1 .

[olofhagsand]

@shubhtrix what is the fix? Change char to signed char/int8_t? I would like to patch the src to cover this case.

[shubhtrix]

@olofhagsand ya sorry for a quick fix on that I applied a simple int not tried with int8_t or signed char. As per the problem is concerned, hopefully both should work (signed char and int8_t). I'll let you know if the time permits after testing with signed char and int8_t. Untill then be with the same char or maybe an int because on any x86 arch. it works fine just the ARM which is causing the problem.

[shubhtrix]

@olofhagsand Sorry to disturb you again, but ya I've realized that the same thing exists in clixon_restconf, clixon_netconf, example_backend, example_restconf etc. I mean wherever you used getopt

[shubhtrix]

@olofhagsand sorry for late reply, I don't have any other problem yet.

But I have a query... "Is it necessary to run the restconf daemon with user : www-data? I mean what if I run the daemon with root user, any problem in that? And if you think any consequences regarding the functionally of the same."

[olofhagsand]

There is some related discussion here:
#37
Also in the slack:
https://clixondev.slack.com/messages/C9M4TC9MW/

[olofhagsand]

Outdated question