search for: wantedbi

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 and running with systemd one has to unmask samba-ad-dc.service and mask smbd.service,nmbd.service, winbind.service. This is the

Am 22.10.19 um 04:52 schrieb Orion Poplawski: > On 10/21/19 3:42 PM, Leon Fauster via CentOS wrote: >> Does someone have a working tmp on tmpfs via >> >> systemctl enable tmp.mount >> >> under CentOS8/RHEL8? This seems to work straight in EL7 ... >> >> >> # LANG=C systemctl enable tmp.mount >> The unit files have no installation config

Currently we install a systemd service named firstboot.service and a SysV service named virt-sysprep-firstboot. On systems where systemd is the init system and runs with the SysV compatibility, the different names make systemd handle them as different services, and thus trying to run the firstboot script runner twice. Rename both the systemd service and the SysV one to guestfs-firstboot: the new

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

Does someone have a working tmp on tmpfs via systemctl enable tmp.mount under CentOS8/RHEL8? This seems to work straight in EL7 ... # LANG=C systemctl enable tmp.mount The unit files have no installation config (WantedBy, RequiredBy, Also, Alias settings in the [Install] section, and DefaultInstance for template units). This means they are not meant to be enabled using systemctl. Possible

Am 19.06.2017 um 11:42 schrieb Winfried via samba: > ### BEGIN INIT INFO > # Provides: samba > # Required-Start: > # Required-Stop: > # Default-Start: > # Default-Stop: > # Short-Description: ensure Samba daemons are started (nmbd and smbd) > ### END INIT INFO well, there is no ordering with network services most likely your samba starts before the network is

Hmmm, you obviously know a lot more about systemd than I do, I'm going to have to look at what you posted more carefully. Thanks. ----- Original Message ----- From: "James Hogarth" <james.hogarth at gmail.com> To: "CentOS mailing list" <centos at centos.org> Sent: Wednesday, December 23, 2015 4:08:31 AM Subject: Re: [CentOS] Starting stunnel on boot with

Hello, I'm trying to configure a daemon (I'm doing tests with "crond" daemon) to send me an email after daemon restart. My "crond.service" file is: # /etc/systemd/system/crond.service [Unit] Description=Command Scheduler After=auditd.service systemd-user-sessions.service time-sync.target #OnFailure=crond-notify-email@%i.service [Service]

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I did a little change in my howto for Gluster and CTDB. Because of a bug in all debian based distributions a glusterfs filesystem will not mount during systemstart. What I did? I removed the mountpoint from /etc/fstab and created a systemd target.mount file /etc/systemd/system/glusterfs.mount. Important is, that the name of the file MUST be the same

I run a pair of dovecot servers for personal small domains with several layers of backup in place ... - The two dovecot servers replicate to each via a Tinc vpn mesh. That gives email resiliency. - All mail is replicated via offlineimap to a 3rd server over that Tinc vpn. It's on the mesh, it has space, so why not ? - All mail is replicated as well as via mbsync to a zfs dataset on my

Hi All,I have a general question.? I have an old rc type startup script that I am still using on CentOS 7.? I got it to run by creating the systemd service file... a simple one as shown below, for Myservices. # used to set up the Myservices onstartup[Unit]Description=Start and stop Myservices[Service]Type=oneshotExecStart=/etc/init.d/Myservices startExecStop=/etc/init.d/Myservices

On my CenOS7 system with stunnel from base stunnel-4.56-4.el7.x86_64 there's a systemd service file /etc/systemd/system/stunnel.service try sudo systemctl enable stunnel.service Hope this helps, K ?al?

Hello listmates, Somehow or other my DNS services that are part of the ndjbdns-1.06-1.el7.x86_64 package would not start properly at startup. When I then start them up using systemctl: systemctl start dnscache systemctl start tinydns they start just fine. >From the log I got the following for tinydns: Oct 24 15:01:43 ns99 tinydns[1867]: tinydns: version 1.06: starting: Oct-24 2014 15:01:43

Depending on the OS. Below is tested/in production since samba 4.9.x and debian stretch Currently running buster with samba 4.12.5 with samba and AD-Backends. All users have UID assigned, and "Domain Users". This is really easy on any setup with systemd systems with samba and winbind. I'll show how easy this is for any debian/ubuntu related system but using systemd, maybe you

Hi everyone, I have a samba DC, let's call it dc1.ad.example.com. I have two members of the domain - server1.ad.example.com and server2.ad.example.com.?? They are not running smbd and winbind. Instead, they are running SSSD with AD backend. I want to create an NFSv4 export on server1.ad.example.com and mount it on server2.ad.example.com (say, sec=krb5). I found some instructions online

Hi Marco, You will hit muliple problems, most can be solved. Im installing a new member here with samba 4.8.5 and building new samba 4.8.6 atm. ;-). Im (trying to ) fix this also again in this new setup. Below it a bit of what i know. > Client are in DHCP, so it is hard to use 'normal' NFSv3 mount, eg > security by IP. If they register ( or are registered) in the dns correctly

I have only verified the fix on Debian 7. The Debian 6 guest doesn't appear to boot, I'm not sure why. The second patch contains a test suite. Rich.

We try to run a reliable ssh tunnel vis systemd. This is the unit configuration file: {{{ [Unit] Description=Tunnel For %i After=network.target [Service] User=autossh ExecStart=/usr/bin/ssh -o "ExitOnForwardFailure yes" -o "ServerAliveInterval 60" -N -R 40443:installserver:40443 -R 8080:installserver:8080 ExecStartPre=-/usr/bin/ssh tunnel@%i "for pid in $$(ps -u

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

I just noticed that by running by commands /usr/sbin/smbd -D or /usr/sbin/smbd -i without systemd's unit, all shares work perfectly so the problem must then be somehow related to systemd.. Let the testing continue.. I also tested what happens if I comment out everything and just use ExecStart=/usr/sbin/smbd -D as that command worked on the console. That did not help. For the record, this is