Sponsored Content
Top Forums UNIX for Advanced & Expert Users Smb & nmb not starting at boot - CentOS7 Post 302992196 by Scrutinizer on Wednesday 22nd of February 2017 02:23:58 PM
Old 02-22-2017
Centos7 uses systemd . Have a look at man systemctl, specifically systemctl enable ...
chkconfig is stiil used, but just for a few remaining applications that still use init scripts...
 

9 More Discussions You Might Find Interesting

1. Slackware

starting up something on boot

I'm trying to bring up a database server when the linux 6.2 machine is restarted, in unix i can set up a Sxxdbstart script under rc3.d and run su user -c /path/to/my/script How can I do this in linux? I thought I could just run it under the rc.d/rc.local script and add it at the end of the... (2 Replies)
Discussion started by: kymberm
2 Replies

2. SCO

Scologin not starting on boot up

Hi, I just finished swapping my computer to a new case. However, now when I try booting up the machine, I cannot get the Scologin to start. It just stays at the screen which says "Scologin is starting (/dev/tty02). Please wait.....". Does anyone have any idea how to fix this? Thanks (1 Reply)
Discussion started by: AtALoss
1 Replies

3. UNIX for Dummies Questions & Answers

Slow FTP & SMB

SCO Unix 5.0.5 moving to Red Hat Intel EtherExpress Pro/100+ Newbie that just started working for a company and having an issue with transfer speeds over the network. Need to move 1.5GB of data from an old server with a single SCSI HDD to a new server with RAID 5 SATA HDD's. Goal was to FTP... (4 Replies)
Discussion started by: rockboles
4 Replies

4. SCO

Stoping & starting the cron daemon

Hi We are running SCO ver 5. Recently the cron daemon stopped running on its own. How do I find out why? How do I restart/stop it? I typed cron but it didn't work. Will rebooting it do the trick or can I manually start and stop the cron daemon? Please help. Thanks & Regards. (0 Replies)
Discussion started by: othman
0 Replies

5. SCO

Stoping & starting the cron

Hi We are running SCO ver 5. Recently the cron daemon stopped running on its own. How do I find out why? How do I restart/stop it? I typed cron but it didn't work. Will rebooting it do the trick or can I manually start and stop the cron daemon? Please help. Thanks & Regards. (9 Replies)
Discussion started by: othman
9 Replies

6. UNIX for Dummies Questions & Answers

Starting & Stop print services in Unix

Hi There Kindly inform me on how to start and stop the print services in Unix from the command line. (2 Replies)
Discussion started by: esh
2 Replies

7. HP-UX

help auto starting app on boot

Hi I need a bit of help figuring out how to auto start an application on boot on an HPUX. I am a fairly exp AIX guy now working an HP shop. I use to change a /etc/rc... file. Any advise would be a great help TIA. –K If it is a help the program is a DB and runs as root /usr/ud{##}/startud... (3 Replies)
Discussion started by: KmJohnson
3 Replies

8. Infrastructure Monitoring

Solaris 10 - starting snmpdx at boot time on a port other than 161

Hi All, Can we start the snmpdx on another port at boot time on solaris 10 instead of the default 161 port? What is the configuration file to set this? We can make it run in a different port after the system boots up by using snmpdx -p port_number This requirement is because i have an... (1 Reply)
Discussion started by: Mr. Zer0
1 Replies

9. Linux

CentOS7 systemd-timer

hi moring everyone, i has used systemd-timer running the task, i set every 5 second execute 1 times,but the systemd-timer don't by that also random times execute. what's reason. testest.timer configure ------------------------------------------------------------------------ ... (2 Replies)
Discussion started by: shean
2 Replies
TELINIT(8)							      telinit								TELINIT(8)

NAME
telinit - Change SysV runlevel SYNOPSIS
telinit [OPTIONS...] {COMMAND} DESCRIPTION
telinit may be used to change the SysV system runlevel. Since the concept of SysV runlevels is obsolete the runlevel requests will be transparently translated into systemd unit activation requests. OPTIONS
The following options are understood: --help Prints a short help text and exits. --no-wall Do not send wall message before reboot/halt/power-off. The following commands are understood: 0 Power-off the machine. This is translated into an activation request for poweroff.target and is equivalent to systemctl poweroff. 6 Reboot the machine. This is translated into an activation request for reboot.target and is equivalent to systemctl reboot. 2, 3, 4, 5 Change the SysV runlevel. This is translated into an activation request for runlevel2.target, runlevel3.target, ... and is equivalent to systemctl isolate runlevel2.target, systemctl isolate runlevel3.target, ... 1, s, S Change into system rescue mode. This is translated into an activation request for rescue.target and is equivalent to systemctl rescue. q, Q Reload daemon configuration. This is equivalent to systemctl daemon-reload. u, U Serialize state, reexecute daemon and deserialize state again. This is equivalent to systemctl daemon-reexec. EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise. NOTES
This is a legacy command available for compatibility only. It should not be used anymore, as the concept of runlevels is obsolete. SEE ALSO
systemd(1), systemctl(1), wall(1) systemd 208 TELINIT(8)
All times are GMT -4. The time now is 12:00 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy