11-10-2010
That's a significant difference all right!
What module is it using to read the drive in either? Is there any difference in readahead settings?
10 More Discussions You Might Find Interesting
1. SuSE
I recently installed SLES 10 on an x86 64bit blade server. I then installed vsftpd from the suse cds through network services; however after configuring the vsftpd.conf file, the server fails to start:
# /etc/init.d/vsftpd start
Starting vsftpd startproc: exit status of parent of... (5 Replies)
Discussion started by: dave521
5 Replies
2. Linux
Dear All,
I have two intel xeon servers running with SLES 10 on a cluster environment (Veritas Cluster 4.1 - 2 Node Cluster - Active Passive). Both the systems are having hardware RAID 1 for OS disk. Both the systems are having DVD writer.
I would like to take the OS backup on DVD which can... (0 Replies)
Discussion started by: jumadhiya
0 Replies
3. UNIX for Advanced & Expert Users
Hi,
I would like to programmatically find if given OS is SLES 10 / RHEL 3/.RHEL 4/RHEL5 etc ..
For this do we have any library call/sys call? Or should we use any sys. structure which would give me detailed info. Share me if you have any pointers.
Thanks in advance
- Krishna (1 Reply)
Discussion started by: krishnamurthig
1 Replies
4. SuSE
YaST no longer works on one of our SUSE Linux Enterprise Server 10, When I issue “Yast” I get the following error messages
"warning: the ncurses frontend is installed but does not work"
"You need to install yast2-ncurses to use the YaST2 text mode interface"
Can you help? please (2 Replies)
Discussion started by: hassan1
2 Replies
5. SuSE
Is there any doc/procedure to set up VNC on SLES 11 to connect from windows clients?? (1 Reply)
Discussion started by: s_linux
1 Replies
6. SuSE
I just upgraded sles 10 sp2 to sles 11. Apache is running on the server. apache needs to contact the backend server which is weblogic. But once I upgrade to sles 11 i cant able to telnet or ping to the backend (weblogic)server. I checked firewall and is disabled. Any ideas. Thanks. (4 Replies)
Discussion started by: s_linux
4 Replies
7. SuSE
Hi,
I am using
SUSE Linux Enterprise Server 11 (x86_64), PATCHLEVEL = 0 as NIS server.
All client is having SUSE Linux Enterprise Desktop 11 (x86_64), PATCHLEVEL = 0.
All system are configured to work in GUI.
When NIS user say 'a' locks system, and user 'b' wants to login to the same system... (1 Reply)
Discussion started by: sachingujrathi
1 Replies
8. SuSE
Hello,
I would like to change a password of a user to a simple one but when i try to add an only lowercase pass i get the error:
Weak password: too short.
Try again.
You can now choose the new password.
A valid password should be a mix of upper and lower case letters,
digits, and... (2 Replies)
Discussion started by: @dagio
2 Replies
9. SuSE
Hello,
I would like ask if SLES 10, PATCHLEVEL 4 is supporting sha512 password encryption algorithm??
Many thanks,
Stan (0 Replies)
Discussion started by: brusell
0 Replies
10. SuSE
Hello All,
I'm trying to configure a SLES 10.3 machine as our Zypper server. I created the zypper directories with all the RPMs, made the directory structure accessible over HTTP but I'm stuck at the final stage: createrepo.
Looks like 'createrepo' is not present on this version :confused:
... (3 Replies)
Discussion started by: satish51392111
3 Replies
LEARN ABOUT CENTOS
systemd-readahead-collect.service
SYSTEMD-READAHEAD-REPLAY.SERVICE(8) systemd-readahead-replay.service SYSTEMD-READAHEAD-REPLAY.SERVICE(8)
NAME
systemd-readahead-replay.service, systemd-readahead-collect.service, systemd-readahead-done.service, systemd-readahead-done.timer, systemd-
readahead - Disk read ahead logic
SYNOPSIS
systemd-readahead-replay.service
systemd-readahead-collect.service
systemd-readahead-done.service
systemd-readahead-done.timer
/usr/lib/systemd/systemd-readahead/systemd-readahead [OPTIONS...] COMMAND [DIRECTORY | FILE]
DESCRIPTION
systemd-readahead-collect.service is a service that collects disk usage patterns at boot time. systemd-readahead-replay.service is a
service that replays this access data collected at the subsequent boot. Since disks tend to be magnitudes slower than RAM, this is intended
to improve boot speeds by pre-loading early at boot all data on disk that is known to be read for the complete boot process.
systemd-readahead-done.service is executed a short while after boot completed and signals systemd-readahead-collect.service to end data
collection. On this signal, this service will then sort the collected disk accesses and store information about them in /.readahead.
Normally, both systemd-readahead-collect.service and systemd-readahead-replay.service are activated at boot so that access patterns from
the preceding boot are replayed and new data collected for the subsequent boot. However, on read-only media where the collected data cannot
be stored, it might be a good idea to disable systemd-readahead-collect.service.
On rotating media, when replaying disk accesses at early boot, systemd-readahead-replay.service will order read requests by their location
on disk. On non-rotating media, they will be ordered by their original access timestamp. If the file system supports it,
systemd-readahead-collect.service will also defragment and rearrange files on disk to optimize subsequent boot times.
OPTIONS
systemd-readahead understands the following options:
-h, --help
Prints a short help text and exits.
--max-files=
Maximum number of files to read ahead. Only valid for thes collect command.
--file-size-max=
Maximum size of files in bytes to read ahead. Only valid for the collect and replay commands.
--timeout=
Maximum time in microseconds to spend collecting data. Only valid for the collect command.
COMMANDS
The following commands are understood by systemd-readahead:
collect [DIRECTORY]
Collect read-ahead data on early boot. When terminating, it will write out a pack file to the indicated directory containing the
read-ahead data.
replay [DIRECTORY]
Perform read-ahead on the specified directory tree.
analyze [FILE]
Dumps the content of the read-ahead pack file to the terminal. For each file, the output lists approximately how much will be read
ahead by the replay command.
SEE ALSO
systemd(1)
systemd 208 SYSTEMD-READAHEAD-REPLAY.SERVICE(8)