Okay i am not really into writing shell-scripts, actually it was one of my first…So i do not think that there is much understand from your side, maybe I put an something in which just a mistake … ;). I first created the shell script without exec=… at the begining but it did not work…So i thouhgt I maybe have to tell him to execute the programm out of the user binarys…
I quite bad in scripting ;) But I did think that this would ruin my system that much…
Should make a repair with the opensuse dvd?
Best – Benjamin
Gesendet: Mittwoch, 23. April 2014 um 12:52 Uhr
Von: "Carlos E. R."
On Wed, 23 Apr 2014 11:51:32 +0200 Benjamin Draxlbauer wrote:
Yes - they are just the profiles of unison, that the program knows which folders to sync...
I'll attempt to explain further: You injected a custom script into the boot process and it has apparently damaged your system. No one here can guess the locations or kinds of damage without knowing, first, the exact commands and arguments that were executed.
cer@Telcontar:~/bin> cat pp #!/bin/sh exec=/usr/bin/unison myprofile -batch cer@Telcontar:~/bin> pp /home/cer/bin/pp: line 3: myprofile: command not found cer@Telcontar:~/bin> Ie, it tries to run "myprofile", not as a parameter to unison. On the other hand, the documentation says: exec [-a NAME] [-cl] [COMMAND] [ARG...] [REDIRECTION...] http://wiki.bash-hackers.org/commands/builtin/exec or man bash: exec [-cl] [-a name] [command [arguments]] If command is specified, it replaces the shell. No new process is created. The arguments become the arguments to command. If the -l option is supplied, the shell places a dash at the beginning of the zeroth argument passed to command. This is what login(1) does. The -c option causes command to be executed with an empty environment. If -a is supplied, the shell passes name as the zeroth argument to the executed command. If command cannot be exe- cuted for some reason, a non-interactive shell exits, unless the shell option execfail is enabled, in which case it returns failure. An interactive shell returns failure if the file cannot be executed. If command is not speci- fied, any redirections take effect in the cur- rent shell, and the return status is 0. If there is a redirection error, the return status is 1. I do not see a reference for the "=" symbol. That would try to assign a variable named "exec", I understand. Or I'm misunderstanding it. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org