On Sat, May 7, 2016, at 02:43 PM, Christian Seiler wrote:
>
> No, it does catch the signal without a problem. But start-stop-daemon
> closes the standard filedescriptors and replaces them with /dev/null.
>
> Try it:
>
> /tmp/t.sh start
> ps ax | grep a.out
> lsof -p
On 05/07/2016 06:39 AM, CN wrote:
> The following compilable C++ program catches signals as expected if it
> runs directly from shell /tmp/a.out.
>
> However, this program fails to catch any signal and silently terminates
> if it is fired by Debian's start-stop-daemon.
N
The following compilable C++ program catches signals as expected if it
runs directly from shell /tmp/a.out.
However, this program fails to catch any signal and silently terminates
if it is fired by Debian's start-stop-daemon. (My real life multiple
threaded program does not silently termi
permission to search directories, or to execute files if
> anyone could execute them before.
>
That I did not know, indeed. Thanks for that.
>> echo "At ${time} on ${date}, file $FILECHANGE was chmodded" >> "$1"
>> done
>> #+end_src
>
d execute permission.
For example, this mode:
a+X
gives all users permission to search directories, or to execute files if
anyone could execute them before.
> echo "At ${time} on ${date}, file $FILECHANGE was chmodded" >> "$1"
> done
> #+en
Andreas Leha writes:
> Hi all,
>
>
> (cross-post from here:
> http://superuser.com/questions/571416/start-stop-daemon-on-an-inotify-scripti)
>
>
>
> I am on debian squeeze.
>
> Consider this stripped down script (placed at
> /usr/local/bin/testinotify) ar
Hi all,
(cross-post from here:
http://superuser.com/questions/571416/start-stop-daemon-on-an-inotify-scripti)
I am on debian squeeze.
Consider this stripped down script (placed at
/usr/local/bin/testinotify) around inotifywait:
#+begin_src sh
#!/bin/bash
WATCHDIR="/tmp/testin
data 32698 18092 0 05:36 ? 00:01:05 php-cgi -b 127.0.0.1:47990
- Stadtpirat
Von: Bob Proulx
An: debian-user@lists.debian.org
Gesendet: 21:33 Freitag, 11.Januar 2013
Betreff: Re: start-stop-daemon : questions about retry
- - wrote:
> unfortu
On Fri, Jan 11, 2013 at 3:33 PM, Bob Proulx wrote:
> - - wrote:
>>
>> # ps aux
>> USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND
>> www-data 1294 0.1 0.7 193960 44688 ?SJan09 1:07 php-cgi -b
>> 127.0.0.1:47990
>> root 1374 0.0 0.0 24712 764 ?
the process parent is 1 or not. 'ps -ef'
or 'ps -efH' shows this. I don't know the BSD ps option to show the
PPID.
> # cat /usr/local/var/run/cherokee.pid
> 1374
That matches fine.
> # start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile
> /
r/bin/rrdtool -
[…]
# cat /usr/local/var/run/cherokee.pid
1374
# start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile
/usr/local/var/run/cherokee.pid --name cherokee
#ps aux
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
www-data 1294 0.1 0.7 193960
On Sun, Jan 06, 2013 at 02:10:43AM -0800, - - wrote:
> Hello,
>
> I am trying to write an init script for cherokee webserver. Not, there is
> already one, but I wanted to have one derived from skeleton.
>
>
>
> In function "do_stop()" the script executes this
Hello,
I am trying to write an init script for cherokee webserver. Not, there is
already one, but I wanted to have one derived from skeleton.
In function "do_stop()" the script executes this line:
"start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE
--n
start-stop-daemon works as root, but not when sudo with qemu-nbd
my definition of works vs doesn't - i can connect to both (assuming a qcow2 vm):
start-stop-daemon --start -b --exec /usr/bin/qemu-nbd -- nocache template.qcow2
nbd-client localhost 1024 /dev/nbd0
fdisk -l /dev/nbd0 #WORKS
hvw59601 writes:
>This process is started at boot by 'do_chk_ip' in /etc/init.d which has:
> stop)
> start-stop-daemon --stop --verbose --exec $DAEMON
> ;;
>where $DAEMON=/usr/bin/do_tail_chk which has:
>tail -s 1 -n 60 -f /var/log/syslog | /usr/bin/d
On Tue, 10 Jan 2012 13:52:21 -0600, hvw59601 wrote:
> hvw59601 wrote:
>> Camaleón wrote:
>>> On Tue, 10 Jan 2012 11:02:13 -0600, hvw59601 wrote:
>>>
There are 2 systems behind a Thomson TG585V8 router connected to the
internet.
Currently about once every halfhour the 'internet'
hvw59601 wrote:
Camaleón wrote:
On Tue, 10 Jan 2012 11:02:13 -0600, hvw59601 wrote:
There are 2 systems behind a Thomson TG585V8 router connected to the
internet.
Currently about once every halfhour the 'internet' LED on the router
goes out (no internet connection) then goes red (internet con
Camaleón wrote:
On Tue, 10 Jan 2012 11:02:13 -0600, hvw59601 wrote:
There are 2 systems behind a Thomson TG585V8 router connected to the
internet.
Currently about once every halfhour the 'internet' LED on the router
goes out (no internet connection) then goes red (internet connection
failed) a
On Tue, 10 Jan 2012 11:02:13 -0600, hvw59601 wrote:
> There are 2 systems behind a Thomson TG585V8 router connected to the
> internet.
>
> Currently about once every halfhour the 'internet' LED on the router
> goes out (no internet connection) then goes red (internet connection
> failed) and goes
Tue Jan 10 10:14:57 2012 187.136.116.91 (226)
I wrote a program 'do_chk_ip' which is piped the tail of syslog and
looks for the appropriate ddclient message and then records the date and
time to a database.
This process is started at boot by 'do_chk_ip' in /etc/init.d whic
On 11 Lip, 09:30, Sven Joachim <[EMAIL PROTECTED]> wrote:
> Hello supermega,
>
> do you also have a real name?
>
> On 2008-07-11 03:59 +0200, supermega wrote:
>
> > I'd like to use start-stop-daemon with chroot option, but I get a
> > strange error. A test:
Hello supermega,
do you also have a real name?
On 2008-07-11 03:59 +0200, supermega wrote:
> I'd like to use start-stop-daemon with chroot option, but I get a
> strange error. A test:
> # start-stop-daemon --start --chroot /bin --exec ls
> start-stop-daemon: Unable to start ls
Hi,
I'd like to use start-stop-daemon with chroot option, but I get a
strange error. A test:
# start-stop-daemon --start --chroot /bin --exec ls
start-stop-daemon: Unable to start ls: No such file or directory (No
such file or directory)
I should work, shouldn't it?
When I run this:
#
I want to use LD_PRELOAD so that a program can use some code that
substitutes for the usual system calls. The program, bacula-fd, is
started by an init script that uses start-stop-daemon.
Is there a way to get this to work?
I've seen some prior discussion of this issue on this list, bu
man start-stop-daemon: "Any arguments given after -- on the command line
are passed unmodified to the program being started."
I mean the environment variables that will be recognized by the invoked
daemon. I have solved this by adding NAME=xxx pairs preceding
start-stop-daemon:
Hi,
On Fri, 13 Jul 2007 06:20:09 +0200 Dallas Clement wrote:
> On Fri, 2007-07-13 at 11:13 +0800, Yuwen Dai wrote:
>>
>> A daemon invoked by start-stop-daemon needs some extra enviroment
>> variables. How to pass them to the daemon? Thanks in advance.
>
>
Yuwen Dai wrote:
> A daemon invoked by start-stop-daemon needs some extra enviroment
> variables. How to pass them to the daemon? Thanks in advance.
Typically in Debian start-stop-daemon is called from within the boot
time /etc/init.d/* scripts. Typically those scripts will
On Fri, 2007-07-13 at 11:13 +0800, Yuwen Dai wrote:
> Dear all,
>
> A daemon invoked by start-stop-daemon needs some extra enviroment
> variables. How to pass them to the daemon? Thanks in advance.
>
> Best regards,
> Yuwen
I'm not sure if you meant environment
Dear all,
A daemon invoked by start-stop-daemon needs some extra enviroment
variables. How to pass them to the daemon? Thanks in advance.
Best regards,
Yuwen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Is there any chance to find out in which package the start-stop-daemon
> is w/o reinstalling the whole debian distribution and hopeing that it
> will be installed automatically?
I really like the program apt-file. It allows you to search a
On Friday 22 June 2007 13:41, Dirk wrote:
> Is there any chance to find out in which package the start-stop-daemon
> is w/o reinstalling the whole debian distribution and hopeing that it
> will be installed automatically?
In my Etch system, start-stop-daemon comes from the dpkg package
any chance to find out in which package the start-stop-daemon
is w/o reinstalling the whole debian distribution and hopeing that it
will be installed automatically?
Dirk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Mon, Feb 19, 2007 at 09:07:36AM -0800, Brad Brock wrote:
> I want to set my program as daemon that started when
> system start. I have read the manual of
> start-stop-daemon but I think an example would be
> great for me. Does anyone has the example? Thank you.
/etc/init.d/ is full
2007/2/19, Brad Brock <[EMAIL PROTECTED]>:
I want to set my program as daemon that started when
system start. I have read the manual of
start-stop-daemon but I think an example would be
great for me. Does anyone has the example? Thank you.
Hi,
which program ? Have you made it yo
I want to set my program as daemon that started when
system start. I have read the manual of
start-stop-daemon but I think an example would be
great for me. Does anyone has the example? Thank you.
No need to
Under etch I'm using start-stop-daemon to start the swatch log
monitoring utility in an /etc/init.d script. This is working, but
each instance of swatch (I'm starting multiple -- one instance per
monitored log) creates a zombie process the first time it logs
something. I'm usi
On Mon, Dec 12, 2005 at 05:22:27PM +0200, Maxim Vexler wrote:
> On 12/12/05, Andrew Cady <[EMAIL PROTECTED]> wrote:
> [snip]
>
> > You could try putting a sulogin immediately before the mythbackend
> > script in your runlevel then running mythbackend manually. If it
> > works you've ruled out orde
On Mon, Dec 12, 2005 at 03:32:57PM -0700, Mike wrote:
>
> normally you just have a set of source functions library like
> /etc/init.d/functions or some other path that you use for your init
> scripts. Debian has decided to daomonize it with this start-stop-daemon
> thing they mad
ions? Huh?
normally you just have a set of source functions library like
/etc/init.d/functions or some other path that you use
for your init scripts. Debian has decided to daomonize it with this
start-stop-daemon thing they made up. I guess I
could create my own functions file and go through all of th
On 12/12/05, Andrew Cady <[EMAIL PROTECTED]> wrote:
[snip]
>
> You could try putting a sulogin immediately before the mythbackend
> script in your runlevel then running mythbackend manually. If it works
> you've ruled out ordering and should check for environment problems by
> stopping mythbackend
On Mon, Dec 12, 2005 at 01:11:44AM -0700, Mike wrote:
> I'm baffled I can start this by running
> "/etc/init.d/mythbackend start" after the computer starts but when
> its starting up it just says its starting but never does.
>
> How on earth would I trouble shoot something like this if it is
r/log/mythtv/mythbackend.log --pidfile
> $RUNDIR/$NAME.pid"
> EXTRA_ARGS=""
> NICE=0
>
> if [ -f /etc/default/mythbackend ]; then
> . /etc/default/mythbackend
> fi
>
> ARGS="$ARGS $EXTRA_ARGS"
>
> mkdir -p $RUNDIR
> chown -R $USER $R
run/mythtv
ARGS="--daemon --logfile /var/log/mythtv/mythbackend.log --pidfile
$RUNDIR/$NAME.pid"
EXTRA_ARGS=""
NICE=0
if [ -f /etc/default/mythbackend ]; then
. /etc/default/mythbackend
fi
ARGS="$ARGS $EXTRA_ARGS"
mkdir -p $RUNDIR
chown -R $USER $RUNDIR
cas
From: Almut Behrens [mailto:[EMAIL PROTECTED]
Sent: Saturday, December 10, 2005 10:01 AM
To: debian-user@lists.debian.org
Subject: Re: start-stop-daemon and java
On Fri, Dec 09, 2005 at 10:26:46PM -0800, Scott Muir wrote:
> Have a question which i think relates to s-s-d more than java but
PPUSER="jsync"
> ARGS="-Xmx256M -jar jsyncmanager.jar --server"
> PIDFILE="/var/run/jsyncmanager.pid"
>
> # Carry out specific functions when asked to by the system
> case "$1" in
> start)
> echo "Starting jsyncmanager"
> start-st
/jsyncmanager.pid"
# Carry out specific functions when asked to by the system
case "$1" in
start)
echo "Starting jsyncmanager"
start-stop-daemon -Sbm -p $PIDFILE -c $APPUSER -d $APPDIR -x
"/usr/bin/java" -- $ARGS
this was derived from a comman
I use an init script which starts and stops the boinc client using the
start-stop-daemon.
[...]
start)
echo -n "Starting $DESC: $NAME"
start-stop-daemon --start --exec $DAEMON --chuid mike --chdir
/home/mike/boinc --pidfile $PIDFILE --make-pidfile --background
echo "."
>From S. Keeling
> (0) keeling /home/keeling_ which start-stop-daemon
> /sbin/start-stop-daemon
>cron runs with a minimal environment and likely doesn't have /sbin in
>its PATH.
That fixed it thanks,
Marion
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a sub
Incoming from Marion Hall:
> I'm trying to stop a wget process after a set amount of time with the
> following command from a crontab.
>
> start-stop-daemon --stop -n wget
>
> When this command runs, I get the following error and it doesn't stop wget:
> /bin/sh:
I'm trying to stop a wget process after a set amount of time with the
following command from a crontab.
start-stop-daemon --stop -n wget
When this command runs, I get the following error and it doesn't stop wget:
/bin/sh: start-stop-daemon: command not found
The wget command that is
might have been a permission problem.
|
| At this point I still don't have jabber starting and I'm not sure where to
| look now. Any help appreciated.
I had this problem for quite a while. The first cause is that jabber
doesn't daemonize on its own. So an option to start-st
and I'm not sure
> > where to look now. Any help appreciated.
>
> Change the first line of the init script from:
Thanks... however during my mucking about got it working again by taking
out the -c opiton for start-stop-daemon. It was -c daemon.
So I think it might be a permission p
On Wed, Mar 19, 2003 at 01:04:09PM +1100, Peter Lavender wrote:
> I installed jabberd from .deb. However jabber won't start from the
> start stop script /etc/init.d/jabber
Which version of the package?
> I can however start jabber from the commandline as root. Since I
> could do this I though
Peter Lavender said:
> Hi Everyone,
>
> I installed jabberd from .deb. However jabber won't start from the start
> stop script /etc/init.d/jabber
>
> I can however start jabber from the commandline as root. Since I could do
> this I thought it might have been a permission problem.
>
>
> At this p
Hi Everyone,
I installed jabberd from .deb. However jabber won't start from the start
stop script /etc/init.d/jabber
I can however start jabber from the commandline as root. Since I could do
this I thought it might have been a permission problem.
At this point I still don't have jabber starti
I've installed cipe-common_1.5.4free-1. The init.d script is supposed
to loop through the peer option files and invoke start-stop-daemon for
each one:
start_all () {
for peer in $PEERS
do
echo -n "$peer "
start-stop
Rob Weir wrote:
> On Thu, Dec 05, 2002 at 08:58:27PM -0600, ZephyrQ wrote:
> > Thank you, the moving the .REAL command fixed it. I was able to
> > configure my printer
>
> Do take up Joey's kind offer of help though, since it sounds like your
> installation screwed up pretty severly...
H
On Thu, Dec 05, 2002 at 08:58:27PM -0600, ZephyrQ wrote:
> Thank you, the moving the .REAL command fixed it. I was able to
> configure my printer
Do take up Joey's kind offer of help though, since it sounds like your
installation screwed up pretty severly...
> Now I have to start
:
> ZephyrQ wrote:
> > >I try to run that command, but get an error:
> > >
> > > Warning: Fake start-stop-daemon called, doing nothing
>
> It sounds to me like you got a debian system installed that has the fake
> start-stop-daemon command used by debootstra
ZephyrQ wrote:
> >I try to run that command, but get an error:
> >
> > Warning: Fake start-stop-daemon called, doing nothing
It sounds to me like you got a debian system installed that has the fake
start-stop-daemon command used by debootstrap when bootstrapping the
system. T
rror:
> >
> > Warning: Fake start-stop-daemon called, doing nothing
>
> I cannot get my printer set up...I keep getting this error.
>
> Every time I shutdown (init 0 *or* shutdown -h now) I get a screen
> full--and I have to shut off the system which, o
I've just installed Debian this past weekend, but I seem to have quite
a few problems getting things to run right. The common thread seems to
be the following:
>I try to run that command, but get an error:
>
> Warning: Fake start-stop-daemon called, doing nothing
Hi!
I would like to run few instances of same program but
with different parameters with start-stop-daemon
tool.
I have tryed:
start-stop-daemon --start --chuid nobody:nogroup
--pidfile /var/run/someprogram.pid --startas
/bin/someprogram
...
(other lines have other pidfile and some parameters
On Sat, Mar 09, 2002 at 07:27:09PM +0100, Ralf G. R. Bergs wrote:
> You might need some shared libraries (that the daemon binary itself depends
> upon) that are missing in the chroot jail.
Since spamd is a perl script, it's most likely missing a perl
interpreter in the chroot jail.
Chris Hilts
On Sat, 09 Mar 2002 12:08:54 -0600, Corey Halpin wrote:
[...]
>Yes, there is a spamd in /usr/sbin, and there is also one in
>/var/lib/spamd/usr/sbin.
You might need some shared libraries (that the daemon binary itself depends
upon) that are missing in the chroot jail.
"ldd -v " should show you
I'm attempting to chroot my spamd process to run from /var/lib/spamd.
I have copied all the relevant files from /etc, and from /usr/sbin to
/var/lib/spamd.
I then edit /etc/init.d/spamassassin and add --chroot /var/lib/spamd after
every start-stop-daemon invocation.
when I ru
On Tue, 12 Feb 2002 02:54:53 +0100, Karsten Heymann <[EMAIL PROTECTED]> wrote:
> Hi list,
>
> somehow I'm lost with start-stop-daemon and quoting. I'm trying to let
> a self-recompiled slapd server both ldap and ldaps. When invoked from
> the command line wi
Hi list,
somehow I'm lost with start-stop-daemon and quoting. I'm trying to let
a self-recompiled slapd server both ldap and ldaps. When invoked from
the command line with
slapd -d 255 -h "ldap:/// ldaps:///"
the debug output shows that both options are accepted. B
p you start, stop, restart, and reload daemons (some of these
> scripts use start-stop-daemon :)
Yes.
If X started with startx, kill it by menu or CTRL-ALT-BS. Restart X with
"exec startx".
If X is started by {x,g,k}gm type daemon, run corresponding /etc/init.d
script with "restart&
On Mon, Apr 30, 2001 at 04:58:02PM -0500, DvB wrote:
> Just how effective is the start-stop-daemon anyway? For instance, can I
> upgrade my kernel (assuming I use a prepackaged version or package my
> own with make-kpkg) or X server and not reboot?
>
> This service only works for
D> Just how effective is the start-stop-daemon anyway? For instance, can
D> I upgrade my kernel (assuming I use a prepackaged version or package
D> my own with make-kpkg) or X server and not reboot?
D> This service only works for daemons, right? (i.e. lpd, httpd, etc).
On Linux sy
On Mon, Apr 30, 2001 at 04:58:02PM -0500, DvB wrote:
> Just how effective is the start-stop-daemon anyway? For instance, can I
> upgrade my kernel (assuming I use a prepackaged version or package my
> own with make-kpkg) or X server and not reboot?
>
> This service only works for
Just how effective is the start-stop-daemon anyway? For instance, can I
upgrade my kernel (assuming I use a prepackaged version or package my
own with make-kpkg) or X server and not reboot?
This service only works for daemons, right? (i.e. lpd, httpd, etc).
Aaron Brashears wrote: >My /etc/init.d/posgresql uses start-stop-daemon to
launch
>/usr/lib/postgresql/bin/postgresql-startup which handles a lot of the
>details of running postgresql.
postgresql-startup was specially written for the Debian package of
PostgreSQL
--
Olive
;
> I've got it mostly working, using start-stop-daemon; the command is:
>
> start-stop-daemon --start --exec --chuid postgres
My /etc/init.d/posgresql uses start-stop-daemon to launch
/usr/lib/postgresql/bin/postgresql-startup which handles a lot of the
details of running po
Greetings.
Running a locally-compiled postgresql 7.0.3, I'm still trying to get it
to start up automatically at boot time. The trick is, of course, to get
it to start as user postgres instead of root.
I've got it mostly working, using start-stop-daemon; the command is:
start-stop-daem
[207.8.152.167]
Nov 27 17:18:04 spoke qmail: 975305884.684175 tcpserver: warning: dropping
connection, unable to run /usr/sbin/rblsmptd: file does not exist
If I run the startup command without start-stop-daemon it works fine. It
is only with the wrapper that I have this porblem. The startup command is
as
On Thu, 30 Dec 1999, Shaul Karl wrote:
: 1) I just installed inn and I am getting
:
: start-stop-daemon: command not found
:
: whenever I am starting or stopping it.
:
: Did I missed something or is it a bug?
Make sure you're starting or stopping as the root user (use su or
1) I just installed inn and I am getting
start-stop-daemon: command not found
whenever I am starting or stopping it.
Did I missed something or is it a bug?
2) Although getlist(1) manages to get about 45000 groups, actsync(8) is
hanging up and I have to kill it. It seems to put in the
changes to let it happen w/o
a password. I'm going to get an error here that it can't find
"start-stop-daemon". Alternatively, if I change the "daemon" script to
point to /sbin/start-stop-daemon then it works fine. I tried this with
/etc/init.d/bind
Is there any way t
[EMAIL PROTECTED] (Marc Haber) writes:
> I am running exim as two daemons. One is listening on port 25, the
> other does periodic queue runs only when I am online. The queue runner
> exim is killed off when I go offline.
[snip]
> How can I make start-stop-daemon check for a proces
-f $DAEMON || exit 0
|
|set -e
|
|case "$1" in
| start)
|echo -n "Starting $DESC: "
|start-stop-daemon --start --quiet \
|--pidfile /var/run/$NAME.$PORT.pid-$PARM \
|--exec $DAEMON -- -$PARM -oX $PORT
|echo "$DESC."
|
I wrote:
> I just upgraded my Debian 1.2 to Debian 1.3, and am having a problem
> with the scripts that are supposed to start kerneld.
>
> The script /etc/init.d/kerneld doesn't start kerneld (when it is run
> automatically boot time).
>
...
> So, have I misinstalled 1.3, or ...
I wrote:
> > From: Frank Barknecht <[EMAIL PROTECTED]>
>
> > After upgrading to Debian 1.3.1 I encountered a serious start-up-problem.
> > Some of the /etc/init.d/-scripts fail with messages like
> > >-
> > /etc/init.d/kerneld: /u
> From: Frank Barknecht <[EMAIL PROTECTED]>
> After upgrading to Debian 1.3.1 I encountered a serious start-up-problem.
> Some of the /etc/init.d/-scripts fail with messages like
> >-
> /etc/init.d/kerneld: /usr/sbin/start-stop-daemon: N
a bug report or is this problem obsolete anyway
> with the new start-stop-daemon in C?
Well, it's a problem other people might encounter when upgrading. I'm not
sure if we have a document on upgrading from previous releases; if we do,
this should go in there.
On Aug 6, Frank Barknecht
> Yes, that's it. I linked perl500... with /usr/bin/perl
> right now and I am about to reboot to see if it works.
IT WORKS.
--
Yours,
Frank Barknecht
r the quick help. That's really great about Debian,
wow.
P.S.:
Is this all worth a bug report or is this problem
obsolete anyway with the new start-stop-daemon in C?
--
Yours,
Frank Barknecht
<<<&
Frank Barknecht hat gesagt: // Frank Barknecht wrote: ([EMAIL PROTECTED]):
> My start-stop-daemon is a perl-script, I can read its content.
Now I have found another strange thing: I don't have an executable named perl
on my system
anymore. Although there is a perl5.00307 under
[Frank, please keep your lines shorter than 80 characters.]
On Aug 6, Frank Barknecht wrote
> [EMAIL PROTECTED] hat gesagt: // [EMAIL PROTECTED] wrote:
> ([EMAIL PROTECTED]):
> > Very strange. Please provide the output of
> > ls -l /sbin/start-stop-daemon /usr/sbi
Frank Barknecht <[EMAIL PROTECTED]> writes:
> Conclusion:
> I don't have start-stop-daemon under /sbin but one in /usr/sbin/ that is not
> a.out or ELF.
> My start-stop-daemon is a perl-script, I can read its content.
That's how it was under older versions of Debia
[EMAIL PROTECTED] hat gesagt: // [EMAIL PROTECTED] wrote: ([EMAIL PROTECTED]):
> Very strange. Please provide the output of
> ls -l /sbin/start-stop-daemon /usr/sbin/start-stopdaemon
Here we go:
fliwatut# ls -l /sbin/start-stop-daemon /usr/sbin/start-stopdaemon
ls: /sbin
On Aug 6, Frank Barknecht wrote
> After upgrading to Debian 1.3.1 I encountered a serious start-up-problem.
> Some of the /etc/init.d/-scripts fail with messages like
> >-
> /etc/init.d/kerneld: /usr/sbin/start-stop-daemon: No such file or directory
> >---
After upgrading to Debian 1.3.1 I encountered a serious start-up-problem.
Some of the /etc/init.d/-scripts fail with messages like
>-
/etc/init.d/kerneld: /usr/sbin/start-stop-daemon: No such file or directory
>-
Same with sendmail, xdm etc.
If I try the command
Running a machine with the frozen version of debian:
etc/init.d/xdm: Command not found.
host:/etc/init.d# /etc/init.d/xdm stop
no /usr/bin/X11/xdm found; none killed.
host:/etc/init.d# start-stop-daemon --stop --exec /usr/bin/X11/xdm
no /usr/bin/X11/xdm found; none killed.
host:/etc/init.d# ps
I would like to be able to use the standard Debian start-up scripts for my
custom router bootdisk. (And it appears so would alot of other people)
Unfortunately start-stop-daemon requires perl.
All together perl and libs are about 500K (about 200K compressed)..a
HUGH waste on a floppy.
Is
erl.
>
> > bash: /usr/sbin/start-stop-daemon: No such file or directory.
> >
> > This is odd since it's finding the correct program and the path for it but
> > is saying it can't find it. Spook! I've looksed in /usr/sbin and
> > start-stop-daemon
[EMAIL PROTECTED] (Brian Skreeg) writes:
> Due to the ridiuclous dependancies involving Perl,io,libnet and
> dpkg-ftp I now find dpkg-ftp broken.
io was merged into perl and is now obsolete. Remove io and reinstall
perl.
> bash: /usr/sbin/start-stop-daemon: No such file or
rough, Ontario fax: (416)431-2617
Canada M1J-2L7
On Fri, 7 Mar 1997, Brian Skreeg wrote:
> Date: Fri, 7 Mar 97 15:44:17 GMT
> From: Brian Skreeg <[EMAIL PROTECTED]>
> To: debian-user@lists.debian.org
> Subject: Perl/io/dpkg-ftp and start-stop-dae
>When I do 'dpkg --status perl' and 'dpkg --status perl-base' it prints out
the
>corresponding lines:
>Package: perl
>Status: install ok installed
>[cut]
>Package: perl-base
>Status: purge ok not-installed
>[cut]
Yep that's what I get. It's "perl" I have installed and not "perl-base" . I
can't
1 - 100 of 105 matches
Mail list logo
