Debug log not working

[precursorca]

The -d option for Debug log does not work.
There is no file at /var/log/pinpoint.log
Even when including the API key in the options.
sudo /Library/Application\ Support/pinpoint/bin/pinpoint.sh -d -k MYlongAPIKey

[precursorca]

This can be resolved by changing the line:

-d | --debug ) use_debug=1
to
-d | --debug ) use_debug="True"

[precursorca]

This may apply to the use_optim too.

[jelockwood]

@precursorca
Sorry for the lack of progress my side. I currently have to work five days a week in the office which means during that time I cannot engage in 'hobbies'. I also have to fit in all the normal household tasks over the weekend.

I saw your message you have made a fork with various fixes. I will look at your commit and review your changes. Might still take a little while, I will then build a new installer pkg.

[precursorca]

Thank you for keeping pinpoint alive!- - -Sincerely,AlexOn Oct 22, 2024, at 1:32 pm, jelockwood ***@***.***> wrote: @precursorca Sorry for the lack of progress my side. I currently have to work five days a week in the office which means during that time I cannot engage in 'hobbies'. I also have to fit in all the normal household tasks over the weekend. I saw your message you have made a fork with various fixes. I will look at your commit and review your changes. Might still take a little while, I will then build a new installer pkg. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[jelockwood]

@precursorca
Another 'excuse' for the slowness, I no longer have a Google API license so cannot do much testing myself.

I see there is currently another pending commit before yours. I will need to review that and might need to approve that first. This might require you to make adjustments to match. I will let you know.

[jelockwood]

I had a look at your currently open commit to Pinpoint. I see it only adds code to run the Python script as a non-root user. This would indeed fix the root user issue whereby root does not have permission to use location services but it does add a dependency that you need to use a known user account which has itself got location services enabled. It is for all intents and purposes impossible to enable location services for root but would be possible for normal and admin accounts - typically a manual exercise. I am intending to no longer use the Python script which does require using location services and hence does not work for root. I am now intending to use a simple shell script which will work fine for root and other users without needing location services. Therefore it will no longer be necessary to check for and execute with a non-root process. It will also remove the need for Python. I therefore suggest you cancel that commit if you can or otherwise if you are ok with it I can do that. We can then move on to the other issues. I see no commit as of yet for those proposed changes. For your benefit, the additional shell script that I will use instead of the Python script is here - https://github.com/jelockwood/pinpoint/blob/master/pinpoint_scan.sh On Tue, Oct 22, 2024 at 7:34 PM Alex Narvey ***@***.***> wrote:

…

Thank you for keeping pinpoint alive!- - -Sincerely,AlexOn Oct 22, 2024, at 1:32 pm, jelockwood ***@***.***> wrote: @precursorca Sorry for the lack of progress my side. I currently have to work five days a week in the office which means during that time I cannot engage in 'hobbies'. I also have to fit in all the normal household tasks over the weekend. I saw your message you have made a fork with various fixes. I will look at your commit and review your changes. Might still take a little while, I will then build a new installer pkg. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***> — Reply to this email directly, view it on GitHub <#29 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABAZ74QCE323NLGYEBMA5DDZ42LBTAVCNFSM6AAAAABNKYEBM2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRZHE3TOOBUGA> . You are receiving this because you commented.Message ID: ***@***.***>

-- [image: View my profile on LinkedIn]View John Lockwood's profile <http://uk.linkedin.com/in/jelockwood/>

[precursorca]

I made a few other changes that affect how options work. I will cancel my commit. And just work on getting things running for myself while you look after the project on your own timetable. Thanks for the simple script. That will make things much easier than using the python scan.

…

--- Alex Narvey ***@***.***

On Oct 23, 2024, at 9:58 AM, jelockwood ***@***.***> wrote: I had a look at your currently open commit to Pinpoint. I see it only adds code to run the Python script as a non-root user. This would indeed fix the root user issue whereby root does not have permission to use location services but it does add a dependency that you need to use a known user account which has itself got location services enabled. It is for all intents and purposes impossible to enable location services for root but would be possible for normal and admin accounts - typically a manual exercise. I am intending to no longer use the Python script which does require using location services and hence does not work for root. I am now intending to use a simple shell script which will work fine for root and other users without needing location services. Therefore it will no longer be necessary to check for and execute with a non-root process. It will also remove the need for Python. I therefore suggest you cancel that commit if you can or otherwise if you are ok with it I can do that. We can then move on to the other issues. I see no commit as of yet for those proposed changes. For your benefit, the additional shell script that I will use instead of the Python script is here - https://github.com/jelockwood/pinpoint/blob/master/pinpoint_scan.sh On Tue, Oct 22, 2024 at 7:34 PM Alex Narvey ***@***.***> wrote: > Thank you for keeping pinpoint alive!- - -Sincerely,AlexOn Oct 22, 2024, > at 1:32 pm, jelockwood ***@***.***> wrote: > @precursorca > Sorry for the lack of progress my side. I currently have to work five days > a week in the office which means during that time I cannot engage in > 'hobbies'. I also have to fit in all the normal household tasks over the > weekend. > I saw your message you have made a fork with various fixes. I will look at > your commit and review your changes. Might still take a little while, I > will then build a new installer pkg. > > —Reply to this email directly, view it on GitHub, or unsubscribe.You are > receiving this because you were mentioned.Message ID: ***@***.***> > > — > Reply to this email directly, view it on GitHub > <#29 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABAZ74QCE323NLGYEBMA5DDZ42LBTAVCNFSM6AAAAABNKYEBM2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRZHE3TOOBUGA> > . > You are receiving this because you commented.Message ID: > ***@***.***> > -- [image: View my profile on LinkedIn]View John Lockwood's profile <http://uk.linkedin.com/in/jelockwood/> — Reply to this email directly, view it on GitHub <#29 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEG7VERZ52S73UWGKRDZW5TZ462PZAVCNFSM6AAAAABNKYEBM2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZSGUYTSMBWGM>. You are receiving this because you were mentioned.

