On Fri, 2002-12-27 at 03:56, Colin Jenkins wrote: > Hello Jack, > > Friday, December 27, 2002, 3:11:36 PM, you wrote: > of people is going to get upset > > >> > > >> > usually this sort of error is due to differing environment or > >> > permissions. If it's a user's crontab ($crontab -e) then you need to su > >> > to that user and debug from there. If it's root's crontab (#vi > >> > /etc/crontab) then make sure root can run it from command line. > >> > > >> > Another possibility is that the network is fine when you're debugging, > >> > but congested by other traffic when your cron job runs. Try doing > >> > something less sensitive to network issues, like rsync'ing to a temp > >> > directory a couple of times, then tar'ing that temp directory to the > >> > tape. > >> > > >> > this is really starting to bug me, > I tried the script below, runs from command line or clicking on icon, > but when run as cron job (as root) , it copies 2.9Mb and stops. there > are no errors in cron logs. AFIK it's not a network problem as no one else was > using it. > Unless I'm missing something obvious, it must be a bug with cron.
I have trouble imagining that, but samba not acting like I expected is a daily occurrence :-) > I have tried the same with 2 different networks, with the same > results. I'm using samba 2.2.6 on mdk9 with all the latest updates > > #!/bin/sh > cp -rpuv /mnt/windows /mnt/hal Anything in the logs? Griping from the NIC driver or filesystem or shorewall? Permissions on NTFS should throw an error via smbmount, I would think... it would certainly produce an error in the Windows security log. actually, humor me -- try removing the u flag from your copy statement and see what that does. -- Jack Coates Monkeynoodle: A Scientific Venture...
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
