Were you able to resolve your issue?
We are having a very strange issue with SolidWorks on our network,
with disappearing assemblies, menu reconfiguration, and other behind
the scenes strangeness from SolidWorks even when testing on models
that are all local to the machine. So far, we have
Guys,
Last progress, I've already updated to samba-3.0.32 (rpm-ed the tar.gz file
for 2 days :p). Now I can use vfs logging facility again and I find out that
the log is prettier than before. What still confusing me is the user cannot
directly double click their solidworks file in our production
BIG sorry,
My mistake, both the samba servers use the same smb.conf file (I have
changed the second smb.conf), except the netbios name parameter and they
both are failed to work with solidworks. Arrghh Funny thing is, although
we failed in the first double-click, the second will succeed! It
On Thu, Nov 06, 2008 at 07:16:50PM +0700, FC Mario Patty wrote:
Guys,
I think I've finally found the cause of my problem. After playing with some
parameters, I've found out that the culprit is vfs objects = full_audit
line. Is this a known bug or a new one? Currently I commented out this
Well, I'm not so techie about samba so I cannot talk much about it. But in
conjunction with my problem, right now I have this in my smb.conf:
[global]
# other parameters in here
log level = 1 vfs:0
[engineering]
path = /solid
comment = Put your data here
Hi all,
We've been using samba for a couple of years now and it always running well.
But last week we decided to shut down our windows server and move all
solidworks file into the samba server. Since then we can't save project
created by solidworks with error code shown below
Access to
On Thu, Nov 06, 2008 at 10:24:22AM +0700, FC Mario Patty wrote:
Hi all,
We've been using samba for a couple of years now and it always running well.
But last week we decided to shut down our windows server and move all
solidworks file into the samba server. Since then we can't save project
Hi Jeremy,
If what you meant was
log level = 10 vfs:0
then here are the log from samba when I tried to save (name) the file as
samba2 (sorry, it's very long):
Nov 6 12:00:39 sambaserver smbd_audit: superman|192.168.1.50|eng-pc|stat|fail
(No such file or
On Thu, Nov 06, 2008 at 12:11:14PM +0700, FC Mario Patty wrote:
Hi Jeremy,
If what you meant was
log level = 10 vfs:0
Nope, I meant a full level 10 log.
What you've given me here is output from the vfs_audit plugin,
which isn't the same thing.
Can you log a bug and attach the full log
Quoting FC Mario Patty [EMAIL PROTECTED]:
Access to \\sambaserver\solid-files\~$project1.SLDPRT was denied.
To me it sounds like a samba configuration issue. Below is an extract
(for that share that works for a client of mine:
path = full path to destination directory
valid
On Thu, Nov 6, 2008 at 1:05 PM, Jeremy Allison [EMAIL PROTECTED] wrote:
On Thu, Nov 06, 2008 at 12:11:14PM +0700, FC Mario Patty wrote:
Hi Jeremy,
If what you meant was
log level = 10 vfs:0
Nope, I meant a full level 10 log.
What you've given me here is output from the vfs_audit
Dear Jeremy,
If I change the parameter to
log level = 10
would it hogs my CPU down? I'd just changed it before all my users yell
about the server was working too slow. Thank you.
Regards,
Nope, I meant a full level 10 log.
What you've given me here is output from the vfs_audit plugin,
On Thu, Nov 06, 2008 at 02:00:35PM +0700, FC Mario Patty wrote:
Dear Jeremy,
If I change the parameter to
log level = 10
would it hogs my CPU down? I'd just changed it before all my users yell
about the server was working too slow. Thank you.
Don't do it generically. Attach from one
13 matches
Mail list logo
