search for: killprocs

Hi, I noticed one small possible error in the openssh-2.3.0p1/contrib/redhat/sshd.init script. In the stop option: stop) echo -n "Shutting down sshd: " if [ -f $PID_FILE ] ; then killproc sshd [ $RETVAL -eq 0 ] && rm -f /var/lock/subsys/sshd fi echo

Hi again, A.A wrote: > Hi Thomas, > As i wrote that's still the old Version: > /usr/local/samba-2.2.8a/bin/smbstatus --> samba version 2.2.7a-SUSE > When i type "Which smbstatus" i get /usr/bin /smbstatus this looks like a standard installation of SuSE. > > I dont know what you mean with : > For startup the samba processes you should change your

After some days, here is my personal cookbook for Samba in Solaris. I needed to share a folder in my Solaris server, but using my Windows Active Directory Account. Here are my proccess, if it can help to anyone or if anyone can make corrections or suggestions. Thx. Personal Cookbook for Samba. Objective: To enable a Unix server for share folders for Microsoft Windows machines with

This patch adds the seatbelts which _only_ kill parent sshd procs... -RMallory (eg: when you ssh into a machine and pkgadd the new openssh, it will not kill your current (or anyone else's sshd session) onanother_note: the buildpkg.sh could use some exec_prefix functionality... to deal with ./configure --prefix= --exec_prefix=/usr *** bak/opensshd.in Fri Oct 19 13:36:24 2001 ---

Hello, I was wondering about the feasibility of including a startup script for icecast for redhat/fedora installs? I've had to do an rpm install on an fc4 box, and a source install, rpms couldn't be found for an rh9 machine, yah i know that's old. And in both cases i had to drop in a custom-made startup script, see below. I was wondering esepcially in the case of the rpm, and

Hi during Startup of SuSE-Linux 7.2 Prof. the PC is sometimes ( 1 of 10 times) stopping by start smbd. Reset knop the help only. I have this problem with the samba version in SuSE package and version 2.2.5 too. In the file ../rc3.d/S12smb I added 2 lines to see if nmbd and smbd are startet. I see nmbd is starting always, the text "SAMBA smbd gestartet" is in case of fault not printing.

Hi everyone, I have the problem with Xen domU's and timekeeping in dom0. Time in dom0 was incorrect by 5 hours due to wrong timezone assumed. Fixed it by ntpdate ntp.nist.gov. The time on a dom0 was changed. I didn't append xen.independent_wallclock=1 to sysctl.conf thus the time in all domU's was also changed. But THEY DIDN'T "KNOW" THAT! The 'date' output

I figured this needed it's own thread, so apologies for spamming the list. Along with the /usr/share/perl5 issues (which I did kinda fix with a manual copy of the directory from another box), we're having an issue with SystemD (go figure) stopping the radiator service, but failing to unbind the ports (1645/1646). It's complaining about 'killproc' not found. Is there a

I've had the wrong sshd daemon killed by "killing using alternate method" too many times. Would this cause anyone any grief? --- opensshd.in.old Sun Oct 21 16:42:02 2001 +++ opensshd.in Mon Jul 15 19:34:16 2002 @@ -3,11 +3,8 @@ # # Stripped PRNGd out of it for the time being. -AWK=/usr/bin/awk CAT=/usr/bin/cat KILL=/usr/bin/kill -PS=/usr/bin/ps -XARGS=/usr/bin/xargs

Hi, one user found problem with restarting nut. upsdrvctl does not wait for drivers being really terminated. In init scripts we have following: killproc upsmon killproc upsd upsdrvctl stop and then upsdrvctl start upsd upsmon problem is upsdrvctl stop only sends terminating signals but does not wait for driver termination. This makes driver fail to start sometimes when old driver is still

(Shame on me: wrong filename in last posting, now here are correct diffs) in contrib/solaris/ (openssh-SNAP-20011017.tar.gz) 1) buildpkg.sh makes wrong link for /etc/init.d/opensshd 2) /etc/init.d/opensshd has not-working killproc here my version tested on Solaris 2.4 and 8 (no pgrep with solaris 2.4, XARGS was undefined, simpler syntax) J?rg --- contrib/solaris/buildpkg.sh Fri Oct 12

Hi, I''m just getting started with puppet, and using the RPMS provided (on CentOS 4.3), and RedHat''s killproc is annoying me again. The process is called ''ruby'' instead of ''puppetmasterd''. $ ps 7869 PID TTY STAT TIME COMMAND 7869 ? Ss 0:00 ruby /usr/sbin/puppetmasterd [ etc ] So, service puppetmaster

Hi, I installed Samba 2.0.3 on Linux 2.2.5. Every time I reboot system I found the smb has not been started. But in the directory /etc/rc.d, the file "smb" exists. When I run "smb restart",after a while, the samba server is ok. I wonder why the samba server is not up when system reboot. Thanks a lot. Followed is the content of the file "smb": #! /bin/sh ..

Hi all, I want to run 2 rsync daemons on my system. Each has its own configuration file, and they are listening on a specific port. These 2 daemons are running perfectly but getting them started by 2 init scripts is a bit more difficult. The problem is that when stopping rsync you check the pid of rsync, which results in both pids of the daemons. Off course i want the script to be very

hi, there is the output of the command samba stop and some more outputs. Maybe you see now more what do i wrong :(! balalayka:/usr/local # ls . bin include man samba-2.2.8a sbin src .. games lib samba samba-2.2.8a.tar.gz share balalayka:/ # /etc/init.d/samba stop bash: /etc/init.d/samba: No such file or directory balalayka:/ # whereis samba samba: /etc/samba

All: I am running on an AIX 5.3 platform and I am looking to see if anybody has a script similar to this (see below) that will work under AIX. My goal is, on boot up I want to have samba started automatically. Can somebody let me what I have to do (on AIX) for this to happen. #!/bin/sh # # /etc/rc.d/init.d/smb - starts and stops SMB services. # # The following

On 09-Sep-98 samba@samba.anu.edu.au wrote: > Date: Wed, 09 Sep 1998 08:48:24 +0200 > From: franca@provincia.torino.it (Franca Vercellone) I'll answer this in English (I speak and read Italian, but writing is another matter ;-) > > HO un problema grandissimo. > Tutte le volte che il server sul quale e' configurato samba reboostrappa, > non si riesce piu' a

you'll need to type './smbd -D' instead of 'smbd -D' if you're in the /usr/local/samba directory (same for nmbd -D and smbstatus). BTW, you need to type 'ps fax | grep smbd' and then 'kill -9 <process ID>', where <process ID> is listed in the 'ps fax | grep smbd' command. Same for nmbd. Also, make sure the smbd and nmbd daemons are not

I'm having problems when I restart the smb server with it not coming back up. As near as I can tell it's actually NMBD that's having the issue. I'm running RedHat 9.0 on a Compaq ML-370 with Dual 1.2GHz P3s and I just upgraded Samba to 2.2.8a-1 after having this same problem with 2.2.7a When I issue: #service smb restart It says that it shut down and restarted ok, but then nobody

Hi there, I have installed samba-2.2.2 on Redhat linux 7.0 . I have setup the whole server properly and have run the ./configure, make and make install commands successfully. I have even written a basic smb.conf file which is located in /etc/samba . The testparm on the conf file shows no errors. i have checked the /etc/services file for the netbios services and they are all done properly