[FastCgi] Don't delete the socket file if it doesn't match the original #12

Merged
merged 3 commits into from May 14, 2013

Projects

None yet

2 participants

@knocte

A good practice for deploying a new version of a web app is to do it over
the same unix domain socket of the previous release (overwriting it). In
this case, it is not desirable that Mono.FastCgi deletes the socket file
when the previous release is killed, as it would remove the socket file
of the new release.

The best way to check if we can delete the socket file is to store the
inode of the file when the unix domain socket file is created, and check
that it is the same before deleting it, at dispose time.

knocte added some commits May 14, 2013
@knocte knocte [FastCgi] Add missing header for UnixSocket.cs file 6417cb2
@knocte knocte [FastCgi] Don't delete the socket file if it doesn't match the original
A good practice for deploying a new version of a web app is to do it over
the same unix domain socket of the previous release (overwriting it). In
this case, it is not desirable that Mono.FastCgi deletes the socket file
when the previous release is killed, as it would remove the socket file
of the new release.

The best way to check if we can delete the socket file is to store the
inode of the file when the unix domain socket file is created, and check
that it is the same before deleting it, at dispose time.
a4743a7
@knocte knocte [configure] Bump version from "2.11" to "3.0", and fix bugtracker link 7b6cf02
@grendello grendello merged commit 4587438 into mono:master May 14, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment