The acquirevnc script somehow gotten out of the PATH #41

Closed
opened 2020-08-27 01:55:45 +00:00 by poweruser · 4 comments

The handler is messed up I guess. I can do acquirevnc, but some directory and the vncserver bin doesn't exist (or maybe they have gotten out of the PATH aswell)

poweruser@thunix:~$ acquirevnc
cat: '/var/lib/vnc/*': No such file or directory
/usr/local/bin/acquirevnc: line 7: [: -gt: unary operator expected
/usr/local/bin/acquirevnc: line 14: /var/lib/vnc/poweruser: No such file or directory
chmod: cannot access '/var/lib/vnc/poweruser': No such file or directory
cat: /var/lib/vnc/poweruser: No such file or directory
/usr/local/bin/startvnc: line 5: vncserver: command not found

Your port number is 5901; please note it down.
You might like to see https://wiki.thunix.net/wiki/vnc for further information.
poweruser@thunix:~$

Alright so I did some search and

poweruser@thunix:~$ ls /var/lib/vnc
ls: cannot access '/var/lib/vnc': No such file or directory
The handler is messed up I guess. I can do acquirevnc, but some directory and the vncserver bin doesn't exist (or maybe they have gotten out of the PATH aswell) ``` poweruser@thunix:~$ acquirevnc cat: '/var/lib/vnc/*': No such file or directory /usr/local/bin/acquirevnc: line 7: [: -gt: unary operator expected /usr/local/bin/acquirevnc: line 14: /var/lib/vnc/poweruser: No such file or directory chmod: cannot access '/var/lib/vnc/poweruser': No such file or directory cat: /var/lib/vnc/poweruser: No such file or directory /usr/local/bin/startvnc: line 5: vncserver: command not found Your port number is 5901; please note it down. You might like to see https://wiki.thunix.net/wiki/vnc for further information. poweruser@thunix:~$ ``` Alright so I did some search and ``` poweruser@thunix:~$ ls /var/lib/vnc ls: cannot access '/var/lib/vnc': No such file or directory ```

Actually, turns out, the install handlers wasn't quite right. This needs to get fixed, as it seems it was copy/pasted from another handler, but not updated for this task

Actually, turns out, the install handlers wasn't quite right. This needs to get fixed, as it seems it was copy/pasted from another handler, but not updated for this task
Author

Fixed, guess I should close this

Fixed, guess I should close this

It's not actually "fixed" completely yet. There's some work in ansible to do to really fix it :)

It's not actually "fixed" completely yet. There's some work in ansible to do to really fix it :)
ubergeek reopened this issue 2020-09-01 12:32:55 +00:00
Owner

I fixed the script but am yet to commit it to ansible, it needs a few further fixes.

I fixed the script but am yet to commit it to ansible, it needs a few further fixes.
This repo is archived. You cannot comment on issues.
No Milestone
No Assignees
3 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: thunix/ansible#41
No description provided.