search for: pid_fil

...lps. __ Donnie Jones svn diff Index: init.rb =================================================================== --- init.rb (revision 519) +++ init.rb (working copy) @@ -24,7 +24,7 @@ } conf = YAML.load_file(@config_file) @options.merge! conf if conf - @pid_file = @options["pid_file"].split(".") + @pid_file = @options["pid_file"].split(".pid") start_port = end_port = @only start_port ||= @options["port"].to_i @@ -34,7 +34,7 @@ end def port_pid_file(port) - &...

....1p1.org/ssh.c openssh-5.1p1.new/ssh.c --- openssh-5.1p1.org/ssh.c 2008-07-04 04:53:50.000000000 +0200 +++ openssh-5.1p1.new/ssh.c 2009-02-18 21:15:26.000000000 +0100 @@ -140,6 +140,9 @@ /* optional user configfile */ char *config = NULL; +/* file to write the pid in after daemonizing */ +char *pid_file = NULL; + /* * Name of the host we are connecting to. This is the name given on the * command line, or the HostName specified for the user-supplied name in a @@ -185,6 +188,7 @@ " [-l login_name] [-m mac_spec] [-O ctl_cmd] [-o option] [-p port]\n" " [-R [...

I need a way to kill the ferret_server drb process programatically, so I can start/stop it as part of the capistrano deployment process. This should be as simple as adding some sort of stop method to ActsAsFerret::Remote::Server. I was just messing around and was able to do it by modifying method_missing to look for the :stop method and then calling DRb.thread.exit -- this is not good enough for

...ux so the rest are up to you. Thanks to the following for patches, bug reports, and suggestions: Corey Donahue, Matt Trott, Donnie Jones, Matte Edens, Joey Geiger, Nathan Vack, and others. New Features: * The cluster::start, stop and restart commands now support --clean. On start, any orphaned pid_files will be removed and any missing members will be started. Running members will be ignored. On stop, orphaned members (with missing pids) will be killed. On restart, --clean will be passed to stop and start. Feel the healing power of the pack! * cluster::status - Reports the status of the clust...

...#!/bin/sh # sshd startup script for FreeBSD 3.5-STABLE, should work elsewhere # Name it /usr/local/etc/rc.d/sshd.sh # Note without the .sh it won't execute from boot # darren at horseplay.demon.co.uk PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/sbin:/usr/local/bin bindir=/usr/local/sbin pid_file=/var/run/sshd.pid export PATH mode=$1 case "$mode" in 'start') # Start daemon if test -x $bindir/sshd then $bindir/sshd else echo "Can't execute $bindir/sshd" fi ;; 'stop') # Stop daemon. if test -f &quot...

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.

...g/smblogs set -o noclobber # Set stderr exec 2>> $SMBLOGS/staleSessions.log print -u2 -- "$@" SELF=${0##*/} OP=$1 SMBPID=$2 SMBCLIENT=$3 SMBSERVER=$4 SMBSERVICE=$5 SMBUSER=$6 status="" # This sets the name of the pid file for this # {client, server, share, user} tuple PID_FILE=$SMBLOCKS/$SMBCLIENT-$SMBSERVER-$SMBSERVICE-$SMBUSER.pid ### ### The idea is to store the calling smbd's pid in $PID_FILE so that it ### can be killed if the client reconnects through a different TCP session. ### case $OP in preexec) while [[ -f "$PID_FILE" ]] do PID=$(cat...

...ng in the mongrel_cluster config file. mongrel_cluster does not use the working directory setting until it is past that point and finally calling the mongrel_rails command. Thus, it isn''t going to find the pid files if you are also susceptible to problem #2. 2) A relative directory :pid_file setting in the mongrel_cluster config. If you''re like me, your :pid_file setting is "log/mongrel.pid". Using a relative directory like that is supposed to be based on the value of the :cwd setting. But mongrel_cluster is not applying the :cwd setting when parsing the :pid...

I''m looking at implementation of Mongrel::Stop.run: def run if @force @wait.to_i.times do |waiting| exit(0) if not File.exist? @pid_file sleep 1 end Mongrel::send_signal("KILL", @pid_file) if File.exist? @pid_file else Mongrel::send_signal("TERM", @pid_file) end end and a question arises: is there any good reason not to rm_f(@pid_file) after sending that SIGKIL...

