search for: claco

Hi In my enterprise we have our php web projects in a Linux server. We are using Samba shared folders to access the source code. The problem that I'm having is that I need a mechanism to control de access of the files so that 2 developers working on the same project can't open the same file for writing at the same time. The only thing that I found for this is using Frontpage

> ----- Original Message ----- > From: sthaug@nethelp.no > To: freebsd-security@dfmm.org > Subject: Re: [fbsd] HEADS UP: FreeBSD 5.3, 5.4, 6.0 EoLs coming soon > Date: Wed, 11 Oct 2006 18:20:18 +0200 (CEST) > > > > I realize that resources to keep chasing this stuff are in > > limited supply, but if you solicit the opinion of the community, > > I'd

I've had ipf working on a few 5.3 servers for quite awhile. Not too long ago some developers had to do some coding work and were coming from dynamic IP's. I (reluctantly) opened up SSH to the world. Immediately I started seeing the attacks where bots of some sort would try to break in with a variety of different users. So, I (thought) I closed it up again and told the developers to use a

I've been tinkering with this for days now and I can't seem to figure out the problem. I know there were problems < 3.0.8 with robocopy and a few other programs, but even after upgrading, I'm still have a similiar issue with related errors. I'm running Samba 3.0.10 on FreeBSD pointed to an NT4 DC. I'm trying to copy files over to one of it's shares via robocopy from

I'm still battling the dreaded "ERROR 5 (0x00000005)" error when trying to robocopy files from a W2K box to Samba 3.0.7 on FreeBSD. I've been fighting this since Samba 2.2.8 and the upgrade hasn't fixed it for me despite the entries in the changlelog. Now here's the strange part. If robocopy is sending NEW files, files which are on W2K but not on the Samba box, the copy