[Cooker] /etc/alternatives: HOW-TO ???
OK, How do I setup things up so that symlinks in /etc/alternatives are used? BTW, I am really not a newbie. jim drash <[EMAIL PROTECTED]>
[Cooker] CUPS need a logrotate file
CUPS stores logs files in /var/log/cups/access_log error_log & page_log. None of the cups packages has a logrotate.d file. This needs to be corrected prior to rc-final. jim drash <[EMAIL PROTECTED]>
Re: [Cooker] Has LM7.2 rc1 been released?
My VERSION file says: "...Ulysses-i586 20001008 15:41" My /etc/mandrake-relase file says: :... Mandrake release 7.2rc1 ..." Khawar Zia wrote: > > hey, > > I was reading through the msg's and saw someone say he is using rc1 of > lm7.2. > So is rc1 out?? > > --Khawar Zia
[Cooker] KDE "Run..." does not work but running in a terminal does
OK, more stange stuff from 7.2 rc1 (no not beta 3, rc1 is newer). When I try to run application via KDE's "Run...", I get:"Sorry - Kdesktop The program name or command cannot be found. Please correct the command and try again" But if I run the exact same command in a terminal window the commnad works. jim drash <[EMAIL PROTECTED]>
Re: [Cooker] konqueror fails constantly
I have loaded the latest kdebase, libs and qt2 stuff and I get the same exact messages!!! jdrash wrote: > > No actually I mean Linux Mandrake 7.2 rc1 (It is newer that beta 3). > > Burkhard Zombronner wrote: > > > > Am Son, 08 Okt 2000 schrieben Sie: > > > rc1 = beta1? You prolly just need to upgrade - 7.2 is up to beta 3 now plus > > > kdebase and libs have seen a few revisions since then. > > > > > > On Sun, 08 Oct 2000, you wrote: > > > > I have installed 7.2 rc1 and konqueror fails everytime. If I launch it > > > > from a console > > > > I get: > > > > fatal parsing error: unexpected end of file in line 1 > > > > fatal parsing error: error while parsing prolog in line 1 > > > > Parsing error > > > > > > > > Xcrash crashing crashRecursionCounter = 2 > > > > > > > > > > > > what gives? I can't even find what package provides konqueror. > > > > > > > > jim drash > > > > <[EMAIL PROTECTED]> > > > > No, Jason. > > > > He means KDE RC1= 1.99 > > > > regards > > > > Burkhard Zombronner
Re: [Cooker] konqueror fails constantly
No actually I mean Linux Mandrake 7.2 rc1 (It is newer that beta 3). Burkhard Zombronner wrote: > > Am Son, 08 Okt 2000 schrieben Sie: > > rc1 = beta1? You prolly just need to upgrade - 7.2 is up to beta 3 now plus > > kdebase and libs have seen a few revisions since then. > > > > On Sun, 08 Oct 2000, you wrote: > > > I have installed 7.2 rc1 and konqueror fails everytime. If I launch it > > > from a console > > > I get: > > > fatal parsing error: unexpected end of file in line 1 > > > fatal parsing error: error while parsing prolog in line 1 > > > Parsing error > > > > > > Xcrash crashing crashRecursionCounter = 2 > > > > > > > > > what gives? I can't even find what package provides konqueror. > > > > > > jim drash > > > <[EMAIL PROTECTED]> > > No, Jason. > > He means KDE RC1= 1.99 > > regards > > Burkhard Zombronner
[Cooker] konqueror fails constantly
I have installed 7.2 rc1 and konqueror fails everytime. If I launch it from a console I get: fatal parsing error: unexpected end of file in line 1 fatal parsing error: error while parsing prolog in line 1 Parsing error Xcrash crashing crashRecursionCounter = 2 what gives? I can't even find what package provides konqueror. jim drash <[EMAIL PROTECTED]>
[Cooker] cups and samba error in Beta 3
I have decided to go with cups vs. lpr I set my printing = cups line in my /etc/smb.conf and until I created a set of symbolic links to lpr-cups as lpr, etc. nothing worked. I have my Windows boxes configured as a HP III with postscript (I have an HP III) and when I did a print test from my windows box I got the raw postscript. The cups test page prints correctly. What am i doing wrong? Jim Drash <[EMAIL PROTECTED]>
Re: [Cooker] logrotate issue: runs "forever"
logrotate stills runs "forever". something is very wrong. jdrash wrote: > > I am deleting /var/log/news as I type this. It is taking a while. I > don't even run a news server and can't recall when I last looked in this > directory. > > thx for the idea I'll see it this clears things up > > jim drash > <[EMAIL PROTECTED]> > > Stefan van der Eijk wrote: > > > > > logrotate 3.3-8mdk (and 6mdk for that matter), run forever and never > > > end. I have this set up as part of my /etc/cron.dailyRunning it > > > with "-d" I get the "reading" the various configs and lots of disk I/O. > > > logrotate is taking 94% of the CPU and 20% of memory. I had not noticed > > > this until a few days ago when I had some very slow responses on the > > > console. I had 3 running versions of logrotate. Presumably, the last the > > > daily runs. > > > > > > What is going on? > > Could you give a listing of your /var/log/news directory? It made a huge > > mess of that directory on my box. To _remove_ /var/log/news (rm -rf > > /var/log/news) took about an hour... > > > > Stefan
Re: [Cooker] logrotate issue: runs "forever"
I am deleting /var/log/news as I type this. It is taking a while. I don't even run a news server and can't recall when I last looked in this directory. thx for the idea I'll see it this clears things up jim drash <[EMAIL PROTECTED]> Stefan van der Eijk wrote: > > > logrotate 3.3-8mdk (and 6mdk for that matter), run forever and never > > end. I have this set up as part of my /etc/cron.dailyRunning it > > with "-d" I get the "reading" the various configs and lots of disk I/O. > > logrotate is taking 94% of the CPU and 20% of memory. I had not noticed > > this until a few days ago when I had some very slow responses on the > > console. I had 3 running versions of logrotate. Presumably, the last the > > daily runs. > > > > What is going on? > Could you give a listing of your /var/log/news directory? It made a huge > mess of that directory on my box. To _remove_ /var/log/news (rm -rf > /var/log/news) took about an hour... > > Stefan
[Cooker] logrotate issue: runs "forever"
logrotate 3.3-8mdk (and 6mdk for that matter), run forever and never end. I have this set up as part of my /etc/cron.dailyRunning it with "-d" I get the "reading" the various configs and lots of disk I/O. logrotate is taking 94% of the CPU and 20% of memory. I had not noticed this until a few days ago when I had some very slow responses on the console. I had 3 running versions of logrotate. Presumably, the last the daily runs. What is going on? jim drash <[EMAIL PROTECTED]>