...lean up after itself, so it does not remove the PID files. As an example: $ sudo /etc/init.d/mongrel-cluster start Starting mongrel-cluster: Starting all mongrel_clusters... mongrel-cluster. $ sudo cat tmp/pids/mongrel.8203.pid | xargs kill -9 $ sudo /etc/init.d/mongrel-cluster status (...) found pid_file: tmp/pids/mongrel.8203.pid missing mongrel_rails: port 8203 (...) $ sudo /etc/init.d/mongrel-cluster restart Restarting mongrel-cluster: Restarting all mongrel_clusters... ** !!! PID file tmp/pids/mongrel.8203.pid already exists. Mongrel could be running already. Check your log/mongrel.8203.log...

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 Shouldn't there be RETVAL=$? after killproc sshd ? If this is the case here's a patch: --- sshd.init~ Mon Oct 16 04:25:1...

...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 RUBY_PLATFORM !~ /mswin/ log "Writing PID file to #{@pid_file}" open(@pid_file,"w") {|f| f.write(Process.pid) } end end The comment''s wrong, and we probably need a File.chmod call there somewhere. Should I submit a patch ? Thanks !...

...l log/mongrel.log -e production -d -a 127.0.0.1 -p 6833 -G config/mongrel.yml Which also worked, and generated a YAML file with my options: --- :cwd: /home/mcornick/rails/mcornick.org/current :includes: - mongrel :environment: production :timeout: 0 :log_file: log/mongrel.log :config_script: #:pid_file: log/mongrel.pid :num_processors: 1024 :debug: false :group: :docroot: public :user: :host: 127.0.0.1 :mime_map: :port: "6833" :daemon: true And it almost works. If I then try: $ mongrel_rails start -C /home/mcornick/rails/mcornick.org/current/config/mongrel.yml ** You have sendfile...

...right) I haven''t touched this file since development mode, so was wondering if anyone knew where i need to turn to work out what''s what with this... the default file (which must have been created at the time of installation is below: production: host: localhost port: 9010 pid_file: log/ferret.pid log_file: log/ferret_server.log log_level: warn can anyone help? I''m so close to having a fully working app! :-) thanks -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send e...

I wanted to show a Rails site to someone so I set up Mongrel and it ran fine, This is my mongrel_cluster.yml, port: ?80" environment: production pid_file: log/mongrel.pid servers: 4 Now, after going back to Apache/Tomcat I can''t get the Mongrel site up and running again...? Any suggestions? (When I run Mongrel, I stop Apache first) Jim

...ne, I am going crazy over here! :) I just want to be able to use --clean with my mongrel_rails cluster::start command. I''ve upgraded to mongrel_cluster 1.0.1.1 and mongrel_rails 1.0.1. my config file is in /etc/mongrel_rails/config.yml and contains: --- log_file: log/mongrel.log port: 8000 pid_file: /var/run/mongrel_cluster/mongrel.pid servers: 2 address: 127.0.0.1 environment: production in the following post it says the init.rb script from mongrel_cluster should create the var/run directory itself, but it does not seem to do so ( I get the message: !!! Path to log file not valid: log/mong...

...------------------------------------------------------------- #!/bin/sh # # description: starts/stops the ices audioencoder # # chkconfig: 345 99 20 # # Source function library. . /etc/rc.d/init.d/functions ICES_BIN="/opt/ices2/bin/ices" ICES_CONF="/opt/ices2/etc/ices-live.xml" PID_FILE="/var/run/ices2_station.pid" # See how we were called. case "$1" in start) echo "Setting line in mixer value's" action /usr/bin/aumix -L -f /root/.aumixrc >> /dev/null echo "Starting Ices station encoder" ${ICES_B...

...d also have monit restart the mongrels after logrotate does it''s thing. Any quick suggestions/examples on a script for monit/logrotate? Thanks BTW I''m using the following cluster config: --- prefix: /myAPP cwd: /web/servers/rails/current port: "8001" address: 127.0.0.1 pid_file: log/mongrel.pid servers: 4

I''m having no luck trying to daemonize mongrel running a camping server. When mongrel daemonizes, I get: /usr/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb:723:in `accept'': closed stream (IOError) from /usr/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/configurator.rb:293:in `join'' ... (This was after I disabled the unhandled exception catchall in the

Not sure this is known behaviour but it seems that if want to set the environment to, for example, test, and you want to use Active Record you have to both explicitly set the RAILS_ENV and the BackgrounDRb environment. So, if you have a config file backgroundrb_test.yml (as well as the default) and set the environment to test in that, this is what *seems* to happen: $