I have a server which I'd like for people to VNC into. Now when Guy 1
logs into it, he/she must do so WITHOUT LOGGING IN (ie. there's some
kind of "default user" which it defaults to if no one says otherwise),
and then they can start apps (indeed, one must autostart - how do I do that?). Now if Guy 2 logs in, they must do the same, but they must able
to start another INSTANCE of that app (that Guy 1 started), ie. the 2
apps must run INDEPENDENT of one another (imagine guy 1 starting Firefox
and surfing site1 and guy2 starting Firefox as well and surfing site2). What's the quick way to do this?
On Sun, 06 Dec 2020 21:14:14 -0800, Groo Vee wrote:
I have a server which I'd like for people to VNC into. Now when Guy 1
logs into it, he/she must do so WITHOUT LOGGING IN (ie. there's some
kind of "default user" which it defaults to if no one says otherwise),
and then they can start apps (indeed, one must autostart - how do I do
that?). Now if Guy 2 logs in, they must do the same, but they must able
to start another INSTANCE of that app (that Guy 1 started), ie. the 2
apps must run INDEPENDENT of one another (imagine guy 1 starting Firefox
and surfing site1 and guy2 starting Firefox as well and surfing site2).
What's the quick way to do this?
Nope. There's no "quick way".
In order to ensure that the VNC sessions for "Guy 1" and "Guy 2" do not overlap, you need some way for the /system/ to distinguish between "Guy
1" and "Guy 2". And, that requires that each of them "LOG IN".
Now, the login /does not/ have to be the traditional userid/password type
of login. But, if it isn't, then you will have to develop your own login solution.
Let me repeat that: YOU will have to DEVELOP your own LOGIN SOLUTION.
On Mon, 2020-12-07, Lew Pitcher wrote:
On Sun, 06 Dec 2020 21:14:14 -0800, Groo Vee wrote:
I have a server which I'd like for people to VNC into. Now when Guy 1
logs into it, he/she must do so WITHOUT LOGGING IN (ie. there's some
kind of "default user" which it defaults to if no one says otherwise),
and then they can start apps (indeed, one must autostart - how do I do
that?). Now if Guy 2 logs in, they must do the same, but they must able
to start another INSTANCE of that app (that Guy 1 started), ie. the 2
apps must run INDEPENDENT of one another (imagine guy 1 starting Firefox >>> and surfing site1 and guy2 starting Firefox as well and surfing site2).
What's the quick way to do this?
Nope. There's no "quick way".
In order to ensure that the VNC sessions for "Guy 1" and "Guy 2" do not
overlap, you need some way for the /system/ to distinguish between "Guy
1" and "Guy 2". And, that requires that each of them "LOG IN".
Now, the login /does not/ have to be the traditional userid/password type
of login. But, if it isn't, then you will have to develop your own login
solution.
Let me repeat that: YOU will have to DEVELOP your own LOGIN SOLUTION.
You have to wonder, if Guy 1 and 2 are different people and have to do
stuff INDEPENDENTly, maybe they should be different Unix users after
all. The mechanism was invented for precisely that situation.
/Jorgen
On Mon, 07 Dec 2020 19:56:31 +0000, Jorgen Grahn wrote:[snip]
On Mon, 2020-12-07, Lew Pitcher wrote:
On Sun, 06 Dec 2020 21:14:14 -0800, Groo Vee wrote:
I have a server which I'd like for people to VNC into. Now when Guy 1
logs into it, he/she must do so WITHOUT LOGGING IN (ie. there's some
kind of "default user" which it defaults to if no one says
otherwise), and then they can start apps (indeed, one must autostart
- how do I do that?). Now if Guy 2 logs in, they must do the same,
but they must able to start another INSTANCE of that app (that Guy 1
started), ie. the 2 apps must run INDEPENDENT of one another (imagine
guy 1 starting Firefox and surfing site1 and guy2 starting Firefox as
well and surfing site2). What's the quick way to do this?
Nope. There's no "quick way".
You have to wonder, if Guy 1 and 2 are different people and have to do
stuff INDEPENDENTly, maybe they should be different Unix users after
all. The mechanism was invented for precisely that situation.
/Jorgen
So often people come and ask too specific a question instead of saying
what big picture they're trying to accomplish and asking how such is
done.
This one sounds to me like creating a multi-seat kiosk type thing but
with remote seats.
(preselected) application. A multi-seat kiosk sounds plausable, for the
OP's question.
On Tuesday, 8 December 2020 at 22:06:22 UTC+5:30, Lew Pitcher wrote:
(preselected) application. A multi-seat kiosk sounds plausable, for the
OP's question.
I'm not too sure what a "multiseat kiosk" is, but yes, that SOUNDS like *exactly* what I'm trying to achieve. How do I do it, then? I want to
connect to the server from a web VNC frontend, so I need the client IP address to somehow be the "login".
Something like this /might/ work for you.
Btw, do I need "inetd" or "xinetd"?
On 12/11/20 10:19 PM, Groo Vee wrote:
Btw, do I need "inetd" or "xinetd"?My understanding is that you need something like (x)inetd to manage the
VNC port and broker between VNC clients and VNC server processes in a
dynamic way.
I believe there must be /something/ doing that brokering. It may not
/have/ /to/ /be/ (x)inetd. But it will probably have to be something
that does much the same thing.
On Saturday, 12 December 2020 at 12:12:32 UTC+5:30, Grant Taylor wrote:
On 12/11/20 10:19 PM, Groo Vee wrote:
Btw, do I need "inetd" or "xinetd"?My understanding is that you need something like (x)inetd to manage the
VNC port and broker between VNC clients and VNC server processes in a
dynamic way.
I believe there must be /something/ doing that brokering. It may not
/have/ /to/ /be/ (x)inetd. But it will probably have to be something
that does much the same thing.
Isn't (x)inetd OBSOLETE? Didn't it get replaced by systemd or something??
Isn't (x)inetd OBSOLETE? Didn't it get replaced by systemd or something??
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 286 |
Nodes: | 16 (3 / 13) |
Uptime: | 86:32:08 |
Calls: | 6,496 |
Calls today: | 7 |
Files: | 12,099 |
Messages: | 5,277,030 |