[etherlab-users] Call control executable as user without admin rights

Richard Hacker ha at igh.de
Mon Apr 28 09:51:13 CEST 2014


Am 04/25/2014 05:29 PM, schrieb Matthias Liermann:
> Hello Richard,
> Thank you for your quick help. Your experiment worked. I could see in the other terminal what I was entering in the first. I wonder what else I could do to help understand the cause of my problem. I only know that when I start the executable as root, it is visible for the testmanager. If I start it normally, it is not visible. We also used netstat to see if a port 2345 was opened. It wasn't in the latter case. We get no error messages and the lamps on the Beckhoff module suggest that the program is running as it should.
> Best, Matthias Liermann
OK, really strange.

Then start the application again, as root and as normal user in 
succession, each time manually connecting to the port (as normal user) 
with "netcat localhost 2345"

Do you get a message
<connected .....>
in the netcat terminal?

What does "netstat -an | grep 2345" say in each case?

>
> -----Original Message-----
> From: Richard Hacker [mailto:ha at igh.de]
> Sent: Friday, April 25, 2014 6:04 PM
> To: Matthias Liermann
> Subject: Re: [etherlab-users] Call control executable as user without admin rights
>
> Am 04/25/2014 03:45 PM, schrieb Matthias Liermann:
>> Dear Martin,
>>
>> You helped us three weeks ago with the advice to add the user to the
>> realtime group. Now we have one more problem. The realtime program
>> starts fine and communicates with the Beckhoff Module as normal user.
>> We use Ubuntu 10.04 and Etherlab 2.0. But it doesn't open the port
>> 2345 so that we can connect to it with the msr_test_manager.
>>
>> We tried starting the realtime with sudo and this still works fine.
> That is a bit odd.
>
> Try as normal user: "netcat -l 2345"  (this listens for incoming connections on port 2345)
>
> On another terminal try "netcat localhost 2345" and type in something (remember to press Enter!). Do you see anything in the first netcat terminal? If so, then the problem is elsewhere. Normally, users can listen on any port > 1023.
>
>>
>> Do you have any idea how we can allow a normal user to open that port?
>>
>> Best, Matthias
>>
>> Assistant Professor
>>
>> American University of Beirut <http://aub.edu.lb/>
>>
>> Department of Mechanical Engineering
>> <http://www.aub.edu.lb/fea/me/Pages/default.aspx>
>>
>> Personal Homepage <http://staff.aub.edu.lb/~ml14/Homepage/>
>>
>>
>>
>> _______________________________________________
>> etherlab-users mailing list
>> etherlab-users at etherlab.org
>> http://lists.etherlab.org/mailman/listinfo/etherlab-users
>>



More information about the Etherlab-users mailing list