Skip to content

Adding explicit instructions about /var/lock #178

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 6 commits into from
Closed

Adding explicit instructions about /var/lock #178

wants to merge 6 commits into from

Conversation

kigster
Copy link
Contributor

@kigster kigster commented Jul 12, 2014

This cost me at least 2 hours of wrestling until I stumbled upon this thread:
#129

I have a 64-bit version of jnlb serial library, but I was still not able to write to serial port until /var/lock was created. So I am adding a check for for MacOS and /var/lock being accessible so that nobody has to waste anymore time :)

If there are alternative means of removing this unfortunate stumbling block, feel free to reject :)

Konstantin Gredeskoul added 2 commits July 11, 2014 18:36
 * this cost me at least 2 hours of wrestling 
   until I stumbled upon this thread:
   #129

Adding a check for for MacOS and /var/lock being
accessible so that nobody has to waste anymore time :) 
Once you run the command, subsequent upload succeeds.
@alpha-ninja
Copy link

Change the text to "not accessible or already in use: try to quit all other programs that may be using it. If that doesn't fix it, please run the following command:"

Also, fix that it's actually quitting not quiting ;)

@kigster
Copy link
Contributor Author

kigster commented Jul 12, 2014

@alpha-ninja that's a great suggestion. Coming up with some refactoring :)

Konstantin Gredeskoul added 2 commits July 11, 2014 21:29
 * Since the change was made so long ago I am hoping we can go 
   back to having this useful descriptive error.  It's really 
   nice to be reminded when the port setting may have remained
   from a previous project/setup.
@kigster
Copy link
Contributor Author

kigster commented Jul 12, 2014

I have another big chunk of the serial code refactored here:
kigster@207d300

I'll submit that as a separate pull request later. But in the meantime any feedback is welcome!

@alpha-ninja
Copy link

Add some \n's to the mac error message. (\r\n is not required as this message only shown on mac anyway) It'd help everyone's eyes :P

@kigster
Copy link
Contributor Author

kigster commented Jul 12, 2014

@alpha-ninja it's already there in the latest commit.

@alpha-ninja
Copy link

as in add it to the text that's passed on to the log method. The readability improvement through concats is not what I mean

@alpha-ninja
Copy link

à la

Common.log(new Status(IStatus.ERROR, ArduinoConst.CORE_PLUGIN_ID, "Serial port " + PortName
+ " is not ... using it. THIS RIGHT HERE ---> \n"
+ " If that doesn't fix it, please run the following command:"
+ "\n\nsudo mkdir -p /var/lock && sudo chmod 777 /var/lock\n"));

@jantje
Copy link
Member

jantje commented Jul 12, 2014

I just wonder why I keep updating the faq : http://eclipse.baeyens.it/Arduino%20eclipse%20plugin%20FAQ.html#MAC_Lock
It should be the first place to look.
I guess you switched to arduino IDE 1.5.6 or higher. That means Arduino moved to JSSC see #67
Arduino removed the delivered RXTX libraries and as such you fall back on the plugin delivered libraries.
I have copied the RXTX libraries into the newer Arduino versions as I had some issues as well.
I give 100% priority to #67 right now so I will not accept these changes. Sorry for that.

@jantje jantje closed this Jul 12, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants