similar to: Starting Samba on the Start-UP??

In the docs for chkconfig it says: <startlevellist> is a list of the runlevels for which the service should be started by default. Only services which are really required for a vital system should define runlevels here. If no runlevels are defined, a - should be used in place of the runlevels list. and then: More commonly, the service is off by default on all runlevels, which looks like

My other source of info is the O'Reilly book _Using Samba_ by Ts, Eckstein, and Collier-Brown. In Chapter 2, they say that the kills--the Kxxservices-- are always run first, then the Startups--the Sxxservice--are run. They're not explicit on the numbering, but they imply that lower numbers are always run before higher numbers. Finally, their example explicitly has the reader

share in the samba box, from the PDC server itself. The log.winbindd and log.nmbd are empty. [2001/08/08 13:11:28, 3] smbd/reply.c:reply_sesssetup_and_X(865) Domain=[EERDBR001] NativeOS=[Windows NT 1381] NativeLanMan=[] [2001/08/08 13:11:28, 3] smbd/reply.c:reply_sesssetup_and_X(876) sesssetupX:name=[administrator] [2001/08/08 13:11:28, 3] libsmb/namequery.c:resolve_lmhosts(733)

Just something I patch in my rpm set to make shorewall configurable. -- Tuomo Soini <tis@foobar.fi> Linux and network services +358 40 5240030 Foobar Oy <http://foobar.fi/> -------------- next part -------------- --- shorewall-2.0.2d/install.sh.orig 2004-05-28 03:17:01.000000000 +0300 +++ shorewall-2.0.2d/install.sh 2004-05-30 01:08:00.000000000 +0300 @@ -87,11 +87,20 @@ # RUNLEVELS

Hi, I cannot 'halt' my CentOS 6 servers while running corosync+pacemaker. I believe the runlevels used to stop corosync and pacemaker are not in the correct order and create the infinite "Waiting for corosync services to unload..." loop thing. This is my first time with this cluster technology but apparently pacemaker has to be stopped /before/ corosync. Applying the following

> > >On Thursday 15 November 2012 18:36:16 david wrote: > > Folks > > > > Just for laughs, I tried installing Centos 6.3 on the laptop HP > > 8540w. Windows 7 installed earlier, but I had to import a driver for > > the Ethernet controller since it was not supported on the > > distribution DVD of Windows7. > > > > The Centos installation I

I just installed Tomcat and when I run the chkconfig -add tomcat, it tells me that tomcat does not support chkconfig. Suggestions? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20060502/a84cc5cb/attachment-0003.html> -------------- next part -------------- A non-text attachment was scrubbed...

I've create a script and associated links(via chkconfig). The script runs in the expected runlevels at boot time, but does not run at all during shutdown(halt, reboot, etc). I swear I've done this a million times. What am I overlooking? # cat /etc/issue CentOS release 3.5 (Final) Kernel \r on an \m # chkconfig --list chnghst chnghst 0:off 1:on 2:off 3:off 4:off

chkconfig is not installed, but systemctl seems to work together with update-rc.d. 21:02:19 # systemctl disable samba Synchronizing state for samba.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d samba defaults Executing /usr/sbin/update-rc.d samba disable update-rc.d: error: samba Default-Start contains no runlevels, aborting. 21:02:58 # systemctl disable nmbd

I have just deployed a new CentOS 6.4 image on AWS, and I'm having issues with init.d scripts not starting up. I've verified the following; 1) They work on their own after boot 2) They're set to run at runlevel 3,4, and 5 via chkconfig 3) The system boots up in runlevel 3 (no GUI) 4) There are no lingering PID files around after boot 5) Permissions

Hi, since the last few days my system crashs at startup of gdm (on system boot). If I choose runlevel 2, the system doesn't crash. I found out, that HAL is the problem. After disabling hal (chkconfig haldaemon --off) no crashes appear. The system freezes completly so I can't look into the logfiles. I removed an reinstalled hal already, but nothing changed. I tried older kernels

After a fresh install, I noticed that shorewall 2.4.0 wasn''t starting automatically under FC4. The startup script installs properly from the rpm: /etc/rc.d/init.d/shorewall ... but the post install "/sbin/chkconfig --add shorewall" produces this in the runlevel symlink directories: /etc/rc.d/rc5.d/S-1shorewall /etc/rc.d/rc0.d/K-1shorewall /etc/rc.d/rc6.d/K-1shorewall

On Mon, 5 Oct 2015, Rowland Penny wrote: > On 05/10/15 18:56, Birgit Berger (UV Wien) wrote: >> How do I stop scripts samba, smbd and nmbd being run at startup? > > I do not know because you are using Debian Jessie, this uses systemd which I > absolutely refuse to use! > > Perhaps somebody else can tell you how to do this and explain just how they > are all got

I'm trying to create an initialization scrip in the /etc/init.d/. Of course, the one I have is failing! At the top of the other initialization scripts in the same directory, there is are two lines, the chkconfig and description # chkconfig: 2345 55 25 # description: OpenSSH server daemon On the check config line, what are the numbers/attributes that follow? If I'm creating an

Here is my output: Console: colour dummy device 80x25 console [tty0] console [hvc0] installing Xen timer for CPU 0 Detected 1806.840 MHz processor Calibrating delay loop (skipped), value calculated using timer frequency.. 3613.68 BogoMIPS (lpj=7227360) Mount-cache hash table entries: 256 CPU: L1 I Cache: 64K (64 bytes/line) Apic siabled by BIOS Grant table initialized NET: Registering protocol

Hi all, I think I've spotted a few stupidities (bugs) in the current version of kernel-utils (kernel-utils-2.4-13.1.80). I'm sure these are all propagated from upstream, but I hope someone could have a quick look to verify this and see if we either can push complaints upwards, or provide local fixes. The kernel-utils package provides several 'kernel-type' functions -

On Sun, 23 Nov 2014 13:07:47 -0600 Gregory P. Ennis wrote: > I also changed the boot level to 5. Do you mean the runlevel? If so, are you sure that you changed it correctly? Centos 7 doesn't use runlevels set in inittab like previous versions did. I see that fact is actually noted in /etc/inittab, along with the expected way to do it. -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~

Hi, after you have done "make", "make install" and maybe "make samples" in asterisk source-dir just do a "make config" and all will be done for you. to check if it worked, simply issue "chkconfig --list asterisk" to see the runlevels asterisk is started or not. to start zaptel drivers do the same after "make install" ("make

Hi all, I need to launch X-Windows at runlevel 4 and 5. CentOS only start up x-windows at runlevel by default. I have modified /etc/inittab to accomplish this: x:4:respawn:/etc/X11/prefdm -nodaemon x:5:respawn:/etc/X11/prefdm -nodaemon But this returns errors every time that start and stop system ... Which is the correct form to launch x-windows under centos at different runlevels?? Many

Date: Sun, 23 Nov 2014 13:50:17 -0600 On Sun, 23 Nov 2014 13:07:47 -0600 Gregory P. Ennis wrote: > I also changed the boot level to 5. Do you mean the runlevel? If so, are you sure that you changed it correctly? Centos 7 doesn't use runlevels set in inittab like previous versions did. I see that fact is actually noted in /etc/inittab, along with the expected way to do it.