Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*lock\s+files\s+after\s+crash\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*lock\s+files\s+after\s+crash\s*$/: 20 ]

Total 20 documents matching your query.

1. lock files after crash (score: 1): Author: "D. Stimits" <stimits@xxxxxxxxxx>; Date: Wed, 12 Sep 2001 01:00:27 -0600; I have an SMP system set to boot to X11/runlevel 5 that is RH 7.1 based (root is XFS). I had a crash at the moment I attempted to start login as a regular user (home is also XFS). It seems that ~/.IC; /archives/xfs/2001-09/msg00263.html (8,388 bytes)
2. Re: lock files after crash (score: 1): Author: Seth Mos <knuffie@xxxxxxxxx>; Date: Wed, 12 Sep 2001 09:13:06 +0200; At 01:00 12-9-2001 -0600, D. Stimits wrote: I have an SMP system set to boot to X11/runlevel 5 that is RH 7.1 based (root is XFS). I had a crash at the moment I attempted to start login as a regular; /archives/xfs/2001-09/msg00264.html (9,196 bytes)
3. Re: lock files after crash (score: 1): Author: "D. Stimits" <stimits@xxxxxxxxxx>; Date: Wed, 12 Sep 2001 02:21:59 -0600; In this case the file is .ICEauthority, not related to Netscape. What I am thinking about is fcntl(). I'm wondering about how these are implemented: F_GETLK, F_SETLK and F_SETLKW. If fcntl locks depe; /archives/xfs/2001-09/msg00265.html (10,653 bytes)
4. Re: lock files after crash (score: 1): Author: Simon Matter <simon.matter@xxxxxxxxxxxxxxxx>; Date: Wed, 12 Sep 2001 18:04:46 +0200; from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 51F4C57306; Wed, 12 Sep 2001 18:04:47 +0200 (CEST) Cc: "XFS: linux-xfs@xxxxxxxxxxx" <linux-xfs@xxxxxxx; /archives/xfs/2001-09/msg00270.html (11,895 bytes)
5. Re: lock files after crash (score: 1): Author: "D. Stimits" <stimits@xxxxxxxxxx>; Date: Wed, 12 Sep 2001 15:18:32 -0600; Since nobody has said anything, let me rephrase the question. There are custom lock file schemes, which I am not interested in. There *is* fcntl to perform locking. Ignoring lock files, is there any; /archives/xfs/2001-09/msg00277.html (9,474 bytes)
6. Re: lock files after crash (score: 1): Author: Steve Lord <lord@xxxxxxx>; Date: Wed, 12 Sep 2001 17:30:16 -0500; I did respond - twice, but I am operating on a temporary workstation here due to a head crash and my mail setup appears not to be all it could be. In my second response, I looked more closely at the; /archives/xfs/2001-09/msg00280.html (10,912 bytes)
7. Re: lock files after crash (score: 1): Author: "D. Stimits" <stimits@xxxxxxxxxx>; Date: Wed, 12 Sep 2001 17:49:57 -0600; Is it safe then to say that "...mode word of the inode that mandatory locking should be used..." does not actually get preserved in the metadata? It could be apples and oranges comparison, that manda; /archives/xfs/2001-09/msg00281.html (11,920 bytes)
8. Re: lock files after crash (score: 1): Author: thomas graichen <list-linux.sgi.xfs@xxxxxxxxxxx>; Date: Fri, 21 Sep 2001 22:25:20 +0200; i observed something similar too - the reason why logging in is not really possible is the existence of some .ICEauthority-* files - simply removing them should fix the problem - so there is no magic; /archives/xfs/2001-09/msg00558.html (9,595 bytes)
9. Re: lock files after crash (score: 1): Author: "D. Stimits" <stimits@xxxxxxxxxx>; Date: Mon, 24 Sep 2001 01:27:13 -0600; I've noticed that the problem isn't that the .ICEauthority-* files are still there, it is because it claims it can't lock the files. This is why I suggested a while back that whenever a filesystem re; /archives/xfs/2001-09/msg00560.html (9,744 bytes)
10. Re: lock files after crash (score: 1): Author: Jim Crilly <noth@xxxxxxxxxxxxxxxx>; Date: 24 Sep 2001 08:20:10 -0400; Most programs just use regular files, (like file.lock) to determine if a lock is held or not because the Linux kernel doesn't enforce mandatory locking by default, and you have to jump some hoops to; /archives/xfs/2001-09/msg00561.html (9,833 bytes)
11. lock files after crash (score: 1): Author: >; Date: Wed, 12 Sep 2001 01:00:27 -0600; I have an SMP system set to boot to X11/runlevel 5 that is RH 7.1 based (root is XFS). I had a crash at the moment I attempted to start login as a regular user (home is also XFS). It seems that ~/.IC; /archives/xfs/2001-09/msg00941.html (8,388 bytes)
12. Re: lock files after crash (score: 1): Author: >; Date: Wed, 12 Sep 2001 09:13:06 +0200; At 01:00 12-9-2001 -0600, D. Stimits wrote: I have an SMP system set to boot to X11/runlevel 5 that is RH 7.1 based (root is XFS). I had a crash at the moment I attempted to start login as a regular; /archives/xfs/2001-09/msg00942.html (9,196 bytes)
13. Re: lock files after crash (score: 1): Author: >; Date: Wed, 12 Sep 2001 02:21:59 -0600; In this case the file is .ICEauthority, not related to Netscape. What I am thinking about is fcntl(). I'm wondering about how these are implemented: F_GETLK, F_SETLK and F_SETLKW. If fcntl locks depe; /archives/xfs/2001-09/msg00943.html (10,653 bytes)
14. Re: lock files after crash (score: 1): Author: >; Date: Wed, 12 Sep 2001 18:04:46 +0200; from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 51F4C57306; Wed, 12 Sep 2001 18:04:47 +0200 (CEST) Cc: "XFS: linux-xfs@xxxxxxxxxxx" <linux-xfs@xxxxxxx; /archives/xfs/2001-09/msg00948.html (11,895 bytes)
15. Re: lock files after crash (score: 1): Author: >; Date: Wed, 12 Sep 2001 15:18:32 -0600; Since nobody has said anything, let me rephrase the question. There are custom lock file schemes, which I am not interested in. There *is* fcntl to perform locking. Ignoring lock files, is there any; /archives/xfs/2001-09/msg00955.html (9,474 bytes)
16. Re: lock files after crash (score: 1): Author: >; Date: Wed, 12 Sep 2001 17:30:16 -0500; I did respond - twice, but I am operating on a temporary workstation here due to a head crash and my mail setup appears not to be all it could be. In my second response, I looked more closely at the; /archives/xfs/2001-09/msg00958.html (10,912 bytes)
17. Re: lock files after crash (score: 1): Author: >; Date: Wed, 12 Sep 2001 17:49:57 -0600; Is it safe then to say that "...mode word of the inode that mandatory locking should be used..." does not actually get preserved in the metadata? It could be apples and oranges comparison, that manda; /archives/xfs/2001-09/msg00959.html (11,920 bytes)
18. Re: lock files after crash (score: 1): Author: >; Date: Fri, 21 Sep 2001 22:25:20 +0200; i observed something similar too - the reason why logging in is not really possible is the existence of some .ICEauthority-* files - simply removing them should fix the problem - so there is no magic; /archives/xfs/2001-09/msg01236.html (9,595 bytes)
19. Re: lock files after crash (score: 1): Author: >; Date: Mon, 24 Sep 2001 01:27:13 -0600; I've noticed that the problem isn't that the .ICEauthority-* files are still there, it is because it claims it can't lock the files. This is why I suggested a while back that whenever a filesystem re; /archives/xfs/2001-09/msg01238.html (9,744 bytes)
20. Re: lock files after crash (score: 1): Author: >; Date: 24 Sep 2001 08:20:10 -0400; Most programs just use regular files, (like file.lock) to determine if a lock is held or not because the Linux kernel doesn't enforce mandatory locking by default, and you have to jump some hoops to; /archives/xfs/2001-09/msg01239.html (9,833 bytes)

Current List: 1 - 20
Page: [1]