You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a salt state for tigervnc server on RHEL 8 & 9. I don't like how it is set up because the vncserver.users and /etc/systemd/system/'vncserver@:2.service' are all explicitly defined in the salt state. I was thinking we could put the user and port list in a map file and then create from that. However, I'm not sure I understand the map syntax correctly.
FYI, the vncserver.users file looks like:
:2=sid1 :3=sid2 :17=sid3
and for every number in the above file, you create in /etc/systemd/system a systemd start script named:
'vncserver@:2.service'
for example. I want to remove the association of port numbers and sids from the state file. If anyone has suggestions, I'd love to hear it
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We have a salt state for tigervnc server on RHEL 8 & 9. I don't like how it is set up because the vncserver.users and /etc/systemd/system/'vncserver@:2.service' are all explicitly defined in the salt state. I was thinking we could put the user and port list in a map file and then create from that. However, I'm not sure I understand the map syntax correctly.
FYI, the vncserver.users file looks like:
:2=sid1 :3=sid2 :17=sid3
and for every number in the above file, you create in /etc/systemd/system a systemd start script named:
'vncserver@:2.service'
for example. I want to remove the association of port numbers and sids from the state file. If anyone has suggestions, I'd love to hear it
Beta Was this translation helpful? Give feedback.
All reactions