[SourceJammer-users] Re: Bugs?
Brought to you by:
robertmacgrogan
From: Robert M. <rob...@ya...> - 2002-03-12 16:01:40
|
Hi Daniele. --- "dan...@a-..." <dan...@a-...> wrote: > Hi Robert > > I can say I started to use SJ in real life now, even > if something isn't > clear to me yet. > One weird thing I notice is that when I start the > client as a normal > user (when I'm root I don't have any problems of > course), and I ckout > and ckin files, the clients returns error message: > Can't find or access > local file. This is due certainly to permission > problems that I'll fix > it by myself...don't worry about that...but, even > though this message > is given, the file is correctly changed and checked > in; I could even > ignore it and go on with my work, but I think better > to tell you about > it so that you can see if some review is needed. I think the problem probably occurs when your non-root user tries to access files "owned" by your root user. This is probably the "source.jam" file, which contains information on what version of each file is contained in a directory. Every time you add, get, check in, or check out, the source.jam file is accessed. If the gui does not find a source.jam in a directory it creates one. My guess is that you are performing some action on a directory as root that is creating a source.jam file. Then you log in as a user and that user cannont access the source.jam file because it is owned by root. > > Another thing. > I told you that on some machine I have to run the > command line client, > since that machine has not any graphical tool. > If I open a connection to that machine from a > graphics provided one, > the sj_gui starts, but it's extremely slow and > cannot work with it; but > the same thing DOESN'T happen with other graphical > tools started on > remote but displayed on the local one (X-Eyes for > instance); do you > think it could be a problem on SJ-side, or it's just > that the tool is > too heavy to be guided through the net? I haven't tried to do this with Linux and x-windows, but I have run the SJ GUI using terminal services and Windows and it runs fine. What are the specs of the remote server you are trying to run the SJ GUI on? I could be that it does not have enough RAM. Java Swing (which the GUI is built on) requires 128 MB. Looks like you really have got your problems straightened outh, though. --Rob > > Thank you > > Daniele > > > __________________________________________________ Do You Yahoo!? Try FREE Yahoo! Mail - the world's greatest free email! http://mail.yahoo.com/ |