Skip to content
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

zoxide can't access it's datase (when exportet to server) #864

Open
MartyMcFlyInTheSky opened this issue Aug 2, 2024 · 1 comment
Open

Comments

@MartyMcFlyInTheSky
Copy link

MartyMcFlyInTheSky commented Aug 2, 2024

I'm using zoxide on my local laptop running ubuntu where it works like a charm. However, since I'm hopping to our production machines frequently I want to make use of zoxide there, so I'm cloning my dotfiles containing the zoxide binary to the servers in /tmp/dotfiles. Basically this becomes my new XDG_HOME. The zoxide binary lives in /tmp/dotfiles/.local/bin/ and since zoxide respects the XDG norm it correctly creates a database file in $XDG_DATA_HOME/zoxide which expands to /tmp/dotfiles/.local/share/zoxide . Everything looks fine so far.

However, I noticed that zoxide fails to read anything from the database. Using zi to access the list will always yield
zoxide: no match found
even though I should be inserting entries with z...

I checked permissions on the db file and they seem fine:
-rw-r--r-- 1 process process 12 Aug 2 09:56 db.zo

So there's read and write permission for the process user which is the one I'm using. Still, one oddity is that on my local machine (Ubuntu), the permissions are:

-rw-rw-r-- 1 myuser myuser 2310 Aug 2 11:43 db.zo

So group has write permissions as well. Idk how important this is, I think write from user should do it?

In summary, zoxide has the right perception of where the file is (it creates it at the right spot at least). But then it doesn't retrieve the data correctly or save it. Again, locally everything works as expected.

We're running RHEL 9.2 on these servers.

@MartyMcFlyInTheSky
Copy link
Author

Update: It now seems to work in some conditions. I haven't changed a thing. Still kinda confused why this appeared. I will test for another 1-2 weeks and then update the status of this ticket.

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

No branches or pull requests

1 participant