similar to: dovecot initscript

I've cleaned up Pekka Savola's newly revised sshd.init and additional sshd-functions and modified them to work they way i've been arguing they should work. Compatibility functions are defined in ./contrib/redhat/sshd-functions, which should get installed no matter what release of Red Hat Linux OpenSSH is getting built for, to be consistent across releases. Specific changes from

--------------------------------------------------------------------- Red Hat, Inc. Red Hat Security Advisory Synopsis: Insecure setserial initscript Advisory ID: RHSA-2001:110-05 Issue date: 2001-09-12 Updated on: 2001-09-19 Product: Red Hat Linux Keywords: setserial initscript temporary file Cross references: Obsoletes:

Am 12.07.2016 um 21:35 schrieb Rowland penny: > On 12/07/16 20:25, Achim Gottinger wrote: >> Just backported 4.4.5 from debian sid to jessie. samba.service is >> masked there. If running as an fileserver the services are started >> via smbd.service,nmbd.service, winbind.service. >> There is an samba-ad-dc script which is masked by default. >> To get the ad-dc up

On Sat, Apr 2, 2016 at 4:05 PM, Rowland penny <rpenny at samba.org> wrote: > I compile Samba myself and I use init files, I would rather have them than > the bloat systemd comes with. They are not complex if you understand bash > and are a lot easier to understand than all that systemd comes with. At first I felt the same way but the service files are starting to seem simpler. Yes,

Moving from CentOS 5 to CentOS 7, discovered that a test in a SysV initscript for whether it is running interactively, instead of at boot time, no longer works. Under CentOS 7 / systemd, is there some way for the initscript to know this?

James Hogarth <james.hogarth at gmail.com> wrote: >On 18 Dec 2016 10:59, "whitivery" <co55-sy1t at dea.spamcon.org> wrote: > >Moving from CentOS 5 to CentOS 7, discovered that a test in a SysV >initscript for whether it is running interactively, instead of at boot >time, no longer works. > >Under CentOS 7 / systemd, is there some way for the initscript

Hello together, > * Report your success/failure! > * Samba4 as a replicating domain controller is still developing rapidly, and we > like to hear from users about their successes and failures. While Samba4 is > still in rc state we would encourage you to report both your successes and > failures to the samba-technical mailing list on

On 18 Dec 2016 10:59, "whitivery" <co55-sy1t at dea.spamcon.org> wrote: Moving from CentOS 5 to CentOS 7, discovered that a test in a SysV initscript for whether it is running interactively, instead of at boot time, no longer works. Under CentOS 7 / systemd, is there some way for the initscript to know this? Generally "interactive" init scripts are not in any way

Hi. I just noticed that the new reconfigure regression test does not work properly (the test passes but it doesn't actually test anything) when SUDO=sudo is used, because the kill -HUP is run as a normal user. This is fixed in the attached patch. -Daz. -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes

Jonathan Billings <billings at negate.org> wrote: >On Sun, Dec 18, 2016 at 08:50:54PM -0800, whitivery wrote: >> It is a system with several servers (various platforms/distros). >> >> One piece of software runs on all of the servers. For it to operate >> correctly, the instance on one server (prime) must start before the others >> (auxiliary). >>

On Sun, Dec 18, 2016 at 08:50:54PM -0800, whitivery wrote: > It is a system with several servers (various platforms/distros). > > One piece of software runs on all of the servers. For it to operate > correctly, the instance on one server (prime) must start before the others > (auxiliary). > > So a boot delay is added (via a script sourced from initscript, which > first

Hai, Really, you dont need to edit the systemd files. Try first with only the interface change. Then if you still need to edit the systemd files. You need these settings, but i dont thing you need it after the interface change. cat /lib/systemd/system/smbd.service [Unit] Description=Samba SMB Daemon Documentation=man:smbd(8) man:samba(7) man:smb.conf(5) After=network.target nmbd.service

Hello list, I would add: # dovecot Startup script for the dovecot server # # chkconfig: - # processname: dovecot # config: /path/to/config # pidfile: /path/to/pid So that it supports the chkconfig used by RHEL and clones too. Also, maybe it should be installed by the Makefile's install target? it could then also set: DAEMON=/path/to/dovecot/daemon instead of:

Does your PIDFile exist? systemd should use that if defined and exiting. https://lists.freedesktop.org/archives/systemd-devel/2013-February/009201.html Am 12.07.2016 um 22:01 schrieb Sonic: > On Tue, Jul 12, 2016 at 3:25 PM, Achim Gottinger <achim at ag-web.biz> wrote: >> This is the samba-ad-dc.service script: > Pretty similar to my samba.service script: >

Hello, we have some problems with users who report connectionproblems to dovecot sometimes. According to the logs there are dovecot reloads at this times. Seems that a reload also causes dovecot to shut all imapconnections down: Jul 16 13:31:40 myhostname dovecot: master: Warning: SIGHUP received - reloading configuration Jul 16 13:31:40 myhostname dovecot: imap: Server shutting down.

Hai Igor, No, that not normal, and this is and old bug in the start/stop. Entered after samba started to use preforking i believe. See the Unit setup below. Note, i added bind9.service here, because i use bind and i want bind to start before samba-ad. Just keep it there, if you change you samba to samba+bind_dlz, then you services are starting in the correct order. This part: # systemctl

Package: xcp-xapi Version: 1.3.2-8 Severity: important Tags: patch Found race condition (specific only to slave hosts): xcp-xapi can start earlier than xcp-networkd due lack of dependency in init.d script. Syptoms: After reboot slave's xcp does not work: xe (anything): The host failed to acquire an IP address on its management interface and therefore cannot contact the master. log:

Can you try with this systemd unit file. Restarting does not close all prosesses with that one. ( you need : ExecReload=/bin/kill -HUP $MAINPID ) Jessie used probely sysv and not systemd, which should explain why there are so many zombies. [Unit] Description=Samba AD Daemon Documentation=man:samba(8) man:samba(7) man:smb.conf(5) After=network.target [Service] Type=notify NotifyAccess=all

Hello, Timo, last year when you remoted into our server and performed the migration from courier-imap, we ran into this issue, and you solved it by doing: echo 1024 > /proc/sys/fs/inotify/max_user_instances Then you said you were going to solve this permanently by changing the init script... Here is what you said (this is from the skype chat): [2012-06-04 10:40:43 AM] timosirainen:

Hi all, A while ago I posted about needing to access samba shares on the same machine that the samba server was running on. Someone posted a script to mount the shares and all was well till I upgraded my PC hadware and had a small accident :( I have tried modifing /etc/init.d/samba adding ... mount -t smbfs //127.0.0.1/common /mnt/samba/common -o