How to optimize and accelerate your system

Discussion in general that pertains to Sabayon Linux - Must Pertain to Sabayon Linux

Moderator: Moderators

Re: How to optimize and accelerate your system

Postby pepebotella » Sun Feb 26, 2012 16:42

yuguang wrote:

Index
1. OpenRC Boot Services in Parallel


1. OpenRC Boot Services in Parallel
We will start at the beginning with boot performance. This tweak will improve the initial boot performance before kdm/gdm is loaded.
Code: Select all
nano /etc/rc.conf

Change rc_parallel="NO" to rc_parallel="YES" and rc_logger="YES" to rc_logger="NO"


*It is possible to know why aint have Change rc_parallel=?
-------------------------------------------------------------------------------------------
*reducing the numbers of tty's can I achieve some improving or it's a myth?
pepebotella
Simple Hen
 
Posts: 71
Joined: Mon Nov 02, 2009 21:26

Re: How to optimize and accelerate your system

Postby pepebotella » Thu Mar 01, 2012 13:57

pepebotella wrote:
*It is possible to know why aint have Change rc_parallel=?
-------------------------------------------------------------------------------------------
*reducing the numbers of tty's can I achieve some improving or it's a myth?


...?...
pepebotella
Simple Hen
 
Posts: 71
Joined: Mon Nov 02, 2009 21:26

Re: How to optimize and accelerate your system

Postby Fitzcarraldo » Fri Mar 02, 2012 12:15

pepebotella wrote:*It is possible to know why aint have Change rc_parallel=

Let me google that for you

pepebotella wrote:*reducing the numbers of tty's can I achieve some improving or it's a myth?

Let me google that for you too
User avatar
Fitzcarraldo
Sagely Hen
 
Posts: 7335
Joined: Sat Mar 10, 2007 5:40
Location: United Kingdom

Re: How to optimize and accelerate your system

Postby pepebotella » Fri Mar 02, 2012 14:55

I'm asking bout why I do not have Change rc_parallel=
Code: Select all
# Global OpenRC configuration settings

# Set rc_interactive to "YES" and you'll be able to press the I key during
# boot so you can choose to start specific services. Set to "NO" to disable
# this feature.
rc_interactive="YES"

# If we need to drop to a shell, you can specify it here.
# If not specified we use $SHELL, otherwise the one specified in /etc/passwd,
# otherwise /bin/sh
# Linux users could specify /sbin/sulogin
rc_shell=/sbin/sulogin

# Do we allow any started service in the runlevel to satisfy the dependency
# or do we want all of them regardless of state? For example, if net.eth0
# and net.eth1 are in the default runlevel then with rc_depend_strict="NO"
# both will be started, but services that depend on 'net' will work if either
# one comes up. With rc_depend_strict="YES" we would require them both to
# come up.
#rc_depend_strict="YES"

# rc_hotplug is a list of services that we allow to be hotplugged.
# By default we do not allow hotplugging.
# A hotplugged service is one started by a dynamic dev manager when a matching
# hardware device is found.
# This service is intrinsically included in the boot runlevel.
# To disable services, prefix with a !
# Example - rc_hotplug="net.wlan !net.*"
# This allows net.wlan and any service not matching net.* to be plugged.
# Example - rc_hotplug="*"
# This allows all services to be hotplugged
rc_hotplug="!net.*"

# rc_logger launches a logging daemon to log the entire rc process to
# /var/log/rc.log
# NOTE: Linux systems require the devfs service to be started before
# logging can take place and as such cannot log the sysinit runlevel.
rc_logger="YES"

# Through rc_log_path you can specify a custom log file.
# The default value is: /var/log/rc.log
#rc_log_path="/var/log/rc.log"

# By default we filter the environment for our running scripts. To allow other
# variables through, add them here. Use a * to allow all variables through.
#rc_env_allow="VAR1 VAR2"

# By default we assume that all daemons will start correctly.
# However, some do not - a classic example is that they fork and return 0 AND
# then child barfs on a configuration error. Or the daemon has a bug and the
# child crashes. You can set the number of milliseconds start-stop-daemon
# waits to check that the daemon is still running after starting here.
# The default is 0 - no checking.
#rc_start_wait=100

