similar to: problem with restarting nut

Hi, I've found that upsdrvctl crashes when there is not ports= specified ups.conf #0 __strrchr_sse2 () at ../sysdeps/x86_64/strrchr.S:33 #1 xbasename (file=0x0) at common.c:266 #2 stop_driver (ups=0x1e163e0) at upsdrvctl.c:135 #3 send_all_drivers (command=0x4020f0 <stop_driver>) at upsdrvctl.c:446 #4 main (argc=1, argv=0x7ffff30be9c0) at upsdrvctl.c:565 stop_driver

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

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, Every time that I have to restart the nut-server it's a nightmare. For example, after editing ups.conf In many cases the only "solution" is to reboot the system. These are the errors: systemctl -l status nut-driver ? nut-driver.service - Network UPS Tools - power device driver controller Loaded: loaded (/usr/lib/systemd/system/nut-driver.service; static; vendor preset:

Hi I am using centos 6.3, and nut-2.6.5-2.el6.x86_64. could you explain why not sending "a delayed command to the UPS to turn it off" may cause that issue? I saw: ups.delay.shutdown: 20 ups.delay.start: 30 is it something related? thanks min On Sat, May 7, 2016 at 3:44 PM, Roger Price <roger at rogerprice.org> wrote: > On Sat, 7 May 2016, Min Wang wrote: > > Hi

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

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

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 ---

My understanding is that NUT provides a mechanism to shut down multiple systems protected by multiple UPS's in a given order. For example to shutdown the users before their NFS server. 1. man ups.conf says sdorder Optional. When you have multiple UPSes on your system, you usually need to turn them off in a certain order. upsdrvctl shuts down all the 0s, then the 1s, 2s, and so on. To

Hi centos 6.3 uses traditional SysV script ( not systemctl) here is the /etc/init.d/ups ( script) assuming it similar to nutshutdown # more /etc/init.d/ups #! /bin/bash # # ups: Starts the Network UPS Tools # # chkconfig: - 26 74 # description: Network UPS Tools is a collection of programs which provide a common \ # interface for monitoring and administering UPS hardware. # processname: upsd #

(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

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

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 ..

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

Hi, you've probably heard about systemd already. In Fedora 15, it's used as default instead old SysV init system. While there is some backward compatibility layer, everything is going to be ported from /etc/init.d/<something> init scripts to systemd's service files /lib/systemd/system/<something>.service Unfortunately?, systemd is not 1:1 compatible with old init

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

If I understand correctly, in order to have the smb.conf file applied you need to restart smbd. Is "service smbd reload" sufficient (which does a "killproc smbd -HUP")? Will this kill any active connections to samba resources causing user disruption? Or is this a seamless process that can be carried out midday? I ask because if I need to kill all user connections to