Ah, so Bluetooth only shuts off when you shut down? Interesting.

When you downloaded blueutil, how did you install it? There is an 'Install' file (it's a .command file). Did you double-click that?

Bluetooth only needs to be restarted after shutting down as one particular user. I have not been able to get Blueutil working yet. I tried installing it with a double click.

What happened when you did that?

I got a message : the execution error: cp: directory /usr/local/bin does not exist (1)

In your Terminal, try the following command:

sudo mkdir /usr/local/bin

And enter your admin password when prompted. Then try installing again.

By the way, that's a pretty poor installer that assumes /usr/local/bin already exists, but doesn't create it in the event that it doesn't. /usr/local/bin is common across Unix systems, but it does not exist by default in OS X.

Trevor

Just tried that but terminal would not accept anything typed after password!

Yes, that's a security feature in the terminal:
You will not see anything repeated as you type in your password. Just type it, then press enter.

Hi, I got
mkdir: /usr/local: No such file or directory

You've probably already moved on by now, but for others asking the same question, using the following will create the directory, including intermediate dircectories:

Hi, thanks for your info. I still have not resolved the problem and work with it but find that except for the admin account, other accounts don't seem to have the problem and remain connected to Bluetooth.
I tried what you suggest but got no response from Terminal as below.
rsk-853:~ test$ sudo mkdir -p /usr/local/bin
rsk-853:~ test$

That is your response.
You run the mkdir command, which creates the folder that you need, and the terminal returns your text prompt. It wouldn't tell you anything else, unless there is a problem with creating the folder.
And, after that command, you should be able to run the blueutil app.

Just tried using blueutil and command not found
was reported. What next?

That probably means that blueutil is not in your PATH. Since you put blueutil in /usr/local/bin (which I think is the best place for you to have put it), you will need to add /usr/local/bin to the PATH.

First, let's verify that my guess is correct, since there are also other possible explanations for 'command not found'.

echo $PATH
(and hit Return at the end of the command)

Terminal should respond with a list of the directories in your PATH, looking something like:

% echo $PATH
/usr/local/bin:/usr/local/sbin:/sw/bin:/sw/sbin:/usr/local/lib:/usr/bin:/bin:/usr/sbin:/sbin:/usr/lib

Check and see if /usr/local/bin is listed, preferably near the beginning, and definitely earlier than /bin. If it's not, you'll need to add it.

I'm going to assume that you are using bash shell, which is the default in OS X. If you use something other than the default, then you probably don't need this explanation from me. Look in your home directory for any of the following files: .bash_profile, .bash_login, .profile, .bashrc

ls -al ~

If you don't see any of those files, then you have many many options for how you want to set this up. I'll give you one way, but there are a bajillion others, and everyone who uses Unix has their own opinion about the best way.

If you DO see one of those files in your home directory, let us know what it is and what it has in it. So for example, if you have a .bash_profile file, then issue the command:
cat ~/.bash_profile

...and copy/paste what you have here for us to see.

But back to the assumption that you don't have any of these files, the way I would do it is to create the files. I'll use pico, which is a very easy to use text editor. First create .bash_profile

pico ~/.bash_profile
(remember to hit Return at the end of commands)

This will put you into the pico text editor. Now copy/paste the text below into pico:

source $HOME/.bashrc

Now, hit Control-O to write the file, then hit Control-X to exit pico.

Next, create .bashrc:

pico ~/.bashrc

Now, copy/paste the following into pico:

export PATH=/usr/local/bin:$PATH


Hit Control-O to write, Control-X to exit.

Now, quit your Terminal program. Relaunch Terminal, and try the following command:
which blueutil

It should respond with /usr/local/bin/blueutil

If it responds with nothing, or with something else, then there's still a problem.

Trevor

Hi, I have 0 29 Nov 11:06 .bash_profile
but cat ~/.bash_profile produces no result.

That means that there is nothing in the file. So follow the directions above as if it didn't exist.

Trevor

Got as far as control-O but got a beep on Control-X with info on running processes being login,bash,nano.
Which blueutil gave me export PATH/usr/local/bin:$PATH

When you hit Control-O, the bottom of the pico screen gives you the filename, and you hit Return. After hitting Return, hit Control-X to exit.

Can you copy/paste a transcript from your Terminal? You should see
export PATH=/usr/local/bin:$PATH
as a response from cat .bashrc, but getting that as a response to which blueutil makes no sense. You'll either get nothing (which means you don't have blueutil anywhere in your PATH) or /usr/local/bin/blueutil (which means that your computer is seeing the right blueutil), or some other path to blueutil (which means that your computer is seening the wrong blueutil).

Trevor

Hardware issues like, for example, the PRAM battery.

Loss of settings after a shutdown is the primary symptom of a dead battery. They frequently need to be replaced every five years or so.

Hi Trevor, just complete what you advised and have the following from Terminal:

Last login: Tue Mar 11 08:01:22 on console
rsk-853:~ test$ pico ~/.bash_profile
rsk-853:~ test$ which blueutil
/usr/local/bin/blueutil
rsk-853:~ test$ cat ~/.bash_profile
source $HOME/.bashrc

rsk-853:~ test$

regards, Robert

OK, so blueutil is now in your PATH. Does it work?

Trevor