# rc_nostop is a list of services which will not stop when changing runlevels.
# This still allows the service itself to be stopped when called directly.
#rc_nostop=""

# rc will attempt to start crashed services by default.
# However, it will not stop them by default as that could bring down other
# critical services.
#rc_crashed_stop=NO
#rc_crashed_start=YES

##############################################################################
# MISC CONFIGURATION VARIABLES
# There variables are shared between many init scripts

# Set unicode to YES to turn on unicode support for keyboards and screens.
unicode="YES"

# Below is the default list of network fstypes.
#
# afs cifs coda davfs fuse fuse.sshfs gfs glusterfs lustre ncpfs
# nfs nfs4 ocfs2 shfs smbfs
#
# If you would like to add to this list, you can do so by adding your
# own fstypes to the following variable.
#extra_net_fs_list=""

##############################################################################
# SERVICE CONFIGURATION VARIABLES
# These variables are documented here, but should be configured in
# /etc/conf.d/foo for service foo and NOT enabled here unless you
# really want them to work on a global basis.

# Some daemons are started and stopped via start-stop-daemon.
# We can set some things on a per service basis, like the nicelevel.
#export SSD_NICELEVEL="-19"

# Pass ulimit parameters
#rc_ulimit="-u 30"

# It's possible to define extra dependencies for services like so
#rc_config="/etc/foo"
#rc_need="openvpn"
#rc_use="net.eth0"
#rc_after="clock"
#rc_before="local"
#rc_provide="!net"

# You can also enable the above commands here for each service. Below is an
# example for service foo.
#rc_foo_config="/etc/foo"
#rc_foo_need="openvpn"
#rc_foo_after="clock"

# You can also remove dependencies.
# This is mainly used for saying which servies do NOT provide net.
#rc_net_tap0_provide="!net"

##############################################################################
# LINUX SPECIFIC OPTIONS

# This is the subsystem type. Valid options on Linux:
# ""        - nothing special
# "lxc"     - Linux Containers
# "openvz"  - Linux OpenVZ
# "prefix"  - Prefix
# "uml"     - Usermode Linux
# "vserver" - Linux vserver
# "xen0"    - Xen0 Domain
# "xenU"    - XenU Domain
# If this is commented out, automatic detection will be attempted.
# Note that autodetection will not work in a prefix environment or in a
# linux container.
#
# This should be set to the value representing the environment this file is
# PRESENTLY in, not the virtualization the environment is capable of.
#rc_sys=""

# This is the number of tty's used in most of the rc-scripts (like
# consolefont, numlock, etc ...)
rc_tty_number=12


----------------------------------------------------------------------------------------------------------------------------------------------------------------------

I'm asking if it is a myth or no reducing tty's,not asking how?!
pepebotella
Simple Hen
 
Posts: 71
Joined: Mon Nov 02, 2009 21:26

Re: How to optimize and accelerate your system

Postby pepebotella » Fri Mar 02, 2012 14:58

pepebotella wrote:I'm asking bout why I do not have Change rc_parallel=
Code: Select all
# Global OpenRC configuration settings

# Set rc_interactive to "YES" and you'll be able to press the I key during
# boot so you can choose to start specific services. Set to "NO" to disable
# this feature.
rc_interactive="YES"

# If we need to drop to a shell, you can specify it here.
# If not specified we use $SHELL, otherwise the one specified in /etc/passwd,
# otherwise /bin/sh
# Linux users could specify /sbin/sulogin
rc_shell=/sbin/sulogin

# Do we allow any started service in the runlevel to satisfy the dependency
# or do we want all of them regardless of state? For example, if net.eth0
# and net.eth1 are in the default runlevel then with rc_depend_strict="NO"
# both will be started, but services that depend on 'net' will work if either
# one comes up. With rc_depend_strict="YES" we would require them both to
# come up.
#rc_depend_strict="YES"

# rc_hotplug is a list of services that we allow to be hotplugged.
# By default we do not allow hotplugging.
# A hotplugged service is one started by a dynamic dev manager when a matching
# hardware device is found.
# This service is intrinsically included in the boot runlevel.
# To disable services, prefix with a !
# Example - rc_hotplug="net.wlan !net.*"
# This allows net.wlan and any service not matching net.* to be plugged.
# Example - rc_hotplug="*"
# This allows all services to be hotplugged
rc_hotplug="!net.*"

# rc_logger launches a logging daemon to log the entire rc process to
# /var/log/rc.log
# NOTE: Linux systems require the devfs service to be started before
# logging can take place and as such cannot log the sysinit runlevel.
rc_logger="YES"

# Through rc_log_path you can specify a custom log file.
# The default value is: /var/log/rc.log
#rc_log_path="/var/log/rc.log"

# By default we filter the environment for our running scripts. To allow other
# variables through, add them here. Use a * to allow all variables through.
#rc_env_allow="VAR1 VAR2"

# By default we assume that all daemons will start correctly.
# However, some do not - a classic example is that they fork and return 0 AND
# then child barfs on a configuration error. Or the daemon has a bug and the
# child crashes. You can set the number of milliseconds start-stop-daemon
# waits to check that the daemon is still running after starting here.
# The default is 0 - no checking.
#rc_start_wait=100

# rc_nostop is a list of services which will not stop when changing runlevels.
# This still allows the service itself to be stopped when called directly.
#rc_nostop=""

# rc will attempt to start crashed services by default.
# However, it will not stop them by default as that could bring down other
# critical services.
#rc_crashed_stop=NO
#rc_crashed_start=YES

##############################################################################
# MISC CONFIGURATION VARIABLES
# There variables are shared between many init scripts

# Set unicode to YES to turn on unicode support for keyboards and screens.
unicode="YES"

# Below is the default list of network fstypes.
#
# afs cifs coda davfs fuse fuse.sshfs gfs glusterfs lustre ncpfs
# nfs nfs4 ocfs2 shfs smbfs
#
# If you would like to add to this list, you can do so by adding your
# own fstypes to the following variable.
#extra_net_fs_list=""

##############################################################################
# SERVICE CONFIGURATION VARIABLES
# These variables are documented here, but should be configured in
# /etc/conf.d/foo for service foo and NOT enabled here unless you
# really want them to work on a global basis.

# Some daemons are started and stopped via start-stop-daemon.
# We can set some things on a per service basis, like the nicelevel.
#export SSD_NICELEVEL="-19"

# Pass ulimit parameters
#rc_ulimit="-u 30"

# It's possible to define extra dependencies for services like so
#rc_config="/etc/foo"
#rc_need="openvpn"
#rc_use="net.eth0"
#rc_after="clock"
#rc_before="local"
#rc_provide="!net"

# You can also enable the above commands here for each service. Below is an
# example for service foo.
#rc_foo_config="/etc/foo"
#rc_foo_need="openvpn"
#rc_foo_after="clock"

# You can also remove dependencies.
# This is mainly used for saying which servies do NOT provide net.
#rc_net_tap0_provide="!net"

##############################################################################
# LINUX SPECIFIC OPTIONS

# This is the subsystem type. Valid options on Linux:
# ""        - nothing special
# "lxc"     - Linux Containers
# "openvz"  - Linux OpenVZ
# "prefix"  - Prefix
# "uml"     - Usermode Linux
# "vserver" - Linux vserver
# "xen0"    - Xen0 Domain
# "xenU"    - XenU Domain
# If this is commented out, automatic detection will be attempted.
# Note that autodetection will not work in a prefix environment or in a
# linux container.
#
# This should be set to the value representing the environment this file is
# PRESENTLY in, not the virtualization the environment is capable of.
#rc_sys=""

# This is the number of tty's used in most of the rc-scripts (like
# consolefont, numlock, etc ...)
rc_tty_number=12


----------------------------------------------------------------------------------------------------------------------------------------------------------------------

I'm asking if it is a myth or no reducing tty's,not asking how?!


thx a/w
pepebotella
Simple Hen
 
Posts: 71
Joined: Mon Nov 02, 2009 21:26

