Re: Package update problem...{***SOLVED***}

2016-12-14 Thread Mark Neidorff
On Wednesday, 12/14/16 11:06:52 AM Lisi Reisz wrote: > On Tuesday 13 December 2016 19:23:49 Mark Neidorff wrote: > > On Monday, 12/12/16 11:49:01 PM kamaraju kusumanchi wrote: > > > On Mon, Dec 12, 2016 at 12:50 PM, Mark Neidorff wrote: > > > > Sorry to seem stubborn, but I don't consider giving a

Re: Package update problem...{***SOLVED***}

2016-12-14 Thread Lisi Reisz
On Tuesday 13 December 2016 19:23:49 Mark Neidorff wrote: > On Monday, 12/12/16 11:49:01 PM kamaraju kusumanchi wrote: > > On Mon, Dec 12, 2016 at 12:50 PM, Mark Neidorff wrote: > > > Sorry to seem stubborn, but I don't consider giving a user account full > > > administrative access acceptable, ev

Re: Package update problem...{***SOLVED***}

2016-12-13 Thread Mark Neidorff
On Tuesday, 12/13/16 02:34:00 PM Henning Follmann wrote: > > Good news! I solved the problem. This solution came from the openSUSE > > forums... (just giving credit where credit is due) > > > > As root, in the folder /etc/cron.* (where * is either daily, hourly, etc. > > depending on how often y

Re: Package update problem...{***SOLVED***}

2016-12-13 Thread Henning Follmann
> > > Good news! I solved the problem. This solution came from the openSUSE > forums... (just giving credit where credit is due) > > As root, in the folder /etc/cron.* (where * is either daily, hourly, etc. > depending on how often you want the check to take place): > > 1. Create a file cal

Re: Package update problem...{***SOLVED***}

2016-12-13 Thread Mark Neidorff
On Monday, 12/12/16 11:49:01 PM kamaraju kusumanchi wrote: > On Mon, Dec 12, 2016 at 12:50 PM, Mark Neidorff wrote: > > Sorry to seem stubborn, but I don't consider giving a user account full > > administrative access acceptable, even if there is only one user on the > > system. My reasoning is th