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

Daemon does not autostart on ubuntu 18.04 #6

Open
svenjochems opened this issue Jun 16, 2018 · 2 comments
Open

Daemon does not autostart on ubuntu 18.04 #6

svenjochems opened this issue Jun 16, 2018 · 2 comments

Comments

@svenjochems
Copy link
Contributor

I'm using ubuntu 18.04.

I know this service adds a script /etc/profile.d/freekey.sh with the command "freekey start" to start the daemon on login.

I've added some log statements to this script and the file DOES seem to be executed properly at login, but the daemon does not seem to start properly.
I have to manually execute "freekey start" to start the daemon after each reboot.

I'm not sure what's causing this problem of what is different in ubuntu 18.04 compared to previous versions.

Any idea what can be causing this or what I can do to debug this further?

@chrisspen
Copy link
Owner

chrisspen commented Jun 17, 2018

Just a word of caution, I neither use nor maintain this script anymore.

That said, you should check syslog for error messages when you login. If freekey still works when you manually start it, but not automatically from the profile.d entry, then that probably means some permissions are wrong. It's also possible that Ubuntu has changed some infrastructure that no longer executes scripts upon login like it used to. I'm still on Ubuntu 16, so I haven't experienced any of those upgrade issues yet.

@chrisspen chrisspen reopened this Jun 17, 2018
@svenjochems
Copy link
Contributor Author

I've tried putting following lines directly to /etc/profile

date >> /home/sven/f.log
whoami >> /home/sven/f.log
/usr/local/bin/freekey start >> /home/sven/f.log

and the log shows

Sat Jun 16 19:27:39 CEST 2018
sven
Loaded command binding: 67 = ...
...
Loaded command binding: 96 = ...
------

So everything seems fine to me, but it just doesn't work so maybe it is indeed cause by some infrastructural changes.
But if this is not used or maintained any longer, it may be better to start looking to an alternative. Thanks anyway.

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

2 participants