Remote mode for FLDIGI

6 posts / 0 new
Last post
w6ocl
Remote mode for FLDIGI

Petr,
Is there a correct way to exit out of fldigi once i'm done using it?  I ask this as i am finding defunct processes hanging around after i exit out of fldigi when running it in remote mode.  See example below:
osiel@Plutonium ~ $ ps -efa|grep fldigiosiel    13460 12842  0 14:53 ?        00:00:06 [fldigi] <defunct>osiel    13577 12842  2 15:10 ?        00:08:05 [fldigi] <defunct>osiel    15226 12842  3 18:42 ?        00:06:29 [fldigi] <defunct>osiel    15882 15869  0 21:35 pts/3    00:00:00 grep --colour=auto fldigi
I've tried to exit fldigi first, the stop the "remote mode for fldigi", I've also tried stopping the "remote mode" first, then shutting down fldigi, but either way, i still get the defunct processes.
 

ok2cqr
ok2cqr's picture
Re: Remote mode for FLDIGI

Hi,
 
very strange. I thought tat close fldigi is correct way to close it completely. I added the communication with fldigi long time a go but I don't use it at all, I'm CW guy and not interested in digi modes. 
 
73 Petr

w6ocl
I understand.. so, i guess

I understand.. so, i guess the defunct processes are not what should be happening.

k8wdx
k8wdx's picture
No problem here. Works great.

No problem here. Works great. Put cqrlog in fldigi mode. Work stations. When done. Shut down fldigi.  And get cqrlog out of fldigi mode. All works great. Tom K8WDX

Tom K8WDX

w6ocl
Tom, do you manually start

Tom, do you manually start fldigi after going into fldigi remote mode or do you let CQRLog start fldigi for you?
After running 2 tests, If i disable the "Run fldidi after entering to Remote Mode" option, then i select File -> Remote mode for fldigi, manually start fldigi, work station, close fldigi, uncheck File -> Remote mode for fldigi, the fldigi process goes away without leaving anything behind.  See below:
osiel@Plutonium ~ $ ps -efa|grep fldigiosiel    28635 28622  0 21:28 pts/1    00:00:00 grep --colour=auto fldigiosiel@Plutonium ~ $ ps -efa|grep fldigiosiel    28637 28622  0 21:28 pts/1    00:00:00 grep --colour=auto fldigiosiel@Plutonium ~ $ ps -efa|grep fldigiosiel    28644     1  9 21:29 ?        00:00:00 fldigiosiel    28689 28622  0 21:29 pts/1    00:00:00 grep --colour=auto fldigiosiel@Plutonium ~ $ ps -efa|grep fldigiosiel    28692 28622  0 21:29 pts/1    00:00:00 grep --colour=auto fldigi
If i enable "Run fldigi after entering to Remote mode", then i select File -> Remote mode for fldigi, let CQRLog start fldigi, work station, close fldigi, uncheck File -> Remote mode for fldigi, the fldigi process goes defunct.  See below:
osiel@Plutonium ~ $ ps -efa|grep fldigiosiel    28694 28622  0 21:29 pts/1    00:00:00 grep --colour=auto fldigiosiel@Plutonium ~ $ ps -efa|grep fldigiosiel    28695 22139  9 21:29 ?        00:00:00 /usr/bin/fldigiosiel    28740 28622  0 21:29 pts/1    00:00:00 grep --colour=auto fldigiosiel@Plutonium ~ $ ps -efa|grep fldigiosiel    28695 22139  5 21:29 ?        00:00:01 [fldigi] <defunct>osiel    28748 28622  0 21:30 pts/1    00:00:00 grep --colour=auto fldigiosiel@Plutonium ~ $
This can't be normal or i'm doing something wrong.
 
My linux version is Linux Mint Trusty Tahr
osiel@Plutonium /etc $ cat os-releaseNAME="Ubuntu"VERSION="14.04, Trusty Tahr"ID=ubuntuID_LIKE=debianPRETTY_NAME="Ubuntu 14.04 LTS"VERSION_ID="14.04"HOME_URL="http://www.ubuntu.com/"SUPPORT_URL="http://help.ubuntu.com/"BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
 

w6ocl
As the defunct processes

As the defunct processes continue to increment with every restart of fldigi, the easiest way to make the defunct processes to go away is to recycle CQRLog.  This tells me that something isn't being killed/closed properly.