Re: How to optimize and accelerate your system

Postby pepebotella » Sat Mar 03, 2012 17:06

Nice,nicest,whatever,blablabla distro! but the support... :roll:

sorry being sincere!
pepebotella
Simple Hen
 
Posts: 71
Joined: Mon Nov 02, 2009 21:26

Re: How to optimize and accelerate your system

Postby Fitzcarraldo » Sat Mar 03, 2012 18:09

pepebotella wrote:Nice,nicest,whatever,blablabla distro! but the support... :roll:

sorry being sincere!

Your attitude is unacceptable. You have to realise that this distribution is produced by unpaid volunteers who have day jobs. There are no staff sitting around waiting to answer questions. The forums are frequented by users such as yourself and myself. They are also unpaid and they don't monitor these forums waiting to answer questions the moment they are posted. If your are lucky, someone will read your post, know the answer and reply. Many times people don't know the answer. And if your post is unintelligable, it makes it even less likely that someone will respond.

You would be better posting your questions in your native language in the SL Spanish-language Forum. You do not communicate clearly in English, and some of your posts are not understandable. The following question of yours is gibberish:

pepebotella wrote:*It is possible to know why aint have Change rc_parallel=

If you wanted to know why you do not have "Change rc_parallel=" (sic) in the file /etc/rc.conf, then you should have asked the question in a clearer fashion. For example: "I do not have 'rc_parallel=' in my file /etc/rc.conf. Why is that?"

My answer to your question is "I don't know". Presumably any readers of your original post who did understand what you meant also don't know, otherwise they would have told you the answer.

However, my file /etc/rc.conf has the following lines at the beginning:

Code: Select all
# Global OpenRC configuration settings

# Set to "YES" if you want the rc system to try and start services
# in parallel for a slight speed improvement. When running in parallel we
# prefix the service output with its name as the output will get
# jumbled up.
# WARNING: whilst we have improved parallel, it can still potentially lock
# the boot process. Don't file bugs about this unless you can supply
# patches that fix it without breaking other things!
#rc_parallel="NO"

Notice that the parameter rc_parallel is commented out. Also notice that there is a big warning message about using it. My guess is that the SL developers removed it to stop people messing around with it, causing their PCs to lock up at boot, and then screaming in the forums.

pepebotella wrote:I'm asking if it is a myth or no reducing tty's,not asking how?!

And I was telling you. If you use Google, you would find the answer. Try it: Let me google that for you too

I didn't know the answer to your question. I used Google and very quickly found the answer. You could have done the same.
User avatar
Fitzcarraldo
Sagely Hen
 
Posts: 7335
Joined: Sat Mar 10, 2007 5:40
Location: United Kingdom

Re: How to optimize and accelerate your system

Postby micia » Sat Mar 03, 2012 20:23

pepebotella wrote:I'm asking bout why I do not have Change rc_parallel=


As Fitzcarraldo correctly deduced that option has been hidden, by the OpenRC developers themselves, since it is a dangerous feature that is known to not work under some circumstances, thus it is not listed rc.conf anymore.
You can still manually add and enable it getting the same result.

pepebotella, be aware that your kind of attitude, including double posting, needless quotes, dubious tone, topic bumping and lack of patience won't help you getting a prompt answer.
User avatar
micia
Sagely Hen
 
Posts: 2710
Joined: Wed Nov 26, 2008 16:41

Re: How to optimize and accelerate your system

Postby sdi » Thu Oct 04, 2012 17:26

Fitzcarraldo wrote:...SL Spanish-language Forum.

where would that be found?

yes, I googled it and found nothing
sdi
Baby Hen
 
Posts: 4
Joined: Tue Sep 18, 2012 8:30

Re: How to optimize and accelerate your system

Postby Stupot » Thu Oct 04, 2012 17:55

Stupot
Sagely Hen
 
Posts: 1012
Joined: Wed Feb 14, 2007 3:44
Location: St. Louis, MO, USA

PreviousNext

Return to Sabayon Linux General Discussion

Who is online

Users browsing this forum: No registered users and 1 guest