
bryan at conserver
Nov 20, 2009, 5:13 PM
Post #2 of 2
(780 views)
Permalink
|
If you use 'console -s <console>' then you'll be requested a read-only connection, and you won't become read-write when the other user disconnects. The default is ask for a read-write connection. If a particular user should always have read-only access to a console, you can put them on the 'ro' list in the conserver.cf file for that console. Then they have no chance of read-write. Bryan On Fri, Nov 20, 2009 at 11:16:10AM +0100, Pearce Andy wrote: > Hi, > > I have seen the following behavior during my checks to see if > we can use conserver. > > I perform the following commands: > > 1] Open a read/write console session to a machine A. > 2] Open a second read only [spy] session to the same machine A. > 3] The first session [read/write] is exited. > 4] The second session [spy] switches to read/write. > > My question is, is it possible to make the spy sessions always be read > only ? > > Many thanks > > Andy Pearce > _______________________________________________ > users mailing list > users [at] conserver > https://www.conserver.com/mailman/listinfo/users _______________________________________________ users mailing list users [at] conserver https://www.conserver.com/mailman/listinfo/users
|