Sponsored Content
Operating Systems Solaris Remote services during Solaris installation Post 302253371 by soliberus on Friday 31st of October 2008 12:00:31 PM
Old 10-31-2008
Remote services during Solaris installation

I've installed Solaris 10 (05-08) on a SPARC platform

During the installation I was prompted with the question below. I selected yes to enable remote services.

Does anyone know what services this option enables?

- Enabling remote services ----------------------------------------
Would you like to enable network services for use by remote clients?
Selecting "No" provides a more secure configuration in
which Secure Shell is the only network service provided to
remote clients. Selecting "Yes" enables a larger set of
services as in previous Solaris releases. If in doubt, it is
safe to select "No" as any services can be individually enabled
after installation.
Note: This choice only affects initial installs. It doesn't affect upgrades.
Remote services enabled
-----------------------
[X] Yes
[ ] No
-------------------------------------------------------------------
F2_Continue F6_Help
 

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

shange user's pass for all services on a remote host

here is the picture: a website on server1 & a "username" logged in that site. The same username has a shell(nologin)/ftp/samba/mail(qmail) acount on server2. i have s form on server1 that can pass the username & its NEW password to a sript that should change all passwords on server2. the... (5 Replies)
Discussion started by: veskonedev
5 Replies

2. Solaris

installation of Solaris: installation bypasses network config.

hello solaris friends, I've tried installing Sun Solaris 10.0, but everytime it seems to bypass the network config. screen that looks similar to this...here's the url: http://www.hup.hu/old/images/hup/Solaris/Sol10beta7/9.png I'm able to install it all the way through but I get no... (2 Replies)
Discussion started by: cadmiumgreen
2 Replies

3. UNIX for Advanced & Expert Users

installation entirely remote - Solaris

moved to Solaris... https://www.unix.com/sun-solaris/84558-installation-entirely-remote-solaris.html (0 Replies)
Discussion started by: vbe
0 Replies

4. Solaris

installation entirely remote - Solaris

Friends, Is there any way to do a installation of Solaris entirely remote? Jumpstart is almost what I want but is not entirely remote because it requires to access the openboot to execute command "boot net - install. Can i to do a upgrade entirely remote too? Thanks, Marcelo... (2 Replies)
Discussion started by: marcmc
2 Replies

5. Red Hat

remote redhat installation

Hi guys! I have fedora6 on server and i want redhell5 to be on it. The problem is that the server is located from me several hundred kilometers away. So the only access i have is ssh. On my notebook i have iso-image with redhell5. How can install redhell5 on it and deinstall fedora6? Thanks in... (8 Replies)
Discussion started by: smallman
8 Replies

6. Solaris

Remote installation of solaris 9

Hi All, We have an ungent requirement of remote installation of a Sun server as we can't attach cd/dvd rom with the server. Is there any way like NFS installation in linux to complete it? We need any possible way except Jumpstart as it has a long procedure to set. Thanks, Deepak (5 Replies)
Discussion started by: naw_deepak
5 Replies

7. UNIX for Advanced & Expert Users

Autosys remote agent installation issue

We require Autosys remote agent to be installed in Unix (AIX) server to invoke a Unix script from Autosys. But the issue is there is already a Jobtrac scheduler present in this server, and the support team who do Autosys installation say that these 2 schedulers cannot exist in the same server.... (0 Replies)
Discussion started by: hidnana
0 Replies

8. Solaris

Solaris 10 flash installation - fatal error. Solaris installation program exited.

Not very helpful to say the least. Seems to read the flar file and go through the upgrade and then come up with this error. Any ideas? (1 Reply)
Discussion started by: psychocandy
1 Replies
DH_INSTALLSYSTEMD(1)                                                 Debhelper                                                DH_INSTALLSYSTEMD(1)

NAME
dh_installsystemd - install systemd unit files SYNOPSIS
dh_installsystemd [debhelperoptions] [--restart-after-upgrade] [--no-stop-on-upgrade] [--no-enable] [--name=name] [unitfile...] DESCRIPTION
dh_installsystemd is a debhelper program that is responsible for enabling, disabling, starting, stopping and restarting systemd unit files. In the simple case, it finds all unit files installed by a package (e.g. bacula-fd.service) and enables them. It is not necessary that the machine actually runs systemd during package installation time, enabling happens on all machines in order to be able to switch from sysvinit to systemd and back. For only generating blocks for specific service files, you need to pass them as arguments, e.g. dh_installsystemd quota.service and dh_installsystemd --name=quotarpc quotarpc.service. FILES
debian/package.service, debian/package@.service If this exists, it is installed into lib/systemd/system/package.service (or lib/systemd/system/package@.service) in the package build directory. debian/package.tmpfile If this exists, it is installed into usr/lib/tmpfiles.d/package.conf in the package build directory. (The tmpfiles.d mechanism is currently only used by systemd.) debian/package.target, debian/package@.target If this exists, it is installed into lib/systemd/system/package.target (or lib/systemd/system/package@.target) in the package build directory. debian/package.socket, debian/package@.socket If this exists, it is installed into lib/systemd/system/package.socket (or lib/systemd/system/package@.socket) in the package build directory. debian/package.mount If this exists, it is installed into lib/systemd/system/package.mount in the package build directory. debian/package.path, debian/package@.path If this exists, it is installed into lib/systemd/system/package.path (or lib/systemd/system/package@.path) in the package build directory. debian/package.timer, debian/package@.timer If this exists, it is installed into lib/systemd/system/package.timer (or lib/systemd/system/package@.timer) in the package build directory. OPTIONS
--no-enable Disable the service(s) on purge, but do not enable them on install. Note that this option does not affect whether the services are started. Please remember to also use --no-start if the service should not be started. --name=name Install the service file as name.service instead of the default filename, which is the package.service. When this parameter is used, dh_installsystemd looks for and installs files named debian/package.name.service instead of the usual debian/package.service. Moreover, maintainer scripts are only generated for units that match the given name. --restart-after-upgrade Do not stop the unit file until after the package upgrade has been completed. This is the default behaviour in compat 10. In earlier compat levels the default was to stop the unit file in the prerm, and start it again in the postinst. This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon will not get confused by the package being upgraded while it's running before using this option. --no-restart-after-upgrade Undo a previous --restart-after-upgrade (or the default of compat 10). If no other options are given, this will cause the service to be stopped in the prerm script and started again in the postinst script. -r, --no-stop-on-upgrade, --no-restart-on-upgrade Do not stop service on upgrade. --no-start Do not start the unit file after upgrades and after initial installation (the latter is only relevant for services without a corresponding init script). Note that this option does not affect whether the services are enabled. Please remember to also use --no-enable if the services should not be enabled. NOTES
Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command (with the same arguments). Otherwise, it may cause multiple instances of the same text to be added to maintainer scripts. SEE ALSO
debhelper(7) AUTHORS
pkg-systemd-maintainers@lists.alioth.debian.org 11.1.6ubuntu2 2018-05-10 DH_INSTALLSYSTEMD(1)
All times are GMT -4. The time now is 11:09 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy