similar to: pgbouncer.pid Permissions on CentOS 7

hey folks, we are migrating our tomcat setup over to centos 7. Im converting init-scripts over to systemd services and whatnot.. One thing that Ive noticed is that my systemd startup script cant seem to write to /var/run as a non-root user to drop a pidfile.. If I create a directory in /var/run owned by my user, it gets wiped out on reboot. Ive searched and found this

Trying to set up a mail server under CentOS7 - having done this with CentOS5 and CentOS6 over the last decade with no issues and reliable service, it was time to upgrade (?) to CentOS7. Shouldn't be a problem, right? Getting to grips with systemd has been challenging - to say the least. So a brief overview of what I am trying to set up: postfix / amavisd-new / spamassassin / clamav so we

Yes I have /var/run/samba/ , I spotted the error with not having an actual filename while I was posting this message. Does the pid file need to be in the same path as samba ? On Thu, Nov 23, 2017 at 10:04 PM, Sonic <sonicsmith at gmail.com> wrote: > On Thu, Nov 23, 2017 at 4:46 PM, Arnab Roy <arniekol at gmail.com> wrote: > > > > PIDFile=/var/run/samba/ > > >

The default path is /var/run/tftpd-hpa.pid, which can be overridden by the newly introduced -P option. On normal termination (SIGTERM or SIGINT) the pid file is automatically removed. Moved setting the umask later, right before entering the select loop, so that it does not affect the permissions of the pid file. Signed-off-by: Ferenc Wagner <wferi at niif.hu> --- tftpd/tftpd.c | 38

This is more a question than a serious proposal. The name of the pid file should probably be configurable, and it should be unlinked on normal termination, but no such thing exists in standalone mode. SIGTERM and SIGINT should be catched and considered normal, I guess. Signed-off-by: Ferenc Wagner <wferi at niif.hu> --- tftpd/tftpd.c | 7 +++++++ 1 files changed, 7 insertions(+), 0

https://bugzilla.mindrot.org/show_bug.cgi?id=1628 Summary: /var/run/sshd.pid file collisions... Product: Portable OpenSSH Version: 5.2p1 Platform: Other OS/Version: Solaris Status: NEW Severity: normal Priority: P2 Component: Build system AssignedTo: unassigned-bugs at mindrot.org

On Thu, 4 May 2017, Jason Welsh wrote: > hey folks, we are migrating our tomcat setup over to centos 7. Im > converting init-scripts over to systemd services and whatnot.. One > thing that Ive noticed is that my systemd startup script cant seem > to write to /var/run as a non-root user to drop a pidfile.. If I > create a directory in /var/run owned by my user, it gets wiped out

If unicorn doesn''t get terminated cleanly (for example if the machine has its power interrupted) and the pid in the pidfile gets used by another process, the current unicorn code will exit and not start a server. This tiny patch fixes that behaviour. --- lib/unicorn/http_server.rb | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/lib/unicorn/http_server.rb

Ok, so i have to know the PID of ices to send the update-signal. I've added this to my ices.xml: <pidfile>/home/www/bin/ices.pid</pidfile> (directly under the node <ices>) I thought i've seen this somewhere in the manual. However, when i start ices, no pid-file is created :-/ Is this the right way? <p>----- Original Message ----- From: "Karl Heyes"

Hi all. I have a simple feature request for the devs and maintainers; when forking into the background using the -f optarg one would normally have to consult the process table of whatever OS they're running to find the process. Would you consider adding another optarg to write the PID out to stdout or a pidfile? This would be rather helpful in several usecases. Thanks, -c

I've had fun with nut on RH systems, these are my notes to get it working: Create /usr/lib/tmpfiles.d/nut-client.conf:D? ? /run/nut 0770 root nut - ...the file did not exist, and so the PID folder/file was not getting generated. Then the driver would start. Also had to setup enabled services (still not 100% confident that this is totally correct):[root at emp80 ups]# systemctl list-unit-files

https://bugzilla.mindrot.org/show_bug.cgi?id=2382 Bug ID: 2382 Summary: option to disable pid file with sshd Product: Portable OpenSSH Version: 6.9p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: sshd Assignee: unassigned-bugs at

Hi all, When I try to start libvirtd, using "libvirtd -d", error notification shown below:error : virPidFileAcquirePath:345 : Failed to acquire pid file '/$HOME/.libvirt/libvirtd.pid': Resource temporarily unavailable Using "libvirtd -v", show: "libvirtd: error: Unable to obtain pidfile. Check /var/log/messages or run without --daemon for more

https://bugzilla.redhat.com/show_bug.cgi?id=1165785 Since the --boot option is relatively new (added 2013-12), I suspect this will break older versions of systemd. However it should be fine for all currently supported versions of Fedora. Rich.

Hi, I'm moving some old stuff from EL6 to EL8 and one setup has a cron job which uses "tmpwatch -umc $dir" to clean some directories (/etc/cron.daily/tmpwatch). It seems that this triggers this AVC (SElinux mode is enforcing): type=AVC msg=audit(1598576896.772:4267): avc: denied { dac_override } for pid=11013 comm="tmpwatch" capability=1

Hi all, I use centos7 and don't want to use tmpwatch as well as crond. I have a question to use `systemd-tmpfiles-clean.service` with my custom configured file in `tmpfiles.d` to delete outdated files periodically in some log dir. I have a `tmpfiles.d` configured file in `/etc/tmpfiles.d` named `my_log.conf` in following contents. ``` #Type Path Mode UID GID Age Arg r

Currently when the appliance is booted we see warning messages like these ones: [/usr/lib/tmpfiles.d/systemd.conf:26] Failed to replace specifiers: /run/log/journal/%m [/usr/lib/tmpfiles.d/systemd.conf:28] Failed to replace specifiers: /run/log/journal/%m [/usr/lib/tmpfiles.d/systemd.conf:29] Failed to replace specifiers: /run/log/journal/%m They are apparently harmless, but are caused because

Came across this issue in 3.0.2; looks to also be present in the latest unstable sources: # ls -l /var/run/xenconsoled.pid -rwS--x--T 1 root root 5 Aug 31 00:29 /var/run/xenconsoled.pid setuid, group-execute, and sticky...? This happens because daemonize() in tools/console/daemon/utils.c isn''t specifying a "mode" parameter when creating the file: fd = open(pidfile, O_RDWR

On 4/4/19 6:22 PM, Nicolás Iglesias wrote: > Hi Fellow users > > I've just compiled latest libvirt and qemu, both from their respective official repositories. > Libvirtd starts perfect, but when I try to start a domain using the virsh console, I get the following: > > virsh # start --domain win8.1 > error: Failed to start domain win8.1 > error: internal error: Failed

Fabian Arrotin wrote: >> This message occurs in the Perl script >> /usr/share/BackupPC/bin/BackupPC : >> >> my $sockFile = "/var/run/BackupPC/BackupPC.sock"; >> unlink($sockFile); if ( !bind(SERVER_UNIX, sockaddr_un($sockFile)) >> ) { print(LOG $bpc->timeStamp, "unix bind() failed: $!\n"); >> exit(1); } >> >> As far as