Menu

#1456 vnc server name problem

open
nobody
None
5
2018-11-30
2018-11-30
Pratiwir
No

I am running a vncserver service on two raspberry pi computers and getting an error in the service startup name field on the pi 3 but not the pi b. The pi 3 refuses to recognize a name field entry in the start call, the other does not. If I then remove the name field the service starts normally on the pi 3.
Both machines are using version 6.3.2.39069 armhf
The pi b is type 000e, the pi 3 is type a02082.
The script comes from here
https://gist.github.com/DaveThw/963f2b6c2670d159a88b#gistcomment-2773214
I listed in the comments at the end some minor mods to stop a hack causing errors on the pi.
I have attached the modified script called vncserver, it is the one from the pi 3 where the name has been removed, the entry used for the pi b is commented out above it. See line 53 and 52.
The script goes in /etc/init.d/ marked +x and then
update-rc.d vncserver defaults
vncpasswd
restart.
If the name field is there the service won't start
systemctl status vncserver.service
journalctl -xe
I don't think the problem is another system file, but it is possible as I purged and reinstalled tightvncserver a few times. The purge doesn't remove entries from /tmp for example, so restarts do help. It seems possible that there are slight differences in the compiled code for the two machines, so I hope it is possible to check if the name field is available on the pi 3 version of the code.
David

1 Attachments

Discussion


Log in to post a comment.

MongoDB Logo MongoDB