-----BEGIN PGP SIGNED MESSAGE-----
On 08/11/2015 12:13 PM, Keith C. Perry wrote:
> didn't work with the while loop either.... I just tried it with a -w
> 3600, assuming it would wait 3600 seconds til it disconnected. Started
> it up with an ampersand, called the PBX, hung up. Tail -f the file from
> a different putty session and saw the info for the call come in....then
> I saw this on the screen.
> + Stopped ./get_smdr.sh
> If I do a ps -ef | grep get_, or grep for netcat, both are still running
> but its not updating the file any longer. If I kill the pid for
> get_smdr.sh, it then says killed and kills the pid for netcat and if I
> restart, works fine again for a bit.
> What is the difference between stopping and killing?
> I thought that maybe the PBX was sending a terminate or end command but
> that would not effect the get_smdr script and besides, in the
> foreground, will run all day long
Sorry, I didn't see this mentioned anywhere yet- *which* netcat are you
Right off the top of my head, I know four:
"nc", which is the original "Hobbit" source from old UNIX days (plus
usually patched in ipv6 support plus some other patches from debian)
"ncat", which is Nmap suite's netcat
"netcat", openBSD's vanilla netcat
"netcat", GNU's total rewrite.
and i'm sure there are other forks.
and they can all be called 'nc' or 'netcat' on the system.
and they all (generally) have incompatible options.
and distros usually include two or more of the above in their package
so knowing which one can be confusing. :) if you check the manpage, it
should give clues under Authors section.
from there i can maybe help you out, but i don't want to take a stab and
guess the wrong netcat.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-----END PGP SIGNATURE-----
Philadelphia Linux Users Group --
General Discussion --