Logger keeps from umounting: target is busy.

[ManuLinares]

Can't umount because it says target is busy.
Cheked via ls -l /proc/*/fd and see that the pidof "logger" is keeping it.

 ps axun| grep logg
    1000   29522  0.0  0.0  12260  4900 ?        S    17:02   0:00 logger -t gocryptfs-29507-logger

I see this in gocryptfs: https://github.com/rfjakob/gocryptfs/blob/master/daemonize.go#L75

Using log/syslog is standard: https://pkg.go.dev/log/syslog
Handling panics with recover(): https://go.dev/ref/spec#Handling_panics

---

System Archlinux:
go 2:1.22.3-1
gocryptfs 2.4.0-1
linux 6.8.9.arch1-2

[rfjakob]

Hi, what does `lsof -p 29522` say? Gocryptfs uses logger because in-process logging is fundamentally flawed, but that's a different discussion.

…

On Fri, 17 May 2024, 01:45 Manu Linares, ***@***.***> wrote: Can't umount because it says target is busy. Cheked via ls -l /proc/*/fd and see that the pidof "logger" is keeping it. ps axun| grep logg 1000 29522 0.0 0.0 12260 4900 ? S 17:02 0:00 logger -t gocryptfs-29507-logger I see this in gocryptfs: https://github.com/rfjakob/gocryptfs/blob/master/daemonize.go#L75 Using log/syslog is standard: https://pkg.go.dev/log/syslog Handling panics with recover(): https://go.dev/ref/spec#Handling_panics — Reply to this email directly, view it on GitHub <#846>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACGA72OL5YP2LYBYBCEEN3ZCVAIFAVCNFSM6AAAAABH3EIV7SVHI2DSMVQWIX3LMV43ASLTON2WKOZSGMYDCNJVGY2TGNQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[rfjakob]

Found a bug related to logger fds, fixed via da87308 . Thanks for the report!

[ManuLinares]

Great, than you!