Re: Li-f-e 13.1

Hi

On Tue, 10 Dec 2013 12:44:20 +0530, Jigish Gohil
<[email protected]> wrote :
> > Same for epoptes here. But maybe I'm just missing documentation?
> > fbreader also had a new version, that currently does not compile
> > with the latest Gnome :-( but we can go with the old version imho.
> >
> On the client  /etc/default/epoptes-client SERVER=3DyourepoptesserverIP
>=20
> then epoptes-client -c
>=20
> On the server, the user running epoptes must be in epoptes group.
>=20
> From: http://www.epoptes.org/installation
>=20
> We have new maintainer of epoptes packages:
> https://build.opensuse.org/home?user=3Dlbssousa not sure he is on this
> list :)

OK, so below is what I tried so far to get epoptes up and running.=20

Please note that this machine is a real openSUSE 13.1 installation with
the Education repository added as installation source - and no LTSP
client.

-----------------------[snipplet from my tries on openSUSE 13.1]

lars@travel:~> id
uid=3D16058(lars) gid=3D50(suse)
Gruppen=3D50(suse),7(lp),10(wheel),14(uucp),16(dialout),17(audio),33(video)=
,42(trusted),71(ntadmin),100(users),481(epoptes),502(teachers)
lars@travel:~> cat /etc/default/epoptes
# The port where the server will be listening on, and where the client
# will try=20
# to connect to. For security reasons it defaults to a system
# port, 789.=20
PORT=3D789

# Epoptes server will use the following group for the communications
# socket.=20
# That means that any user in that group will be able to
# launch the epoptes UI=20
# and control the clients.
SOCKET_GROUP=3Depoptes

lars@travel:~> cat /etc/default/epoptes-client
# The server where epoptes-client will be connecting to.
# If unset, thin client user sessions running on the server will try to
# connect=20
# to "localhost", while thin client root sessions and fat or
# standalone clients=20
# will try to connect to "server".
# LTSP automatically puts "server" in /etc/hosts for thin and fat
# clients,=20
# but you'd need to put "server" in DNS manually for
# standalone clients.=20
SERVER=3Dlocalhost

# The port where the server will be listening on, and where the client
# will try=20
# to connect to. For security reasons it defaults to a system
# port, 789.=20
PORT=3D789

# Set Wake On LAN for devices that support it. Comment it out to
# disable it.=20
WOL=3Dg

lars@travel:~> sudo su -
travel:~ # epoptes-client=20
travel:~ # echo $?
0
travel:~ # exit
lars@travel:~> epoptes=20
/usr/lib/python2.7/site-packages/epoptes/ui/gui.py:83: GtkWarning:
Unknown property: GtkMenu.ubuntu-local
self.wTree.add_from_file('epoptes.ui') Connection with epoptes failed:
An error occurred while connecting: 2: No such file or directory.

-----------------------[/snipplet from my tries on openSUSE 13.1]

=46rom a strace, I see that the epoptes-client wants to
create/connect to a socket in /var/run/epoptes - this directory (and
file) does not exist. If neither the client nor the server creates it
automatically, it should become part of the RPM.

The epoptes client also tries to stat /usr/share/ltsp/ltsp_config -
which does not exist on my machine. I guess this is the main reason on
a standard machine (note: no LTSP!) that epoptes can not be executed.=20

...any help is welcome!

Regards,
Lars
-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]