Hi Steve,
Sorry that you found the canned response accompanying rejection of your
post to wsjt-devel from an un-subscribed email address to be rude. As I
recall, that message simply says that posts are accepted only from
registered subscribers.
We have found this restriction to be necessary i
OK apparently i already had this allocation:
> Last login: Tue Nov 1 03:12:38 on ttys000
> Charless-MacBook-Pro:~ charlesrogers$ sysctl -A | grep shmmax
> kern.sysv.shmmax: 33554432
> Charless-MacBook-Pro:~ charlesrogers$
So it must be something else.
> On Oct 31, 2016, at 4:45 PM, Steven Fra
On 11/1/2016 6:54 PM, Relu Jianu wrote:
> Is there a mechanism of updating the call3.txt list?
>
> Thanks
> 73 Relu NJ9R
Everyone's working habits of band, mode, location, etc., are different.
The callsign database is best maintained by you, yourself, using the
"Add" button on the WSJT or WSJT
Is there a mechanism of updating the call3.txt list?
Thanks73 Relu NJ9R--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel
I just submitted a pull request for Nate that fixed an apparently long standing
buffer overflow in rigctl_parse and rotctl_parse.When connecting rigctl to
rigctld over the network rigctld was aborting with an fscanf arg error. The
\dump_state that rigctl sent was overflowing the buffer.This did
Hi Mike,
I perfectly understood your message, but in a so complex and continuous
evolving project where a lot of code and ideas changed in the years.
So some can be missed
There is also a jt9.txt (see r2820 and r2678) that refer to a
jt9- or wsjtx_changelog.txt that stuck to r3323
Several
Noticed the README is a tad out-of-date.Should there just be a pointer to go
read the introduction.adoc in there along with the other project info?Otherwise
seems like it's just a copy/paste from the introduction to the README with a
bit of added info.
de Mike W9MDB
Well...as one who has never read the manual I understand your concern :-)And I
am one who reads instructions typically.I use manuals as reference and simply
expect to be able to search for questioned information.So unique string chars
like that should appear. I had not idea it was related to VH
Hi Mike,
On 10/31/2016 11:30 PM, Black Michael wrote:
>>> What's up with "#*" modes?
>>
>> #* ==> JT65 mode, normal sync achieved
>> ## ==> JT65 mode, reverse sync ==> EME 'OOO' signal report.
>>
>> It would appear that you have VHF features enabled ??
> Yup...that would be it...was testing a bug
Ok thanks will give it a try tonight.
Sent from my iPhone
> On Nov 1, 2016, at 4:30 AM, Ulderico Arcidiaco
> wrote:
>
> Gary,
>
> just remove the leading $ character before the sysctl command. The $ in the
> command line that you copied is the console prompt, not part of the command.
>
> B
Gary,
just remove the leading $ character before the sysctl command. The $ in the
command line that you copied is the console prompt, not part of the command.
But $ is also used to represent variables in Unix, so $sysctl assumes a
completely different meaning. Because the $sysctl variable doesn
so i went into terminal and here is the result…I must be doing something
wrong…Not a coder:
> Last login: Mon Oct 31 19:52:17 on ttys000
> Charless-MacBook-Pro:~ charlesrogers$ $sysctl -A | grep shmmax
> -bash: -A: command not found
> Charless-MacBook-Pro:~ charlesrogers$ $sysctl -A | grep shmmax
12 matches
Mail list logo
