I am unsing 1.53 (tarball verson) under opensuse 12.1.
I have "Run rigctld when program starts"
rigctld does start, but when I exit CQRLog using the File --> Close menu, rigctld is not killed.
32404 ? S 0:00 /usr/bin/rigctld -m 313 -r /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AH01D7H3-if00-port0 -t 4532
Do I need set something so rigctl dies when CQRLog exits?
Sun, 2013-04-07 02:29
#1
CQRLog doesn't kill rigctld
I'm having this problem as well and am surprised everyone is not having this issue (or are they?) -I've written a small script to kill the rigctld and do a few backups when I'm donewith CQRLog but remain surprised that the program doesn't kill its daemon when it exists.
Seems like a bug -?
I find that I can exit cqrlog (leaving rigctld running) then invoke it again with no problems- BUT if the machine I'm using "sleeps" or "hibernates", or if I log out then back in to the (continuously-running) machine, I'm left with a rigctld that has lost its connection to the rig.
If I exit cqrlog, then kill rigctld, I find I must unplug and re-plug the rig's USB connector in order for the next invocation of rigctld to obtain a connection to the rig. I'm using /dev/ttyUSB0 and a Prolific USB-Serial adapter.
Does anyone else have this issue?
Same issue here. Using Ubuntu 12.04 and CQRLog 1.5.4. Real problem cuz i cannot connect to device after repowering it. Ubuntu assigns a new port and CQLog locked to old port thru still active rigctld. Hope the team fixes this.
Regards,
Blair ki4yy
I have checked it on my machine and rigctld is killed here without problems after shutting down CQRlog 1.5.4
on Ubuntu 10.04. As well as on my Mint 14 installation. I am using a true serial port (/dev/ttyS0 and /dev/ttyS4 in Mint 14).