Article View: comp.sys.next.sysadmin
Article #1563Re: 3.0: what gives with cron
From: Mark Crispin
Date: Sat, 26 Sep 1992 20:54
Date: Sat, 26 Sep 1992 20:54
12 lines
1185 bytes
1185 bytes
I encountered the same problem with cron in 3.0. I'll bet you're piping your backup data to rsh, eh? Sorry, bunkie; rsh in 3.0 does not work under cron. I spent several hours on this problem and fairly conclusively proved that rsh just dies silently when it is run under cron. Don't think of trying an old rsh from 2.1 and seeing if that will work; you'll get a no such host name error. I reported this bug to NeXT. Judging from past performance, we can expect to see this fixed sometime in 1995. After all, 3.0 finally fixes some bugs we reported in 0.8 days.
Technical Details
Message-ID:
<MS-C.717540884.662824084.mrc@Tomobiki-Cho.CAC.Washington.EDU>Path:
arc1-ca.pugleaf.net!sparky!uunet!think.com!rpi!uwm.edu!ogicse!news.u.washington.edu!newsShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!think.com!rpi!uwm.edu!ogicse!news.u.washington.edu!news From: mrc@Tomobiki-Cho.CAC.Washington.EDU (Mark Crispin) Newsgroups: comp.sys.next.sysadmin Subject: Re: 3.0: what gives with cron Message-ID: <MS-C.717540884.662824084.mrc@Tomobiki-Cho.CAC.Washington.EDU> Date: 26 Sep 92 20:54:44 GMT Article-I.D.: Tomobiki.MS-C.717540884.662824084.mrc Sender: news@u.washington.edu (USENET News System) Organization: University of Washington Lines: 12 In-Reply-To: <19qhh7INN1df@network.ucsd.edu> Content-Type: TEXT/PLAIN; charset=US-ASCII To: alevine@ucsd.edu Mime-Version: 1.0