[jelockwood]

@precursorca
As you can see I have now uploaded that shell script and done some documentation changes. So the next major step would be to incorporate your debug etc. fixes. Then I can add changes to call my new pinpoint_scan.sh script and provide a pre-release installer pkg for testing.

[precursorca]

Thank you.

…

--- Alex Narvey ***@***.***

On Oct 23, 2024, at 10:06 AM, jelockwood ***@***.***> wrote: @precursorca <https://github.com/precursorca> As you can see I have now uploaded that shell script and done some documentation changes. So the next major step would be to incorporate your debug etc. fixes. Then I can add changes to call my new pinpoint_scan.sh script and provide a pre-release installer pkg for testing. — Reply to this email directly, view it on GitHub <#29 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEG7VEUXTB4LAYDLGRQ4D6LZ463PZAVCNFSM6AAAAABNKYEBM2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZSGU2DOOJRHE>. You are receiving this because you were mentioned.

[precursorca]

I do have an API instance but it is capped at the free limit of 600 lookups per day (300 for geolocation and 300 for geocoding). You would think that with 120 or so devices and with using the optimization I would be under that for the day, I am having some success but by afternoon I all my instances start showing RATE EXCEEEDED messages even though the haven’t moved and the AP hasn’t changed. So I continue to work on my version and am now fussing a bit with the optimization code. So I continue to update my fork accordingly (just so you can see if you like) but haven’t asked for any pull request. I also corrected a problem in the location module itself that was preventing pins from being displayed (only clusters were still working but when you magnify enough to pierce the cluster there was nothing). I have asked for a pull request from the location modules repo (not your concern at all but I thought you might like to know). Sincerely,

…

--- Alex Narvey ***@***.***

On Oct 23, 2024, at 9:58 AM, jelockwood ***@***.***> wrote: I had a look at your currently open commit to Pinpoint. I see it only adds code to run the Python script as a non-root user. This would indeed fix the root user issue whereby root does not have permission to use location services but it does add a dependency that you need to use a known user account which has itself got location services enabled. It is for all intents and purposes impossible to enable location services for root but would be possible for normal and admin accounts - typically a manual exercise. I am intending to no longer use the Python script which does require using location services and hence does not work for root. I am now intending to use a simple shell script which will work fine for root and other users without needing location services. Therefore it will no longer be necessary to check for and execute with a non-root process. It will also remove the need for Python. I therefore suggest you cancel that commit if you can or otherwise if you are ok with it I can do that. We can then move on to the other issues. I see no commit as of yet for those proposed changes. For your benefit, the additional shell script that I will use instead of the Python script is here - https://github.com/jelockwood/pinpoint/blob/master/pinpoint_scan.sh On Tue, Oct 22, 2024 at 7:34 PM Alex Narvey ***@***.***> wrote: > Thank you for keeping pinpoint alive!- - -Sincerely,AlexOn Oct 22, 2024, > at 1:32 pm, jelockwood ***@***.***> wrote: > @precursorca > Sorry for the lack of progress my side. I currently have to work five days > a week in the office which means during that time I cannot engage in > 'hobbies'. I also have to fit in all the normal household tasks over the > weekend. > I saw your message you have made a fork with various fixes. I will look at > your commit and review your changes. Might still take a little while, I > will then build a new installer pkg. > > —Reply to this email directly, view it on GitHub, or unsubscribe.You are > receiving this because you were mentioned.Message ID: ***@***.***> > > — > Reply to this email directly, view it on GitHub > <#29 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABAZ74QCE323NLGYEBMA5DDZ42LBTAVCNFSM6AAAAABNKYEBM2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRZHE3TOOBUGA> > . > You are receiving this because you commented.Message ID: > ***@***.***> > -- [image: View my profile on LinkedIn]View John Lockwood's profile <http://uk.linkedin.com/in/jelockwood/> — Reply to this email directly, view it on GitHub <#29 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEG7VERZ52S73UWGKRDZW5TZ462PZAVCNFSM6AAAAABNKYEBM2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZSGUYTSMBWGM>. You are receiving this because you were mentioned.