Project

General

Profile

Anomalie #1745

Bizarreries dans la gestion des lock bash

Added by Emmanuel GARETTE over 10 years ago. Updated over 7 years ago.

Status:
Classée sans suite
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Distribution:
EOLE 2.4

Description

1/ AddLock de FonctionEoleNg lance un script python (/usr/share/eole/eolelock.py) qui import creole/eolelock qui import pyeole/lock.
On pourrait se passer du script eolelock.py et importer directement pyeole/lock.

2/ La fonction lock test si le fichier lock a été correctement créé. Il ne test pas si le fichier existe déjà.

Le message d'erreur de FonctionEoleNg n'est donc pas correct :

EchoRouge "Le verrou (lock) \"/var/lock/$1\" existe déjà, abandon !"

Je ne vois aucun test permettant de savoir si le verrou pré-existe.

Associated revisions

Revision ece7e031 (diff)
Added by exarkun almost 15 years ago

Merge faster-preview-1745

Author: exarkun
Reviewer: jml
Fixes #1745
Refs #1211
Refs #1624

Change InboxScreen.fastForward to only return information about the message
being selected. Remove all of the code which previously supported also
retrieving preview information to return alongside that information, since
it was hopelessly slow and the client already has the information anyway.

History

#1 Updated by Joël Cuissinat over 10 years ago

  • Target version changed from EOLE 2.3 Stable to 76

#2 Updated by Emmanuel GARETTE about 9 years ago

  • Target version changed from 76 to Eole 2.4-dev-1
  • Distribution set to EOLE 2.4

#3 Updated by Joël Cuissinat almost 9 years ago

  • Target version changed from Eole 2.4-dev-1 to 189

#4 Updated by Joël Cuissinat over 7 years ago

  • Status changed from Nouveau to Classée sans suite
  • Target version deleted (189)
  • Start date deleted (05/02/2011)

La demande a été reportée pour EOLE 2.4 mais comme la gestion des locks a été recodée...

Also available in: Atom PDF