On 01/26/2011 08:24 PM, Denys Vlasenko wrote:
After a quick look at abrt-cli source, I think this can be approached
We add -D DIR option which specifies which directory to list.
It can be used more than once. If it is not specified,
abrt-cli defaults to -D /var/spool/abrt -D $HOME/abrt/spool.
With "abrt-cli --list", dumps from all these directories
- what are you going to show here? the list of paths or some summary
about every dump? if the first one, then user will have hard time
guessing which is the dump he wants to process and if the second then
you'll hit the locking problem again.. unless you ask the daemon to give
you the data...
When "abrt-cli --report DUMP_DIR" is run and abrt-cli
that it can't lock DUMP_DIR for writing, it informs the user:
DUMP_DIR is not writable.
Do you want to copy it to $HOME/abrt/spool? (y/n)
(The directory to copy to can be specified by another option,
-W DIR; or we can have a convention that the DIR from the
first -D DIR option is used)
- this sounds ok
When "abrt-cli --delete DUMP_DIR" is run and abrt-cli
that it can't lock DUMP_DIR for writing, it tries to delete
the directory through dbus call to abrtd.
- I'm ok with this, but at one point we will have to make the surgery
and cut the dbus from daemon (or we can leave it if we can live with the