![]() I just thought it was the easiest way from within a. I don’t mandatory need a view on a terminal while it’s doing the backup. ⋅ tells me it’s ok and done or not ok there has been a problem. I did not try yet as I’m not comfortable with script.Īt the end I just want a « launcher » stored on the HDD, which : I’m afraid it will behave the same after the pause. ⋅ to open that file once the backup is done ⋅ to name that file as « sauv_DATA_date_time » and save it at root of the backup destination ⋅ instruction to print the output from that command in a file instead of terminal itself, So maybe the strategy is writing a more elaborate script which would contain : If I set « hold terminal opened » after a command is done in Tilix preferences, I get an header message « child process stopped normally with signal ×× » offering to relaunch but that fails again hence that terminal remains unusable. It just closes, preventing the ability to check what happened. What I can’t manage so far with « x-terminal-emulator » is keeping Tilix’s window opened once the command is done. Launches Tilix with the expected command so it seems Tilix is associated one way or another as the « default » system terminal on UBudgie. ![]() In the other hand, x-terminal-emulator -e "sudo rsync -va -delete-after /media/DATA/ /media/django/SAUV_2020/DATA/" ![]() I don’t understand how having a symlink named nxterm may launch the symlinked tilix when xterm is called ? What’s the rationale behind ? ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |