similar to: Bug#717575: xcp-storage-managers: Wrong path of pidof in /usr/lib/xcp/sm/iscsilib.py

Package: xcp-storage-managers Version: 0.1.1-2 Severity: important Dear Maintainer, I can not create an iSCSI storage resource using the following command: xe sr-create host-uuid=<my-host-uuid> content-type=user name-label="LVM over iSCSI SR"> shared=true device-config:target=192.168.10.100 device-config:targetIQN=<here-target-iqn>

Package: xcp-storage-managers Version: 0.1.1-3 Severity: normal XCP cannot use iscsi block devices. Fails with iscsiadm: No active sessions. I ran the following commands trying to diagnose the problem: First introducing a SR and then creating a PBD with the needed configuration for the iscsi block device. These steps work fine but when I tried to plug the PBD I got the error: root at

Package: xcp-storage-managers Version: 0.1.1-2 Severity: important I still am not able to create iSCSI storage repositories using this command xe sr-create host-uuid=<my-host-uuid> content-type=user name-label="LVM over iSCSI SR"> shared=true device-config:target=192.168.10.100 device-config:targetIQN=<here-target-iqn> device-config:SCSIid=<my-scsi-id>

Package: xcp-storage-managers Version: 0.1.1-3.1 Severity: normal User: mayhem at forallsecure.com Usertags: mayhem tp crashes with exit status 139. We confirmed the crash by re-running it in a fresh debian unstable installation. The attachment [1] contains a testcase (under ./crash) crashing the program. It ensures that you can easily reproduce the bug. Additionally, under ./crash_info/, we

> > You can probably replace that with a much cleaner pid=$(pidof cassandra). Good to know! I hadn't heard of pidof before. However this is what I get when I run it: [root at web1:~] #pidof cassandra [root at web1:~] # Returns nothing. However: [root at web1:~] #pidof java 27210 11418 10852 Gives me a few pids. Only one of which belongs to cassandra, as I have a few java processes

The path of 'pidof' binary is also incorrect. Needed to change it from /sbin/pidof to /bin/pidof I believe it is not necessary to open a new bug report... Leonardo Bruno -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20121029/14c3ad4a/attachment.html>

Dave St John wrote: > Before the official release of icecast2 1.0 (non beta) i would like to see > pid file management, > ive discussed this before on how to capture the pid, but ended up with alot > of bash rigamaroo that mounted to even more > headaches. If I understand you correctly, all you want is the PID of the Icecast process and not of its children (probably to be able to

Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Sun, 04 Nov 2012 18:54:52 +0000 Source: xcp-storage-managers Binary: xcp-storage-managers Architecture: source amd64 Version: 0.1.1-3 Distribution: unstable Urgency: low Maintainer: PKG-Xen Devel <pkg-xen-devel at lists.alioth.debian.org> Changed-By: Thomas Goirand <zigo at debian.org> Description:

dont worry Dave, it'll be committed soon and will be in the next beta...definately in 2.0 oddsock At 03:43 PM 12/1/2003 -0700, you wrote: >Thanks for the snippet, albeit id still like to see it added :) > > > PID files are quite useless junk on the harddisk in most cases... IMO > > they make only sense if you have to run a program in the foreground and > > send

tried that already but it doesnt catch the parent, it captures one of the children. Would the fact that the server runs as a user and not as root having anything to do with $! not working, since it works with shoutcast running as root? <p>Dave St John (CEO) Mediacast1.com ----- Original Message ----- From: "Karl Heyes" <karl@xiph.org> To: <icecast@xiph.org> Sent:

Hellos, Yes, I did some tests with "OnFailure" attribute, but the result was the same: system didn't sent any mail. Daemon and script files were: * crond.service: * [Unit] Description=Command Scheduler After=auditd.service systemd-user-sessions.service time-sync.target OnFailure=crond-notify-email.service [Service] EnvironmentFile=/etc/sysconfig/crond

On Mon, 2003-11-03 at 21:53, Dave St John wrote: > Anyone know of or how to capture the pid via the command line in bash? pidof ??? $ pidof httpd 827 825 824 788 -- Drew <p>--- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only

Hello, I am running a Samba 4 DC, recently upgraded to the latest version and I have just installed a member server to run as a File Server (Samba 4.1.9). While it seems to be working properly, we are getting a lot of zombie nmbd processes on the member server, running the command *pidof nmbd* results in: *[root at BHFS01 etc]# pidof nmbd* *12861 12644 12404 12236 12071 11885 11720 11553 11388

We are unfortunately still seeing a lot of these errors once the machine reaches a high number of concurrent users/logins (just below 20k simultaneous IMAP connections on a powerful 24 core machine with 128GB RAM): 2020-01-14T09:18:58.661349+01:00 dovecot: imap-login: Warning: net_connect_unix(imap) succeeded only after retrying - took 140330 us 2020-01-14T09:18:58.854692+01:00 dovecot:

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]

Thanks for the snippet, albeit id still like to see it added :) > PID files are quite useless junk on the harddisk in most cases... IMO > they make only sense if you have to run a program in the foreground and > send signals like SIGUSR1 to it (those that don't have hotkeys like > CTRL+C). Besides, they come with their own set of potential problems. > Anyways - Icecast2 is very

The conf/redhat/client.init script (installed in /etc/init.d) in 0.24.6 has this "status" method: status) status -p "$pidfile" $puppetd RETVAL=$? ;; Unfortunately the ''-p "$pidfile"'' option is available in Red Hat Server 5 but not earlier versions, where it produces an error: $ cat /etc/redhat-release Red Hat Enterprise

Gesti? Servidors wrote: > > 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 >

Hi, it seems there is no difference in "systemctl status crond" :( El 22/11/2019 a las 13:00, centos-request at centos.org<mailto:centos-request at centos.org> escribi?: Message: 3 Date: Thu, 21 Nov 2019 14:41:25 +0100 From: Leon Fauster <leonfauster at googlemail.com><mailto:leonfauster at googlemail.com> To: centos at centos.org<mailto:centos at centos.org>

I need ssh-add to fail cleanly if it tries and fails to read a key, rather than prompting the user. I can't seem to figure out how to do that. This is on a Linux 2.6.26 system, running OpenSSH 5.1p1 (as built on debian lenny/sid) First, the things i've tried: * i've unset the DISPLAY and SSH_ASKPASS environment variables, so no X11-style prompting should happen. * i've