Ticket #517 (closed defect: upstream)

Opened 4 years ago

Last modified 4 years ago

opkg lock file in wrong place

Reported by: rtp Owned by: ainulindale
Priority: trivial Milestone:
Component: SHR Image Version:
Keywords: Cc:

Description

When strace opkg, found that:
creat("/usr/lib/opkg/lock", 0640)

This means that opkg creates its lock in /usr/lib/opkg.
FHS is asking that this file should be put in /var/lock.
This is also important as /var/lock is in tmpfs and not /usr/lib/. Using the right place will avoid some r/w on the flash for a temporary file.

Change History

comment:1 Changed 4 years ago by dos

  • Status changed from new to closed
  • Version SHR-unstable deleted
  • Resolution set to upstream

Well, it rather looks like upstream issue, doesn't it?

Please fill ticket on Openmoko trac.

comment:2 Changed 4 years ago by spaetz

  • Priority changed from major to trivial

FYI: I aggree this is an upstream issue that we cannot do a lot about (besides starting to patch this in substantial ways). I have asked this on the opkg mailing list bug haven't gotten an answer yet. I recommend to file this issue as ticket at code.google.com in the opkg project.

Note: See TracTickets for help on using tickets.