sh and sshfs-static processes remain after unmounts - no Force Eject involved

[GoogleCodeExporter]

A few days ago Mac OS failed to shut down in the normal way. Faded as far as 
the blue screen 
but no further. After waiting for a long time I went downstairs to a Windows 
computer on the 
same LAN (home) and connected via ssh to my Mac to (a) top and then (b) sudo 
halt. 

top 
on its own revealed a surprisingly large number of 
sh 
processes

I opted to 
sudo kill 
each of the PIDs that related to a 
sh 
process

AFAIR as I killed the last of these sh processes, my Mac proceeded to shut down 
gracefully. 

## 

Back on topic: 
MacFusion and/or MacFUSE and/or sshfs-static

This evening at home I observed that memory usage was much higher than 
expected, so I 
launched Activity Monitor to figure out what might be going on. Ignoring memory 
usage for a 
moment, the things that immediately caught my eye amongst the list of processes 
were

sh
sh
sshfs-static
sshfs-static

Curious, because at no point since I had started up (that morning) had I force 
ejected any 
volume. I wondered about my tests under issue 25, and my noting in issue 109 
that on two 
occasions 

> with MacFusion set to 
> 
>   Unmount on Sleep, Remount on Wake
> 
> prior to each sleep, Growl notified me that
> 
>   *   MacFusion failed to Unmount the volume

(with no apparent detriment to my subsequent work after each awakening).

## 

By coincidence that evening, I had moved my MacFusion.app to Trash to make way 
for a new 
version (checked out from Subversion). (Issue 60 describes why MacFusion could 
not be 
overwritten whilst volumes were mounted and sshnodelay.so was in use; I should 
add a new 
comment to that issue.)

I opened Activity Viewer inspection windows for each of the four

sh
sh
sshfs-static
sshfs-static

and put myself (not the computer) to sleep. When I awoke a few hours later I 
noted that the two 
sh processes: 

  * included amongst their list of Open Files and Ports
    the MacFusion.app (or something in the application bundle)
    that was in Trash

  * were terminated. 

Accidentally (bearing in mind, I had just woken up) I Quit from Activity 
monitor so I lost the 
activity windows for each of the terminated sh processes :( but for the record 
the Open Files and 
Ports and Samples for both sshfs-static process are at 

<http://pastie.textmate.org/61922>
<http://pastie.textmate.org/61923>

## 

An attempt to empty Trash, with no sshfs volumes mounted, results in the 
following error: 

> Trash
> The operation cannot be completed because the item 
> "sshfs-static" is in use. 
> [Stop] [Continue]

I opted to Stop. 

In Activity Monitor, attempts to Quit normally from each of the sshfs-static 
processes failed. 
Force Quits were successful after which Trash emptied successfully. 

## 

Also for the record: 

console.log filtered to show 
macf <http://pastie.textmate.org/61875>

console.log filtered to show 
ssh <http://pastie.textmate.org/61874>

system.log filtered to show 
macf <http://pastie.textmate.org/61876>

##

I hesitated before adding this issue to the MacFusion Project. Wonder whether 
it belongs in the 
MacFuse Project. In today's case these 'remarkable' processes _might_ have been 
associated with 
sleep/wake behaviour preferred by the user through MacFusion. On the earlier 
occasion (when 
my Mac failed to shut down and I had to ssh in remotely to kill the many sh 
processes) (right 
now, I'm filing this issue before I attempt to shut down) sleep/wake behaviour 
would have been 
different (_probably_ the MacFusion default). On both occasions it's almost 
certain that I had 
used MacFusion at some time during the day. On the previous occasion it's 
_possible_ that I had 
used sshfs-static (bundled within MacFusion) from the command line. 

These sh (and sshfs-static) processes 
running in the absence of sshfs 
connections concern me only because on the previous occasion I associated a 
large number of 
sh processes with a failure of Mac OS to shut down normally. 

Original issue reported on code.google.com by grahampe...@gmail.com on 16 May 2007 at 12:52

[GoogleCodeExporter]

See also 
MacFusion issue 118

Original comment by grahampe...@gmail.com on 16 May 2007 at 12:07

[GoogleCodeExporter]

In this issue 116: no Force Eject occurred. 

In another issue 118: I opted for a Force Eject (during a very long waiting 
period).

In *both* cases: I was left with an sshfs-static process running after the 
volume had been unmounted

Original comment by grahampe...@gmail.com on 16 May 2007 at 4:58

[GoogleCodeExporter]

Original comment by grahampe...@gmail.com on 16 May 2007 at 4:59

• Changed title: sh and sshfs-static processes remain after unmounts - no Force Eject involved

[GoogleCodeExporter]

If it's relevant ... org.macports.OpenSSH ...
<http://pastie.textmate.org/62665>

Original comment by grahampe...@gmail.com on 18 May 2007 at 3:04

[GoogleCodeExporter]

Original comment by grahampe...@gmail.com on 24 May 2007 at 10:18

• Added labels: fs_sshfs