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

Running profile-sync-daemon #2488

Closed
cefn opened this issue Mar 20, 2016 · 3 comments
Closed

Running profile-sync-daemon #2488

cefn opened this issue Mar 20, 2016 · 3 comments
Labels

Comments

@cefn
Copy link

cefn commented Mar 20, 2016

Tried to install and launch profile-sync-daemon since I'm now running from my USB drive (My Lexar S45 128GB on Toshiba Chromebook 2 now seems to survive a sleep cycle).

If I launch with

/usr/bin/profile-sync-daemon sync &

I get the following error...

ERROR: Cannot find XDG_RUNTIME_DIR which should be set by systemd

I don't know if that means it's actually a systemd dependency, (which I gather can't be met), or if there's some other way to satisfy the need for a XDG_RUNTIME_DIR value. Any ideas? It would make my browsing much more efficient to be running in tmpfs.

There's some detailed information about profile-sync-daemon at https://wiki.archlinux.org/index.php/Profile-sync-daemon

@DennisLfromGA
Copy link
Collaborator

@cefn,

Looking at the author's github repo here, it looks like they won't be supporting anything other than 'systemd' going forward:

  • With the release of psd version 6.x I will no longer be supporting alternative init systems such as upstart and openrc.

-DennisL

@cefn
Copy link
Author

cefn commented Mar 20, 2016

That seems fair enough, but I was assuming that systemd was just doing the job of starting up the program and providing a folder, so if I chose to launch it myself, then I could satisfy it's requirements by pointing to appropriate directories.

Was thinking of pointing $XDG_RUNTIME_DIR to something in /var/run perhaps, as described at... http://unix.stackexchange.com/questions/162900/what-is-this-folder-run-user-1000

However, I'm unfamiliar with the conventions and permissions which such a startup configuration should have in order for programs to behave themselves, and how this interacts with Chrome or Crouton chroot filesystem structures and conventions.

Perhaps the dependency on systemd is deeper than I recognise, though.

@DennisLfromGA
Copy link
Collaborator

@cefn - I don't know if you've seen this PR #2474 but it offers some hope I think.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants