similar to: [Bug 606] sshd [-t] should warn when cannot create pid file

Hey folks. Sorry for the SUPER long email but if you''ve been experiencing the same problems with restarting your mongrel cluster with Capistrano, then I have two solutions that have worked for me and I''m pretty sure will for you as well. THE PROBLEM I was having trouble restarting my clusters using Capistrano. I''ve seen this come up before on the mailing list and

https://bugzilla.mindrot.org/show_bug.cgi?id=1433 Summary: sshd.pid has permissions of 666 Classification: Unclassified Product: Portable OpenSSH Version: 4.7p1 Platform: HPPA OS/Version: HP-UX Status: NEW Severity: security Priority: P2 Component: sshd AssignedTo: bitbucket at mindrot.org

Hi, I have an application which is dying horrible deaths (i.e. segmentation faults) in mid-flight, in production... And of course, I should fix it. But while I find and fix the bugs, I found something I think should be different - I can work on submitting a patch, as it is quite simple, but I might be losing something on my rationale. When Mongrel segfaults, it does not -obviously- get to clean

Hi, Is there any way to store HostKey in hardware (and delegate the related processing)? I have been using Roumen Petrov's x509 patch for clients, which works via an OpenSSL engine, but it does not seem to support server HostKey: http://roumenpetrov.info/pipermail/ssh_x509_roumenpetrov.info/2012q4/000019.html For PKCS#11, I have found an email on this list from a year back suggesting this

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

While I could figure this out, I''m asking here first to see if anyone has already dealt with/created this. I''m running a mongrel cluster, running 4 mongrels on ports 8001-4. I''m using capistrano to deploy. And I''d like to use monit to check to make sure everything is running nice. I''d like to have monit restart only single mongrels if they fail, and

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

Hello, Thank you for your development of Mongrel, great job. :) I am using mongrel_cluster, but I have a problem where my rails application name includes a "." such as mydomain.com, which causes an error when generating the PID file for mongrel. I have attached below a diff of the current working copy in the trunk and the changes I made to overcome this problem. I kept your

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

The full description of this bug is here: https://bugzilla.redhat.com/show_bug.cgi?id=838592 and the effect it has on OpenStack is described here: https://bugzilla.redhat.com/show_bug.cgi?id=835466#c9 Rich.

Hi there, I''m using Mongrel (0.3.13 prerelease, installed today) to serve up some Rails apps in production. Everything works fine if I give all the appropriate options on the command line, such as: $ mongrel_rails start -c /home/mcornick/rails/mcornick.org/current -P log/mongrel.pid -l log/mongrel.log -e production -d -a 127.0.0.1 -p 6833 So, having accomplished that, I thought it

Hi ! I''m using Mongrel 1.0.1 with --pid and --user/--group. The PID files are correctly owned by the user/group, but their permissions is 0666. Is that normal ? Shouldn''t it be something like 0664 ? Just curious to know if I''m wrong. Configurator has this (line 77): # Writes the PID file but only if we''re on windows. def write_pid_file if

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

Could people please test -current? We will be making a release fairly soon. -d -- | By convention there is color, \\ Damien Miller <djm at mindrot.org> | By convention sweetness, By convention bitterness, \\ www.mindrot.org | But in reality there are atoms and space - Democritus (c. 400 BCE)

http://bugzilla.mindrot.org/show_bug.cgi?id=605 Summary: make install don't create piddir Product: Portable OpenSSH Version: -current Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: Build system AssignedTo: openssh-bugs at mindrot.org ReportedBy:

Hi all, I'm wondering whether it is feasible or not to run two distinct sshd daemons with different config options! I have a CentOS 4.4 gateway with 2 Ethernet interfaces. One is connected to the Internet and the other to the LAN. Basically, what I would like to do is having a sshd that listens to the LAN interface with password enabled auth. and a sshd bound to the Internet interface with

after I check sshd.init file, I found: you use 'daemon' function to start sshd. but 'daemon' will not start a daemon if the daemon process already exist, isn't it right?

Hi, We would like to use openssh in fips mode. It looks it is not provided as a configurable option through sshd_config, Are there plans to do incorporate such change. Do we have to change openssh code for now until the option is provided. If sshd is operating in fipsmode, does it provide additional errors/audits to indicate failures such as pair wise consistency failed during on of the sshd

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

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"