> > note : I think, you will have this trouble on a lot of
> > distribution. you have importas program which do the same thing as
> > import program, so perhaps you can remove the import program?!?
>
> Oh really? How about you write to the ImageMagick maintainers and
> suggest *them* to remove
On 13/06/2016 16:50, Eric Vidal wrote:
I totaly agree with you but i do not have the choice, you import
program is in conflict with import from imagemagick. So, under
Archlinux system (i'm based on it) the bin directory is a symlinks to
/usr/bin.
You totally have the choice. Install it with
> > > However, i have a another trouble, when i try to launch some classic
> > > service with the second scandir(or the first, it's equal) i have this
> > > error on the log : @4000575cf0bb05fd2e24 s6-supervise
> > > syslogd-linux/log: warning: unable to spawn ./run - waiting 10
> > > seconds
#!/usr/local/bin/execlineb -P
If you're a distributor: don't do that. Distributions should not install
anything in /usr/local.
Also, if you're providing s6 as the base init system, you should have the
execline binaries in the root filesystem, which means /bin. Because the user
may choose to
Hello, i'm trying to test to use multiple scandir and multiple rc database.
So i have a one scandir started at the end of init file then i have a second
started by a longrun service on stage 2 like this :
#!/usr/local/bin/execlineb -P
fdmove -c 2 1
if { s6-echo -- start switch-svscan