04-23-2015
Hi
thanks for the replay.
but from showhardconf is showing nothing is faulty for me
10 More Discussions You Might Find Interesting
1. Debian
Hi All,
I am running my application on a dual cpu debian linux 3.0 (2.4.19 kernel).
For my application:
<sar -U ALL>
CPU %user %nice %system %idle
...
10:58:04 0 153.10 0.00 38.76 0.00
10:58:04 1 3.88 0.00 4.26 ... (0 Replies)
Discussion started by: jaduks
0 Replies
2. Solaris
Hi,
I found devices errors in #ioscan -En.
it is showing that soft errors = 0 and hard errors= 5.
what should i do for hard errors=0.
Thanks. (4 Replies)
Discussion started by: arjunreddy3
4 Replies
3. Shell Programming and Scripting
Hi,
I have line in input file as below:
3G_CENTRAL;INDONESIA_(M)_TELKOMSEL;SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL
My expected output for line in the file must be :
"1-Radon1-cMOC_deg"|"LDIndex"|"3G_CENTRAL|INDONESIA_(M)_TELKOMSEL"|LAST|"SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL"
Can someone... (7 Replies)
Discussion started by: shis100
7 Replies
4. UNIX for Advanced & Expert Users
Hi Experts,
I am executing "svn" checkout command through my java code on a freeBSD machine. SVN checkout gets started , but when I run "top" command on my freebsd machine, I have observed that "svn" processes are stuck in "pipewr" state.
Any pointer for this problem?
Thanks,
akash (0 Replies)
Discussion started by: akash.mahakode
0 Replies
5. BSD
Hi Experts,
I am executing "svn" checkout command through my java code on a freeBSD machine. SVN checkout gets started , but when I run "top" command on my freebsd machine, I have observed that "svn" processes are stuck in "pipewr" state.
Any pointer for this problem?
Thanks,
akash (0 Replies)
Discussion started by: akash.mahakode
0 Replies
6. Shell Programming and Scripting
I am just trying to read the password from command prompt that user should type with in 10 seconds,
I am getting "read: Illegal option -t"
#!/bin/bash ... (1 Reply)
Discussion started by: KarthikPS
1 Replies
7. Solaris
I keep getting "Too many open files" in /var/adm/messages that I do not know how to fix.
I've searched for solution on this forum and have increased the file descriptors limit but the problem persists.
The problem is happening in a solaris zone....
/var/adm/messages log example
May... (8 Replies)
Discussion started by: JT-KGY
8 Replies
8. Solaris
Hi Forum
please help me to fix M5000 Server which we were not using. now i logged to serve and foung that everything is showing as Deconfigured.
XSCF> showhardconf
SPARC Enterprise M5000;
+ Serial:BDF1051F30; Operator_Panel_Switch:Locked;
+ Power_Supply_System:Single;... (4 Replies)
Discussion started by: bentech4u
4 Replies
9. Solaris
Hi all, I have a LUN that is in "Online Busy" when I issue the dev_gestate subcommand of luxadm:
root@es088wb6:~# luxadm -v -e dev_getstate /dev/rdsk/c21t50050763090887FEd4s2
phys path = "/devices/pci@6c0/pci@1/pci@0/pci@4/SUNW,qlc@0/fp@0,0/ssd@w50050763090887fe,4:c,raw"
... (5 Replies)
Discussion started by: ludiegu
5 Replies
10. Shell Programming and Scripting
Hello.
System : opensuse leap 42.3
I have a bash script that build a text file.
I would like the last command doing :
print_cmd -o page-left=43 -o page-right=22 -o page-top=28 -o page-bottom=43 -o font=LatinModernMono12:regular:9 some_file.txt
where :
print_cmd ::= some printing... (1 Reply)
Discussion started by: jcdole
1 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)