[comp.sys.ncr] 020101 CRON under 010300

nigel@cmsfl@labtam.oz (Nigel Harwood) (04/09/90)

I don't know whether you saw a previous message I posted
about cron core dumping under 010300 ?  Don't worry, seems
like no one else did either 8-)

Well NCR here can't offer me any help except to upgrade which
is impossible at present.

As I'm fairly desperate for a solution I was wondering if
it would be feasible to use the cron from one of our 020101
systems after hitting it with 'mcs'.

We already have the /etc/zoneinfo stuff on the 010300 systems
so that wouldn't be a problem.

Anyone know of any other objections ?

-- 
<<<<<<<<<<<<<<<<<<<<<<<  Nigel Harwood  >>>>>>>>>>>>>>>>>>>>>>>>>
<< Post:  Coles Myer Ltd, PO Box 2000 Tooronga 3146, Australia >>
<< Phone: +61 3 829 6090      E-mail: nigel%cmsfl@labtam.oz.au >>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

nigel@cmsfl@labtam.oz (Nigel Harwood) (05/07/90)

I recently posted a problem regarding cron core dumping
under 010300.

I received no responses from the NET (or my local NCR
support).

I decided I had to do something, so posted a proposal to
use the 020101 version of cron under 010300 (with the
correct time zone stuff and run through mcs).

Having received no unfavourable responses (in fact none
again, sigh ... ) I assumed this was probably okay.

It has been running on one of our systems for a week
or so which probably indicates its okay but I will
leave it for a bit longer to be safe.

For anyone who is interested in the outcome I will
post the results of my experiment.  Although I am
beginning to suspect that no-one really cares ;-(.

Oh, BTW, does anyone know if I will need licensing permission
to overcome my problem in this way ?

Regards
-- 
<<<<<<<<<<<<<<<<<<<<<<<  Nigel Harwood  >>>>>>>>>>>>>>>>>>>>>>>>>
<< Post:  Coles Myer Ltd, PO Box 2000 Tooronga 3146, Australia >>
<< Phone: +61 3 829 6090      E-mail: nigel%cmsfl@labtam.oz.au >>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>