instances vs. Everything Service

[NotNull]

When Everything 1.5 is running without instance (NO_ALPHA_INSTANCE file in the program folder), a service named Everything is created (as expected).

New named instances (everything64.exe -instance "Something" command-line) don't detect the already running service and try to create a new one instead of re-using the existing one.

I (think I) get why this is done -- possible conflicts with 1.4 -- so something to keep in the back of your mind for later.

[tuska]

Hi,
Not here.

Everything 1.5.0.1358a (x64) ... main instance ...
C:\Everything\Everything64.exe
C:\Everything\NO_ALPHA_INSTANCE

C:\Everything\Everything_PRIVAT\Everything64.exe -instance "PRIVAT" -startup
C:\Everything\Everything_PRIVAT\NO_ALPHA_INSTANCE

C:\Everything\Everything_PRIVATE\Everything64.exe -instance "PRIVATE" -startup
C:\Everything\Everything_PRIVATE\NO_ALPHA_INSTANCE

C:\Everything\Everything_DRIVE-C\Everything64.exe -instance "DRIVE-C" -startup
C:\Everything\Everything_DRIVE-C\NO_ALPHA_INSTANCE

C:\Everything\Everything_INSTANT\Everything64.exe -instance "Instant"
C:\Everything\Everything_INSTANT\NO_ALPHA_INSTANCE

The main instance and sub-instances use only 1 Everything Service together with the name "Everything".

If you keep several instances in several folders separately,
it could be that the file "NO_ALPHA_INSTANCE" is not present in one of them.

_____________________________________________________________________________________
14.10.2021: Everything-1.5.0.1280a removed requirement for multiple Everything Service instances.

[void]

it could be that the file "NO_ALPHA_INSTANCE" is not present in one of them.

I think tuksa is on to something here.

Only one Everything Service needs to be installed for Everything 1.5.



When the Everything Service is started with -svc it will first check for the NO_ALPHA_INSTANCE file.

When NO_ALPHA_INSTANCE is present:
The Everything Service uses the pipe: \\.\PIPE\Everything Service

When NO_ALPHA_INSTANCE is not present:
The Everything Service uses the pipe: \\.\PIPE\Everything Service (1.5a)



The Everything Service will never use a custom instance name for the service named pipe.
It's either (unnamed) or (1.5a)

-There's some weird leftover -instance support with -svc which I'll remove in the next alpha update.
-instance doesn't do anything with -svc



When the Everything Search Client is started it will first check for the NO_ALPHA_INSTANCE file.

When NO_ALPHA_INSTANCE is present:
Connect to the Everything Service with the pipe: \\.\PIPE\Everything Service
The Everything Service is installed as: Everything

When NO_ALPHA_INSTANCE is not present:
Connect to the Everything Service with the pipe: \\.\PIPE\Everything Service (1.5a)
The Everything Service is installed as: Everything (1.5a)



The Everything Search Client will never connect with a custom instance name for the service named pipe.
It's either (unnamed) or (1.5a)



Please try reinstalling the Everything Service with NO_ALPHA_INSTANCE present in the same location as all your Everything.exe files.
(Tools -> Options -> General -> Everything Service)

[NotNull]

I now realize that I left out a crucial detail: the instances are started through Everything64.exe in another folder.

So regular Everything on this system is started through:

"C:\Program Files\Everything 1.5a\Everything64.exe"

And the "C:\Program Files\Everything 1.5a" folder contains a NO_ALPHA_INSTANCE file.


One of the other instances is started with

Code: Select all

T:\parms\Everything64.exe -instance "some name" -db "T:\parms\Settings\my db.db" -config "T:\parms\Settings\my ini.ini"

No NO_ALPHA_INSTANCE file in the T:\prarms folder
.. which will look for a service "Everything (1.5a)"


The idea was to let all Everything 1.5 instances -- named as well as unnamed -- use one single service when it is time for the official release.
If the name of that service is "Everything (1.5)" or "Everything" at that point doesn't really matter (to me).


I hope I described the idea a bit better this time ...

[tuska]

The idea was to let all Everything 1.5 instances -- named as well as unnamed -- use one single service
when it is time for the official release.
If the name of that service is "Everything (1.5)" or "Everything" at that point doesn't really matter (to me).

For me that would make a small but noticeable difference.

If there were an Everything Service called "Everything" from Everything 1.5b onwards,
then a migration would only require the following steps:

1. Search for: exact:NO_ALPHA_INSTANCE
2. Ctrl+A (mark all files)
3. Del - Yes
4. Migration DONE! ... (e.g. for all of the instances listed above)

Everything.ini - The setting alpha_instance=0 then probably requires a little more effort...

[NotNull]

I have a feeling that a future non-alpha version of Everything does not check for the presence of a NO_ALPHA_INSTANCE file or act upon it .
In that case, migration is even simpler: Do nothing!

(But just like you, I will definitely clean up these files too)

[void]

Just making a note here.

Everything 1.5.0.1359a no longer sets the -instance name when installing the service.
(or checking if the service is installed correctly)



This change may show the Everything Service as square-checked/partially installed.

Please make sure Everything Service is installed correctly:

• In Everything, from the Tools menu, click Options.
• Click the General tab on the left.
• Check Everything Service. (Please make sure this is tick-checked and not square-checked)
• Click OK.