PLEX86  x86- Virtual Machine (VM) Program
 Plex86  |  CVS  |  Mailing List  |  Download  |  Linux  |  Newsgroups

Defrag Constant HD accessing 737


Your Ad Here

Your Ad Here

In a message on 6 Apr 2006 18:27:15 -0700, wrote :

There are several 'standard' cron jobs that Linux (generally UNIX) run:

Defrag Constant HD accessing 738
hiwa Pertaining to the info within the above link I wish some of the more experienced Linux users would comment on editing, maintaining these cron files. I too have experienced this *seemingly* random once-in...

1) Daily (usually about 4AM) there are two main ones: updating the slocate database and rebuilding the whatis database

2) Weekly (generally early Sunday AM): log rotation.

The runlevels from 2-5 (or 3-5) are the full multi-user. There are several to allow for several different options: with networking, without networking, with X11 login, without X11 login. With a SysV startup, it is possible to create several sets of startup script sets, which can be selected by the selected runlevel.

Yes, this can be confusing at a certain level. The 'XServer' is the process that is directly attached to the hardware (video card, keyboard, pointing device mouse) and provides the graphics services to one or more *Clients*, which are applications that interface to the user in a graphical manner (via a 'GUI). The XServer and the Clients need not be running on the same machine, since the XServer and Clients are fully networked programs. The XServer process always runs on the hardware the user has physical contact with -- the keyboard and mouse that the user is touching with his-her hands and the screen he-she is looking at. It is possible to run more than one XServer process on the same machine, either with multiple video cards-keyboards-mice OR with multiple incarnations using the same hardware and separate *virtual* terminals, or to run an XServer as a client process in a window of a parent XServer (XNest). In the latter case, the nested XServer can be on a different physical machine that the one it is nested in (since it is also a client).

slocate expects updatedb to run each day (usually at 4AM), when this does not happen, slocate detects that the satabase file is 'old' and warns you that the information it is giving you is probably out of date. Or possibly, it is deciding that since the database is old, it is not going to use it all. You should run updatedb again.

Robert Heller -- 978-544-68 plus 133 Deepwoods Software -- Linux Installation and Administration

SAMBA automatic remounting
On Fri, 31 Mar 2006 11:13:05 -0500, John-Paul Stewart staggered into the Black Sun and...



Your Ad Here

List | Previous | Next

Defrag Constant HD accessing 738

Linux groups from Newsgroups

The #1 Usenet Provider on the Internet

Adobe Reader 7.0.5 fails in redhat 9