EricZ
08-14-2009, 09:45 AM
Here is a follow up to subject "Firmware option for remote com port access" http://ubnt.com/forum/viewtopic.php?t=11704 ...
I follow the tutorial pointed by j7r4 : http://linuxfreak.pl/linux/build-wirelless-serial-port-using-ubiquiti-ministation/
After some trouble with cross-compilation, I finally succeed to complete the "how to" but the redirection didn't function.
So I activated log (via "Services" web panel) and in "/var/log/messages" I found this kind of error message :
daemon.err ser2net[300]: Could not open device /dev/ttyS0 for port 2001: No such file or directory
As the ttyS0 device is existing :
XS2.ar2316.v3.3.2.4257.090214.1451# ls -al ttyS0
crw--w--w- 1 admin admin 4, 64 Feb 14 19:29 ttyS0
I search elsewhere.
I look at the running process :
300 admin 316 S ./ser2net -u -c ser2net.conf
...
544 admin 304 S /sbin/getty -L ttyS0 9600 vt100
I thought that the process "getty" was locking ttyS0, so I try to kill it ... and finally succeed.
How I kill getty :
- edit "/etc/inittab" to disable getty respawn
- restart inittab to apply change : "kill -HUP 1"
- at last, kill getty itself : "kill 544"
I check that my process list is clean of any "getty" process and try to connect to ser2net service, but still don't work.
In log, I found the same message :
daemon.err ser2net[300]: Could not open device /dev/ttyS0 for port 2001: No such file or directory
Could permission or something like lock could stay even after running process is killed ?
Cheers from France,
Eric
ps : As my last Linux experience was red hat 5.0 in the late 90's, I consider myself as a newbie. Plus, too many years in Microsoft paradigm didn't help :lol:
But, Hey, I'm here to learn, any help is welcome.
I follow the tutorial pointed by j7r4 : http://linuxfreak.pl/linux/build-wirelless-serial-port-using-ubiquiti-ministation/
After some trouble with cross-compilation, I finally succeed to complete the "how to" but the redirection didn't function.
So I activated log (via "Services" web panel) and in "/var/log/messages" I found this kind of error message :
daemon.err ser2net[300]: Could not open device /dev/ttyS0 for port 2001: No such file or directory
As the ttyS0 device is existing :
XS2.ar2316.v3.3.2.4257.090214.1451# ls -al ttyS0
crw--w--w- 1 admin admin 4, 64 Feb 14 19:29 ttyS0
I search elsewhere.
I look at the running process :
300 admin 316 S ./ser2net -u -c ser2net.conf
...
544 admin 304 S /sbin/getty -L ttyS0 9600 vt100
I thought that the process "getty" was locking ttyS0, so I try to kill it ... and finally succeed.
How I kill getty :
- edit "/etc/inittab" to disable getty respawn
- restart inittab to apply change : "kill -HUP 1"
- at last, kill getty itself : "kill 544"
I check that my process list is clean of any "getty" process and try to connect to ser2net service, but still don't work.
In log, I found the same message :
daemon.err ser2net[300]: Could not open device /dev/ttyS0 for port 2001: No such file or directory
Could permission or something like lock could stay even after running process is killed ?
Cheers from France,
Eric
ps : As my last Linux experience was red hat 5.0 in the late 90's, I consider myself as a newbie. Plus, too many years in Microsoft paradigm didn't help :lol:
But, Hey, I'm here to learn, any help is welcome.
