-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >Subject: Re: "Couldn't lock /var/mail/russ?<wbr/>" message when trying to >access
srevilak> find /var/mail/ -type f -name \*russ\* russ> Hi Steve, russ> russ> When i ran the command, this was the output: russ> russ> russ> /var/mail//russ russ> russ> Is there any other commands i can run. What does this mean? There are several locking stratgies that can be used in a mail spool directory. A common one is "dotlock", where FILE.lock is used as an advisory lock on FILE. (The manpage for mutt_dotlock(1) describes the general process.) I was curious as to whether find would show a `/var/mail/russ.lock'. If that file existed, then you may have been able to resolve the "Couldn't lock" issue by removing `russ.lock'. However, your find output indicates that a russ.lock wasn't the problem. >I was unable to resolve this, so i ended up recompiling mutt, and so far >everything seems fine. On my system, mutt_dotlock is installed setgid mail; the setgid bit allows mutt_dotlock to create a file in /var/mail, despite the fact that I, an ordinary user, cannot create a new file in that directory. It's possible that your copy of mutt_dotlock lost its setgid bit, and recompiling/reinstalling restored the setgid bit. But hey, as long as it's working now :) Steve -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (Darwin) iEYEARECAAYFAkpuV80ACgkQX7YJI4BuyDTCUgCeM7KE35+rZOAwNGasciywR8vi fUAAn0PSe/y7RUzz3vwIyI18kDKZbBKa =NeM2 -----END PGP SIGNATURE-----
