LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - General (https://www.linuxquestions.org/questions/linux-general-1/)
-   -   privoxy/samba problems (https://www.linuxquestions.org/questions/linux-general-1/privoxy-samba-problems-233405/)

adaptor 09-21-2004 12:05 PM

privoxy/samba problems
 
So, I'm developing a webapp for work and I've been working on it from many different computers, both windows and linux. I set up a webserver, greebo, and set up a samba share on it so I could compile directly to it from the workstations. Now, this is all working fine except yesterday I tried to mount the share from my main workstation, wintermute, for the first time and got some very weird results. On the webserver the are some softlinks that as far as samba's concerned I'm allowed to follow, and this works from every computer except my workstation (btw, both greebo and wintermute are running 32-bit suse 9.1, fully updated). Unable to cd into my work directory I did ls -al and saw that the links were owned by privoxy.users and the other files were owned by privoxy.privoxy! I'd never heard of privoxy (www . privoxy . org) before so I called over my officemate who explained what it was, though couldn't explain how it came to be installed on wintermute and owning my samba shares. So, I uninstalled it to no avail. I removed the privoxy user and the privoxy group. There is no privoxy user/group on the webserver and it doesn't have that software installed. This is what I get now:
Code:

wintermute:/mnt # mount -t smbfs -o username=xxx //greebo/tomcat /mnt/tomcat
wintermute:/mnt # cd tomcat/
wintermute:/mnt/tomcat # l
total 4
drwxr-xr-x  1 root root  4096 2004-09-15 08:37 ./
drwxr-xr-x  5 root root  120 2004-09-08 12:23 ../
drwxr-xr-x  1  100  101    0 2004-09-01 09:41 balancer/
lrwxrwxrwx  1  100 users  33 2004-09-14 09:10 catalina.out -> /var/log/tomcat/base/catalina.out
lrwxrwxrwx  1  100 users  12 2004-09-02 09:58 qci -> /storage/qci
drwxr-xr-x  1  100  101    0 2004-08-31 09:32 ROOT/

So, why is this a problem? Because (which, btw, is what happened before I uninstalled privoxy):
Code:

wintermute:/mnt/tomcat # more catalina.out
catalina.out: No such file or directory
wintermute:/mnt/tomcat # cd qci
bash: cd: qci: No such file or directory

Now, I can repeat all these steps from another suse 9.1 (or RH, slack, etc) box and everything works fine.
Code:

luggage:/ # mount -t smbfs -o username=xxx //greebo/tomcat /mnt/
luggage:/ # l /mnt
total 731
drwxr-xr-x    1 root    root        4096 Sep 14 09:10 ./
drwxr-xr-x  24 root    root          576 Sep  7 13:26 ../
drwxr-xr-x    1 root    root        4096 Aug 31 09:32 ROOT/
drwxr-xr-x    1 root    root        4096 Sep  1 09:41 balancer/
-rwxr-xr-x    1 root    root      731116 Sep 14 09:05 catalina.out*
drwxr-xr-x    1 root    root        4096 Sep 14 09:09 qci/

Same is true with windows. I'm pretty confident that the problem is with wintermute, but any ideas on how to remedy this problem? Why it happened in the first place? I'm out of ideas and am ready to give up as it's taking away from my development time and I do have other machines to work from. Having said that, I hate to walk away not knowing why and how to fix it as I'm sure this won't be the last time I want to do this...
Thanks,
m

ps: 100 was user privoxy and 101 was group privoxy...
pps: I tried mounting another computers samba share and that worked fine, no privoxy user/group.... Of course, this is after I uninstalled privoxy and removed the user/group so maybe samba has a memory or something? I did uninstall and reinstall samba as well. No difference...

secesh 09-21-2004 12:29 PM

you have colorized readouts -- the red means the symbolic link is bad.

--check your permissions, starting from the top, check each directory, and then the actual
file to insure the permissions are correct, and that you should have access.

do this on the real file, not the syn link.

adaptor 09-21-2004 12:59 PM

Quote:

Originally posted by secesh
you have colorized readouts -- the red means the symbolic link is bad.
Thanks, but I knew that... It also isn't bad, only from this one machine.

Quote:

--check your permissions, starting from the top, check each directory, and then the actual
file to insure the permissions are correct, and that you should have access.

do this on the real file, not the syn link.

I've done that previously. All relevant files/directories are owned by tomcat.users with permissions set to 775.
Thanks,
m


All times are GMT -5. The time now is 04:28 PM.