Harald Hoyer wrote:
> Trying a yum everything install, I found out, that booting now takes
> endlessly.
>
> # ls /etc/rc.d/rc5.d/S*|wc -l
> 95
>
> Please review, if the packages really need to be "on" after an install.
>
<snip>
I would argue that since this was an "everything" install, most of these
services are not enabled by default, but by installing the (non default)
package.
And that if I install a specific package, I would want the service to
start as default (or else I would not have installed the package in the
first place).
Rgds.
Ola (T)
--
_,--', _._.--._____
.--.--';_'-.', ";_ _.,-' Ola Thoresen
.'--'. _.' {`'-;_ .-.>.'
'-:_ ) / `' '=. It is easier to fix Unix
) > {_/, /~) than to live with Windows
|/ `^ .'
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
03-31-2008, 08:37 AM
Harald Hoyer
Too many default services on
Trying a yum everything install, I found out, that booting now takes endlessly.
# ls /etc/rc.d/rc5.d/S*|wc -l
95
Please review, if the packages really need to be "on" after an install.
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
03-31-2008, 09:24 AM
Rahul Sundaram
Too many default services on
Ola Thoresen wrote:
And that if I install a specific package, I would want the service to
start as default (or else I would not have installed the package in the
first place).
That isn't necessarily true. It depends on where and how the software is
being deployed.
Rahul
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
03-31-2008, 09:25 AM
"Izhar Firdaus"
Too many default services on
On Mon, Mar 31, 2008 at 4:16 PM, Ola Thoresen <redhat@olen.net> wrote:
> Harald Hoyer wrote:
> > Trying a yum everything install, I found out, that booting now takes
> > endlessly.
> >
> > # ls /etc/rc.d/rc5.d/S*|wc -l
> > 95
> >
> > Please review, if the packages really need to be "on" after an install.
> >
> <snip>
>
> I would argue that since this was an "everything" install, most of these
> services are not enabled by default, but by installing the (non default)
> package.
> And that if I install a specific package, I would want the service to
> start as default (or else I would not have installed the package in the
> first place).
>
I would expect a service to not start until I configure it, and enable
it explicitly. Installing packages doesnt mean I want to use it ..
(eg: httpd's libs is a dependency for some app in fedora livecd .. but
that doesnt mean I want httpd to start on boot )
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
03-31-2008, 09:43 AM
Nicu Buculei
Too many default services on
Ola Thoresen wrote:
I would argue that since this was an "everything" install, most of these
services are not enabled by default, but by installing the (non default)
package.
And that if I install a specific package, I would want the service to
start as default (or else I would not have installed the package in the
first place).
And I argue that is *not* the case at least for *some* of the packages.
Example: Fyre is a graphic application, "a tool for producing
computational artwork based on histograms of iterated chaotic functions".
It also install a service, fyre-cluster, which is on by default.
However, this service is not needed by the average Fyre user (or even
for the large majority of users).
--
nicu :: http://nicubunu.ro :: http://nicubunu.blogspot.com
Cool Fedora wallpapers: http://fedora.nicubunu.ro/wallpapers/
Open Clip Art Library: http://www.openclipart.org
my Fedora stuff: http://fedora.nicubunu.ro
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
03-31-2008, 11:35 AM
Dennis Jacobfeuerborn
Too many default services on
Rahul Sundaram wrote:
Ola Thoresen wrote:
And that if I install a specific package, I would want the service to
start as default (or else I would not have installed the package in the
first place).
That isn't necessarily true. It depends on where and how the software is
being deployed.
Quite frankly I'd say even in the case of services that usually are
expected to be started as default (e.g. httpd) I think I could live with
having to manually activate it.
I see two exceptions: sshd and "local" services like e.g. dbus, beagle,
etc. that don't listen on external IPs and that you cannot really expect
the user to activate manually.
Regards,
Dennis
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
03-31-2008, 01:00 PM
Patrice Dumas
Too many default services on
On Mon, Mar 31, 2008 at 01:35:46PM +0200, Dennis Jacobfeuerborn wrote:
>
> Quite frankly I'd say even in the case of services that usually are
> expected to be started as default (e.g. httpd) I think I could live with
> having to manually activate it.
httpd requires to be setup before started. But even in the case of more
straigthforward network services, they should never be started, since
one may only want to install them and start them only after some actions
(start a specific interface, start vpns, modify routing and firewalling
or whatever).
> I see two exceptions: sshd and "local" services like e.g. dbus, beagle,
> etc. that don't listen on external IPs and that you cannot really expect
> the user to activate manually.
Indeed. There are a lot of such services in the list, so it is not easy
to know which ones are right and which ones are wrong.
For sshd, it is debatable to have it started automatically, since it is
a network facing service, but I think that it is a reasonable exception
given that in many case it can be the only way to login to the
computer after installation.
--
Pat
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
03-31-2008, 01:29 PM
"Jhann B. Gumundsson"
Too many default services on
There does not seemed to be any rule to whats enabled and what's not.
Package maintainer's and or developers seem to decide for them self
whether service
is enabled/disabled by default.
The proper way to do this is to only enabled system and network needed
services
for a functional and network connected system by default.
The rest of the services being enabled/disabled in firstboot either
individually ( advanced control )
or group together in a big buttons for more noob user friendly solution
For example Enable Blutetooh ( user clicks on that and all bluetooth
related services are enabled )
Enabled printing ( Cups and printing related service enabled )
etc..
Already filled an RFE for this and hopefully it will make F-X
Best regards
Johann B.
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
03-31-2008, 01:50 PM
Rahul Sundaram
Too many default services on
Jhann B. Gumundsson wrote:
There does not seemed to be any rule to whats enabled and what's not.
Package maintainer's and or developers seem to decide for them self
whether service
is enabled/disabled by default.
The proper way to do this is to only enabled system and network needed
services
for a functional and network connected system by default.
The rest of the services being enabled/disabled in firstboot either
individually ( advanced control )
or group together in a big buttons for more noob user friendly solution
For example Enable Blutetooh ( user clicks on that and all bluetooth
related services are enabled )
Enabled printing ( Cups and printing related service enabled )
etc..
Already filled an RFE for this and hopefully it will make F-X
If you are talking about RFE's or bug reports, please provide the bz
number.
Rahul
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
03-31-2008, 02:11 PM
John Dennis
Too many default services on
Jhann B. Gumundsson wrote:
There does not seemed to be any rule to whats enabled and what's not.
Package maintainer's and or developers seem to decide for them self
whether service
is enabled/disabled by default.
My understanding is rpm's which install a service do *not* start the
service in %post via chkconfig for all the reasons cited in the thread
(i.e. the sys admin or owner decides what should be running, how it's
configured,e etc. merely installing an rpm should not start a hidden
service). There are a minority of exceptions, services which must run to
make the system usable, these are well known. It is permissible to
perform a condrestart in %post, but this is just respecting the existing
configuration on the box.
These are the guidelines as I've always understood them. I wonder if
part of the problem lies in the new LSB blocks which have been added to
many initscripts without a complete understanding of what some of the
boilerplate actually does, e.g. Default-Start.
--
John Dennis <jdennis@redhat.com>
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
Too many default services on
