You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@jlesage Just wanted to share information -- I have my own container I run, and it stopped working today from an update.
My container depended on PIDFILE existing. It looks like in this latest update they have stopped using a pid file, but instead the grep through ps to find the process by name. Now I just do PID=$(pgrep -f /crashplan/crashplan/bin/CrashPlanService) inside my container to find the pid to wait on:
(This is the last line of my wrapper script in the container)
PID=$(pgrep -f /crashplan/crashplan/bin/CrashPlanService)
while kill -0 $PID
do
ps -l $PID
# echo Service is still running on $PID...
sleep 30
done
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
@jlesage Just wanted to share information -- I have my own container I run, and it stopped working today from an update.
My container depended on PIDFILE existing. It looks like in this latest update they have stopped using a pid file, but instead the grep through ps to find the process by name. Now I just do
PID=$(pgrep -f /crashplan/crashplan/bin/CrashPlanService)
inside my container to find the pid to wait on:(This is the last line of my wrapper script in the container)
Beta Was this translation helpful? Give feedback.
All reactions