Re: FTDI Consoles appear down

Hi, 

Finally worked!, I'm quite sorry as finally was due a permissions problem:

When I tried to launch the conserver daemon with debug enabled I've seen that all prior non-working consoles shown now as Up. After supicious checks I realized that I was 'debugging' conserver as root user (instead of the usual 'conservr' user), so I checked and:

crw-rw-r-- 1 root plugdev 188, 3 Apr  4 16:48 /dev/serial/by-id/usb-FTDI_SheevaPlug_JTAGKey_FT2232D_B_FTVB6MLG-if01-port0
crw-rw---- 1 root dialout 188, 6 Mar 17 16:11 /dev/serial/by-path/pci-0000:00:1d.7-usb-0:4.3:1.0-port0
crw-rw---- 1 root dialout 188, 9 Apr  4 17:30 /dev/serial/by-path/pci-0000:00:1d.7-usb-0:4.1.4:1.0-port0
crw-rw---- 1 root dialout 188, 7 Apr  4 17:29 /dev/serial/by-path/pci-0000:00:1d.7-usb-0:4.1.1:1.0-port0
crw-rw---- 1 root dialout 188, 8 Mar 17 15:18 /dev/serial/by-path/pci-0000:00:1d.7-usb-0:4.1.3:1.0-port0
crw-rw-r-- 1 root plugdev 188, 5 Apr  4 17:42 /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AI0388XH-if00-port0
crw-rw-r-- 1 root plugdev 188, 4 Apr  4 17:42 /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AL00LUS9-if00-port0

~# id conservr
uid=111(conservr) gid=20(dialout) groups=20(dialout)

The fact that it only happened with FTDI devices made me, erroneoulsy, suspect of HW/driver/serial issue. Although really was due the fact the FTDI devices are configured in conserver.cf by dev ID while the rest by path, and some udev rules (which give dialup permissions) didn't worked over them.

Yes, novice mistake. Big mistake from my side.
I'm very sorry for the time, but thanks for the hints which although pointing to some other reasons, allowed me to find my error.


Thanks All