Solaris uses a few different mechanisms to start up services and processes at boot time. Where do all the running processes come from? Can you find from where they were started? (8 Replies)
I'm trying to add services to start services automatically during the system start up in suse linux.
I followed these steps..
chkconfig servicename on
and created symbolic link at /etc/rc.d/rc3.d/ folder with name S80servicename. here is the command I used
ln -s /etc/init.d/servicename... (8 Replies)
Hi all,
can any one guide me to configure samba services on solaries8 machine and how to use at the client side (i,e) how the client can retrive the data using samba services.
Thanks
venky (2 Replies)
Hello All
i have a question related to some services,i want to start some services with server linux centos.
i make "chkconfig httpd on" and "chkconfig asterisk on",but when i verify with chkconfig --list i found
httpd 0: off 1: off 2: on 3: on 4: on 5: on 6:... (6 Replies)
I had a doubt if any services need to be restarted if port no in /etc/services in an RHEL setup is changed. For eg, the port no of 443 for SSL may need to be changed.
I hope my query is clear whether any services need to be restarted if port no in /etc/services is changed.
Please revert with... (10 Replies)
I normally use "chkconfig" to configure start up services in a particular run level.....
But i don't know how to do it in solaris 10.... please help me !!! (2 Replies)
Hi all,
I remember way back in some old environment, having the HA cluster services not being started automatically at startup, ie. no entry in /etc/inittab.
I remember reason was (taken a 2 node active/passive cluster), to avoid having a backup node being booted, so that it will not... (4 Replies)
Hello Experts,
I have a requirement to start and stop weblogic services in a clustered environment.
First i need to start weblogic server and once the server is in Running mode i need to do SSH to other server and there i need to start Node Manager and Managed server, After these two are in... (1 Reply)
Discussion started by: beginner786
1 Replies
LEARN ABOUT LINUX
inets
inets(3erl) Erlang Module Definition inets(3erl)NAME
inets - The inets services API
DESCRIPTION
This module provides the most basic API to the clients and servers, that are part of the Inets application, such as start and stop.
COMMON DATA TYPES
Type definitions that are used more than once in this module:
service() = ftpc | tftp | httpc | httpd
property() = atom()
EXPORTS
services() -> [{Service, Pid}]
Types Service = service()
Pid = pid()
Returns a list of currently running services.
Note:
Services started as stand_alone will not be listed.
services_info() -> [{Service, Pid, Info}]
Types Service = service()
Pid = pid()
Info = [{Option, Value}]
Option = property()
Value = term()
Returns a list of currently running services where each service is described by a [{Option, Value}] list. The information given in
the list is specific for each service and it is probable that each service will have its own info function that gives you even more
details about the service.
service_names() -> [Service]
Types Service = service()
Returns a list of available service names.
start() ->
start(Type) -> ok | {error, Reason}
Types Type = permanent | transient | temporary
Starts the Inets application. Default type is temporary. See also application(3erl)
stop() -> ok
Stops the inets application. See also application(3erl)
start(Service, ServiceConfig) -> {ok, Pid} | {error, Reason}
start(Service, ServiceConfig, How) -> {ok, Pid} | {error, Reason}
Types Service = service()
ServiceConfig = [{Option, Value}]
Option = property()
Value = term()
How = inets | stand_alone - default is inets
Dynamically starts an inets service after the inets application has been started.
Note:
Dynamically started services will not be handled by application takeover and failover behavior when inets is run as a distributed applica-
tion. Nor will they be automatically restarted when the inets application is restarted, but as long as the inets application is up and run-
ning they will be supervised and may be soft code upgraded. Services started as stand_alone , e.i. the service is not started as part of
the inets application, will lose all OTP application benefits such as soft upgrade. The "stand_alone-service" will be linked to the process
that started it. In most cases some of the supervision functionality will still be in place and in some sense the calling process has now
become the top supervisor.
stop(Service, Reference) -> ok | {error, Reason}
Types Service = service() | stand_alone
Reference = pid() | term() - service specified reference
Reason = term()
Stops a started service of the inets application or takes down a "stand_alone-service" gracefully. When the stand_alone option is
used in start, only the pid is a valid argument to stop.
SEE ALSO ftp(3erl) , httpc(3erl) , httpd(3erl) , tftp(3erl)Ericsson AB inets 5.5.2 inets(3erl)