Opened 12 years ago
Closed 12 years ago
#9705 closed enhancement (duplicate)
Replicants added using desklink aren't "resistant"
| Reported by: | Giova84 | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | Applications/Command Line Tools | Version: | R1/Development |
| Keywords: | Replicants added using desklink aren't resistant | Cc: | |
| Blocked By: | #5367 | Blocking: | |
| Platform: | x86 |
Description
If we add a replicant in the Deskbar using the command "desklink", if/when the Deskbar will crash, this replicant will be lost. Instead, if in the Deskbar we add a replicant like ProcessController or NetworkStatus, these replicants, will be restored after crash. Would be nice improve user's replicants added via "desklink", to have them restored after a Deskbar crash.
Steps to reproduce: 1: open a Terminal windows and type: desklink /boot/home/queries (this will add the "queries" folder to Deskbar
2: do a CTRL+ALT+CANC to open Team Monitor and here kill the Deskbar
3: restart the Deskbar (clicking on "Restart the desktop") and you will see that the replicant added using "desklink" is not restored. Instead, if in your Deskbar you will add ProcessController or NetworkStatus, these replicants will be restored when you will restart the Deskbar.
Change History (2)
comment:1 by , 12 years ago
| Component: | Applications/Deskbar → Applications/Command Line Tools |
|---|---|
| Owner: | changed from to |
comment:2 by , 12 years ago
| Blocked By: | 5367 added |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
That's entirely up to desklink, there are two different ways to add a deskbar replicant, one of which is persistent, the other is not.