Hi all! I'm looking for a method of doing the following, given that I'm taking care of a network with a Samba 3.0.6 box (running Mandrake 10.0) acting as a PDC for about 15 W2K boxes: . There is a share full of program files and data files on the Samba box . These files are currently synchronized at logon - all movement is from the server to the clients via a logon script using XCOPY /D I want to engineer a solution that would allow updates of the share to have changes propagated out to clients as the share is updated without the users being made aware. Essentially, the software vendor is demanding that everyone run their software from the network share as to ensure consistency, but I hardly think a 300 MB application with 15 MB (!!) executables (about 8 of them) is really suitable for being "deployed" in that fashion. All comments appreciated! Best regards, Chris
>everyone run their software from the network share as to ensure consistency, >but I hardly think a 300 MB application with 15 MB (!!) executables (about 8 >of them) is really suitable for being "deployed" in that fashion. > >Try a 1.1GB app with the main executable being 131MB and run by 60+ users at once. That really is the best way to run this particular app (Pro/Engineer) as that way the config files all point to the same license server and other important file paths. If you ever have to run around and fix it you either change it once and it just works or you change it, script a push to all the clients, and then run around fixing the ones that didn't work for some reason, which assumes the users have permission to replace system executables. I'll pick the network option personally. -- Paul Gienger Office: 701-281-1884 Applied Engineering Inc. Information Systems Consultant Fax: 701-281-1322 URL: www.ae-solutions.com mailto: pgienger@ae-solutions.com ----------------------------------------- The information contained in this message is privileged and intended only for the recipient names. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.
Chris Ricks wrote:>Hi all! > >I'm looking for a method of doing the following, given that I'm taking care >of a network with a Samba 3.0.6 box (running Mandrake 10.0) acting as a PDC >for about 15 W2K boxes: > >. There is a share full of program files and data files on the Samba box >. These files are currently synchronized at logon - all movement is from the >server to the clients via a logon script using XCOPY /D > >I want to engineer a solution that would allow updates of the share to have >changes propagated out to clients as the share is updated without the users >being made aware. Essentially, the software vendor is demanding that >everyone run their software from the network share as to ensure consistency, >but I hardly think a 300 MB application with 15 MB (!!) executables (about 8 >of them) is really suitable for being "deployed" in that fashion. > >All comments appreciated!I would say that your vendor is being unreasonable, and that you are correct to want to run these locally. A few questions to think about : How often do you update the application ? If it's only every few months, then there's no problem. Do you ever do it while users are working ? Well you shouldn't be ! And what does the vendor propose to do about the problem of changing a binary whilst it is in use ? Having said that, I have done in-place upgrades on Unix systems by MOVING the original file and slipping the new one into place - if it's in use then the system will continue to use the old file (referenced by inode no, not file name) until it is closed. Do you have (or do you ever expect to have, any remote workers ? If so then there is no way (even on Broadband/ADSL) that you want users sucking that sort of file size down the pipe. One way of dealing with the issue is to make all the users log out and back in again when you upgrade. Another might be to run a scheduled task that periodically does an XCOPY, but then you'll run into problems of the program crashing when you change the binary running (or more likely a file in use error). Simon -- Simon Hobson MA MIEE, Technology Specialist Colony Gift Corporation Limited Lindal in Furness, Ulverston, Cumbria, LA12 0LD Tel 01229 461100, Fax 01229 461101 Registered in England No. 1499611 Regd. Office : 100 New Bridge Street, London, EC4V 6JA.
> I'm looking for a method of doing the following, given that I'm taking care...> but I hardly think a 300 MB application with 15 MB (!!) executables (about 8 > of them) is really suitable for being "deployed" in that fashion.rsync is available on both platforms and could be scripted in a bat script. Why don't you just set up an application share? I run OpenOffice and MS Office from a share that I have mapped to network drives on the clients. Also, I think if you place the files in a directory on the Linux box and then put links from each user directory to the application directory, you can even avoid mapping drives. Perms/Ownership might get tricky though. Should be safe, despite certain Samba bugs, since the link is from the user's directory to an outside directory rather than vice versa. Real time synchronization might be a good idea for a VFS module. One might even use something like that to get around having to set up re-directed folders etc. Could be a nice way to fool Windows into functioning a little more like NFS with less setup on the client side. -- ----------------------------------------------------------------- | I can be reached on the following Instant Messenger services: | |---------------------------------------------------------------| | MSN: j_c_llings@hotmail.com AIM: WyteLi0n ICQ: 123291844 | |---------------------------------------------------------------| | Y!: j_c_llings Jabber: jcllings@njs.netlab.cz | -----------------------------------------------------------------
I've read all answers, but you should do it by distribuited file systems. You should try AFS; it's easy to install and works well. uz. Il giorno ven, 01-10-2004 alle 00:50 +1000, Chris Ricks ha scritto:> Hi all! > > I'm looking for a method of doing the following, given that I'm taking care > of a network with a Samba 3.0.6 box (running Mandrake 10.0) acting as a PDC > for about 15 W2K boxes: > > . There is a share full of program files and data files on the Samba box > . These files are currently synchronized at logon - all movement is from the > server to the clients via a logon script using XCOPY /D > > I want to engineer a solution that would allow updates of the share to have > changes propagated out to clients as the share is updated without the users > being made aware. Essentially, the software vendor is demanding that > everyone run their software from the network share as to ensure consistency, > but I hardly think a 300 MB application with 15 MB (!!) executables (about 8 > of them) is really suitable for being "deployed" in that fashion. > > All comments appreciated! > > Best regards, > > Chris > >