On Fri, 8 Jun 2018 14:21:02 -0400
Greg Wooledge wrote:
> On Fri, Jun 08, 2018 at 08:13:24PM +0200, Holger Nessen wrote:
> > I'am not sure which sound backend you are using.
> > As far as I can remember, ALSA didn't allow multiple processes to
> > output sound at the same time.
>
> Depends on th
On Fri, Jun 08, 2018 at 08:13:24PM +0200, Holger Nessen wrote:
> I'am not sure which sound backend you are using.
> As far as I can remember, ALSA didn't allow multiple processes to
> output sound at the same time.
Depends on the hardware. If the hardware allows mixing natively, then
you can get
ter the
upgrade.
Best Regards,
Holger
Am Fri, 8 Jun 2018 16:33:45 +0200 (CEST)
schrieb Roger Price :
> For nearly 20 years, I have had a cron job in which a dog (yes, it's
> Biff) barks the hours. The lines in /etc/crontab are
>
> 0 0,12 * * * rprice /mnt/home/rprice/b
On Fri, 8 Jun 2018 16:33:45 +0200 (CEST)
Roger Price wrote:
> For nearly 20 years, I have had a cron job in which a dog (yes, it's Biff)
> barks
> the hours. The lines in /etc/crontab are
>
> 0 0,12 * * * rprice /mnt/home/rprice/bark/bark.sh 12
> ...
>
For nearly 20 years, I have had a cron job in which a dog (yes, it's Biff) barks
the hours. The lines in /etc/crontab are
0 0,12 * * * rprice /mnt/home/rprice/bark/bark.sh 12
...
0 11,23 * * * rprice /mnt/home/rprice/bark/bark.sh 11
In the bark.sh script, the sound is pro
On 31 August 2017 at 04:32, James H. H. Lampert
wrote:
>
> I added a line to echo $SHELL to my debugging log file, and
> that was it: if I ran it from cron, $SHELL was /bin/sh; if I ran it from a
> command line, $SHELL was /bin/bash.
Be careful to correctly understand the purpose of the SHELL env
On 8/31/17, 5:16 AM, Reco wrote:
$ bash -c 'cd foo; echo $?'
bash: line 0: cd: foo: No such file or directory
1
To this:
$ dash -c 'cd foo; echo $?'
dash: 1: cd: can't cd to foo
2
Aha! That's what it was! Thanks!
At any rate, changing the test script's utterly nonspecific shebang
(that, I g
Hi.
On Thu, Aug 31, 2017 at 08:03:51AM -0400, Greg Wooledge wrote:
> On Thu, Aug 31, 2017 at 06:52:28AM +0100, Jonathan de Boyne Pollard wrote:
> > James H. H. Lampert:
> >
> > > Could it be that |cron| is running it an entirely different shell, that
> > > doesn't understand the |if| stat
On Thu, Aug 31, 2017 at 06:52:28AM +0100, Jonathan de Boyne Pollard wrote:
> James H. H. Lampert:
>
> > Could it be that |cron| is running it an entirely different shell, that
> > doesn't understand the |if| statement?
> >
> Despite what others have said, the answer to this question is no. Whils
James H. H. Lampert:
Could it be that |cron| is running it an entirely different shell,
that doesn't understand the |if| statement?
Despite what others have said, the answer to this question is no.
Whilst you /are/ running two different shells, the problem is not the
|if| statement. Both o
On Wed, Aug 30, 2017 at 09:32:37PM +0300, Reco wrote:
> > > #!
>
> A curious shebang.
> > Why would the behavior be any different? Could it be that cron is running it
> > an entirely different shell, that doesn't understand the "if" statement?
>
> Presumably your script runs via /bin/bash in int
On Wed 30 Aug 2017 at 11:07:36 (-0700), James H. H. Lampert wrote:
> Can somebody explain this:
>
> My backup script WILL detect that ExternalHD is not mounted, and
> attempt to mount it, if I run it manually.
>
> But it WON'T do that if it runs in a cron job.
>
&g
A few minutes ago, with respect to my backup script attempting to mount
ExternalHD if run from a command line, but not from cron, I wrote:
Why would the behavior be any different? Could it be that cron is
running it an entirely different shell, that doesn't understand the "if"
statement?
That w
Hi.
On Wed, Aug 30, 2017 at 11:07:36AM -0700, James H. H. Lampert wrote:
> Can somebody explain this:
>
> My backup script WILL detect that ExternalHD is not mounted, and attempt to
> mount it, if I run it manually.
>
> But it WON'T do that if it runs in a cron
Can somebody explain this:
My backup script WILL detect that ExternalHD is not mounted, and attempt
to mount it, if I run it manually.
But it WON'T do that if it runs in a cron job.
I've isolated the relevant code into its own script, added debugging
output, and set it up to
On Sun, May 06, 2012 at 11:24:44AM +, Camaleón wrote:
> On Sat, 05 May 2012 18:26:30 -0400, Tony Baldwin wrote:
>
> > I've got a little cron job,
> > just trying to fire off a script (see http://tonyb.us/mattbot ) and it's
> > not firing.
> >
> >
On Sun, May 06, 2012 at 02:07:08AM +0300, Adrian Fita wrote:
> On 06/05/12 01:26, Tony Baldwin wrote:
> > I've got a little cron job,
> > just trying to fire off a script (see http://tonyb.us/mattbot )
> > and it's not firing.
>
> [...]
>
> > Pro
=?iso-8859-1?q?Camale=F3n?= writes:
> Here is a good collection of the common reasons why a cron job does not
> engage:
>
> http://askubuntu.com/questions/23009/reasons-why-crontab-does-not-work
One thing you can do is to set an "at" job to run your
script once. G
On Sat, 05 May 2012 18:26:30 -0400, Tony Baldwin wrote:
> I've got a little cron job,
> just trying to fire off a script (see http://tonyb.us/mattbot ) and it's
> not firing.
>
> I have other jobs on the same crontab that do. When I run the script
> manually, it
On Sat, May 5, 2012 at 6:26 PM, Tony Baldwin wrote:
> I've got a little cron job,
> just trying to fire off a script (see http://tonyb.us/mattbot )
> and it's not firing.
>
> I have other jobs on the same crontab that do.
> When I run the script manually, it runs.
On 06/05/12 01:26, Tony Baldwin wrote:
> I've got a little cron job,
> just trying to fire off a script (see http://tonyb.us/mattbot )
> and it's not firing.
[...]
> Probably something really obvious I'm overlooking, but the more I look,
> the less I see why there
I've got a little cron job,
just trying to fire off a script (see http://tonyb.us/mattbot )
and it's not firing.
I have other jobs on the same crontab that do.
When I run the script manually, it runs.
I've tried, in my user crontab
0 * * * * /path/to/script
or
@hourly /path
On Thu, Mar 8, 2012 at 11:32 PM, T o n g wrote:
>
> I've got the following entry in my cron job:
>
> 1 1 1 */2 * me my-this-job
>
> How often will it execute?
>
> Checking the log, I notice that it run on Jan 1 and Mar 1. That's really
> not something that I&
Hi,
I've got the following entry in my cron job:
1 1 1 */2 * me my-this-job
How often will it execute?
Checking the log, I notice that it run on Jan 1 and Mar 1. That's really
not something that I've been expecting for. I have another cron job fired
at Feb 1, so no doubt t
the email give for the failure?
> > > > Chris
> > >
> > >
> > > mv: cannot stat `/var/log/apache2/MY.log': No such file or directory
> > > Clearly not merging logs and creating the MY.log file.
> > > I will try with the fully path
ache2/MY.log': No such file or directory
> > Clearly not merging logs and creating the MY.log file.
> > I will try with the fully path and see happens tonight.
>
> Your first cron job:
> 0 1 * * * mergelog /var/log/apache2/access.log
> /var/log/apache2/other_vhosts_acc
it without my intervention?
> >
> >
> > What reason does the email give for the failure?
> > Chris
>
>
> mv: cannot stat `/var/log/apache2/MY.log': No such file or directory
> Clearly not merging logs and creating the MY.log file.
> I will try wit
On Wed, Feb 08, 2012 at 09:18:32AM +, Chris Davies wrote:
> Tony Baldwin wrote:
> > 0 1 * * * mergelog /var/log/apache2/access.log [...]
> > Every day I get an e-mail telling me this failed.
>
> > Now, I can go in and to this manually,
> > Why can't cron do it without my intervention?
>
>
Tony Baldwin wrote:
> 0 1 * * * mergelog /var/log/apache2/access.log [...]
> Every day I get an e-mail telling me this failed.
> Now, I can go in and to this manually,
> Why can't cron do it without my intervention?
What reason does the email give for the failure?
Chris
--
To UNSUBSCRIBE, e
On Wed, 2012-02-08 at 01:27 -0500, Tony Baldwin wrote:
> I have the following in my root crontab on my webserver:
>
> 0 1 * * * mergelog /var/log/apache2/access.log
> /var/log/apache2/other_vhosts_access.log /var/log/apache2/my.log >
> MY.log
> 4 2 1 * * * mv /var/log/apache2/MY.log /var/log/apa
I have the following in my root crontab on my webserver:
0 1 * * * mergelog /var/log/apache2/access.log
/var/log/apache2/other_vhosts_access.log /var/log/apache2/my.log >
MY.log
4 2 1 * * * mv /var/log/apache2/MY.log /var/log/apache2/my.log
5 5 1 * * * webalizer
Every day I get an e-mail te
"Boyd Stephen Smith Jr." writes:
> Finally, while you currently make your order via phone, it may be that
> your distributor has a more easily automated method, so it may be
> worth talking to their customer support and exploring the other
> ordering options.
LOL :)
--
Burton Samograd
--
To
ering horny goat weed every week manually so can
>> >someone please make a [...] cron job to do this for me?
>>
>> You'll have to better describe how you order horny goat weed in order for
>> me to write a script that does it for you. Computers are very good at
>&g
Thanks but how did you make the shell script? Please post contents to list.
Thanks.
> Date: Sat, 21 Aug 2010 00:57:22 +0400
> Subject: Re: Cron job
> From: eero.voloti...@iki.fi
> To: debiantux...@hotmail.com
> CC: debian-user@lists.debian.org
>
> 2010/8/20 Poo Py :
> &
2010/8/20 Poo Py :
> Hi I'm tired of fucking ordering horny goat weed every week manually so can
> someone please make a fucking cron job to do this for me? Many thanks and
> god bless your kind souls.
>
crontab -e and:
@weekly /path/to/order_horny_goat_weed.sh
--
Eero
-
On Sun, May 9, 2010 at 18:42, David Baron wrote:
> >> At certain times, seems Friday noontime, I am unable to shutdown the
> >> system. Instead of the usual scripts to killing all processes,
> unmounting
> >> everything and will now halt, goodby, I get:
> >>
> >> process running pstree (or somet
>> At certain times, seems Friday noontime, I am unable to shutdown the
>> system. Instead of the usual scripts to killing all processes, unmounting
>> everything and will now halt, goodby, I get:
>>
>> process running pstree (or something like that)
>> shutdown aborted
>>
>> At this point, th
> At certain times, seems Friday noontime, I am unable to shutdown the system.
> Instead of the usual scripts to killing all processes, unmounting everything
> and will now halt, goodby, I get:
> process running pstree (or something like that)
> shutdown aborted
> At this point, the system (or at
On Sun, May 9, 2010 at 01:22, David Baron wrote:
> At certain times, seems Friday noontime, I am unable to shutdown the
> system.
> Instead of the usual scripts to killing all processes, unmounting
> everything
> and will now halt, goodby, I get:
>
> process running pstree (or something like that
At certain times, seems Friday noontime, I am unable to shutdown the system.
Instead of the usual scripts to killing all processes, unmounting everything
and will now halt, goodby, I get:
process running pstree (or something like that)
shutdown aborted
At this point, the system (or at least any
<87a8dc10910270120y754f590es1019c2bbb76e8...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
You are right only the apache2 directly needs "execute" permission and not =
the files inside it.
#chmod 755 /var/log/apache
Actually the log file itself doesn't need the execute permission. You
need that on directory you want to access a file from.
On Tue, Oct 27, 2009 at 10:23 AM, Kushal Koolwal
wrote:
>
> <20091027035155.gb5...@localhost.localdomain>
> Content-Type: text/plain; charset="iso-8859-1"
> Content-Transf
On Tue, Oct 27, 2009 at 9:51 AM, Andrew Sackville-West
wrote:
> On Mon, Oct 26, 2009 at 07:08:04PM -0700, Kushal Koolwal wrote:
>>
>> <20091027012939.ga19...@localhost.localdomain>
>> Content-Type: text/plain; charset="iso-8859-1"
>> Content-Transfer-Encoding: quoted-printable
>> MIME-Version: 1.
<20091027035155.gb5...@localhost.localdomain>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Ahhh I finally resolved it.
chmod 755 -R /var/log/apache2/*
did the trick. It's funny that it needs execute permission also. No where i=
n
On Mon, Oct 26, 2009 at 07:08:04PM -0700, Kushal Koolwal wrote:
>
> <20091027012939.ga19...@localhost.localdomain>
> Content-Type: text/plain; charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
> MIME-Version: 1.0
>
>
> > Try becoming the www-data user and trying the above
>
>
<20091027012939.ga19...@localhost.localdomain>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
> Try becoming the www-data user and trying the above
> line from the command line directly? perhaps you'll get some helpful
> output.
A
OT get updated.
>
> However if I change the awstats cron job to be executed by "root" like this:
> 0,10,20,30,40,50 * * * * root [ -x /usr/lib/cgi-bin/awstats.pl -a
> -f /etc/awstats/awstats.conf -a -r /var/log/apache2/access.log ]
> && /usr/lib/cgi-bin/awstats.pl -con
/cgi-bin/awstats.pl -config=mydomain -update>/dev/null
The Syslog shows that the above job is being executed but my webpage stats
(http://mydomain/awstats/awstats.pl) do NOT get updated.
However if I change the awstats cron job to be executed by "root" like this:
0,10,20,30,40,50 *
On Thu, Jun 18, 2009 at 10:24:31AM -0500, John W Foster wrote:
> I have been experimenting a bit and have tried this command line for
> upgrading my system;
>
> apt-get -y update; apt-get -y upgrade
>
> It works fine if issued from a root terminal. However as a command line
> issued as 'root' fr
I have been experimenting a bit and have tried this command line for
upgrading my system;
apt-get -y update; apt-get -y upgrade
It works fine if issued from a root terminal. However as a command line
issued as 'root' from webmin it fails with this error;
-
Ign
On Fri, 2008-10-17 at 19:45 +0300, Andrei Popescu wrote:
> On Fri,17.Oct.08, 18:10:26, Emanoil Kotsev wrote:
>
> > > this doesn't seem to be true the job runs and produces output and
> > > root mail is (via /etc/aliases - thanks to Doug!) sent to me but yet I
> > > don't get any o/p from /etc
On Fri, 17 Oct 2008 19:10:01 +0200, Emanoil Kotsev wrote:
>> On Fri,17.Oct.08, 18:10:26, Emanoil Kotsev wrote:
>>
>>> > this doesn't seem to be true the job runs and produces output
>>> > and root mail is (via /etc/aliases - thanks to Doug!) sent to me but
>>> > yet I don't get any o/p from
Andrei Popescu wrote:
> On Fri,17.Oct.08, 18:10:26, Emanoil Kotsev wrote:
>
>> > this doesn't seem to be true the job runs and produces output and
>> > root mail is (via /etc/aliases - thanks to Doug!) sent to me but yet I
>> > don't get any o/p from /etc/cron.daily jobs whereas I do from al
On Fri,17.Oct.08, 18:10:26, Emanoil Kotsev wrote:
> > this doesn't seem to be true the job runs and produces output and
> > root mail is (via /etc/aliases - thanks to Doug!) sent to me but yet I
> > don't get any o/p from /etc/cron.daily jobs whereas I do from all my
> > crontab jobs...
>
>
michael wrote:
> On Tue, 2008-10-14 at 14:18 +0100, Dave Ewart wrote:
>> On Tuesday, 14.10.2008 at 13:22 +0100, michael wrote:
>>
>> > If I wish to have, say, a backup script running daily by the system (ie
>> > with su privileges) and to have access to any std out/err output what's
>> > the reco
On Tue, 2008-10-14 at 14:18 +0100, Dave Ewart wrote:
> On Tuesday, 14.10.2008 at 13:22 +0100, michael wrote:
>
> > If I wish to have, say, a backup script running daily by the system (ie
> > with su privileges) and to have access to any std out/err output what's
> > the recommended Debian way to d
On Tue, Oct 14, 2008 at 02:55:15PM +0100, michael wrote:
> On Tue, 2008-10-14 at 14:18 +0100, Dave Ewart wrote:
> > On Tuesday, 14.10.2008 at 13:22 +0100, michael wrote:
> > I think the standard output for jobs run out of cron.daily will
> > typically go to root's mailbox.
>
> Well, root seems not
On Tue, 2008-10-14 at 14:59 +0100, Dave Ewart wrote:
> On Tuesday, 14.10.2008 at 14:55 +0100, michael wrote:
>
> > > I suggest writing/rewriting backup.sh so that it writes its output
> > > to well-defined files, rather than relying on the behaviour of
> > > standard output/error.
> >
> > I thoug
On Tue, 2008-10-14 at 14:57 +0100, Steve Kemp wrote:
> On Tue Oct 14, 2008 at 14:55:15 +0100, michael wrote:
>
> > ratty:~# ls /var/mail
> > mail michael
> > ratty:~#
>
> You might find that /var/mail/mail is mail for the root user.
>
> Steve
well I did check it ;)
but it didn't have a rece
On Tuesday, 14.10.2008 at 14:55 +0100, michael wrote:
> > I suggest writing/rewriting backup.sh so that it writes its output
> > to well-defined files, rather than relying on the behaviour of
> > standard output/error.
>
> I thought about this but presumed if there was an already set-up
> mechani
On Tue Oct 14, 2008 at 14:55:15 +0100, michael wrote:
> ratty:~# ls /var/mail
> mail michael
> ratty:~#
You might find that /var/mail/mail is mail for the root user.
Steve
--
Managed Anti-Spam Service
http://mail-scanning.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
On Tue, 2008-10-14 at 14:18 +0100, Dave Ewart wrote:
> On Tuesday, 14.10.2008 at 13:22 +0100, michael wrote:
>
> > If I wish to have, say, a backup script running daily by the system (ie
> > with su privileges) and to have access to any std out/err output what's
> > the recommended Debian way to d
On Tuesday, 14.10.2008 at 13:22 +0100, michael wrote:
> If I wish to have, say, a backup script running daily by the system (ie
> with su privileges) and to have access to any std out/err output what's
> the recommended Debian way to do so?
>
> I've tried
> a) create $HOME/bin/backup.sh script
>
If I wish to have, say, a backup script running daily by the system (ie
with su privileges) and to have access to any std out/err output what's
the recommended Debian way to do so?
I've tried
a) create $HOME/bin/backup.sh script
b) sudo ln -is $HOME/bin/backup.sh /etc/cron.daily
and it appears to
Le Friday 04 April 2008 11:53:48 Pete Kay, vous avez écrit :
> Hi,
>
> Is there any utility that can help me to check the cron jobs that are
> currently running under Linux?
> If there is one, would you please kindly let me know?
>
If you mean the jobs which are effectively running, any process vi
Hi,
Is there any utility that can help me to check the cron jobs that are
currently running under Linux?
If there is one, would you please kindly let me know?
Thanks,
Pete
Tom Scrape wrote:
> Is there a location (eg. log file) where run-parts activity can be found? Or
> is
> it rather just hit-and-miss debugging when trying to figure out a problem?
Output is normally not generated. It's only generated in case of an
error. Since it is executed by cron (<== /etc
> -Original Message-
> Sent: Thursday, June 07, 2007 1:32 AM
>
> Tom Scrape wrote:
> > Cron.log shows nothing:
> > [EMAIL PROTECTED]:/var/log# cat cron.log |grep pflogsumm
> > [EMAIL PROTECTED]:/var/log#
>
> Err...
>
> The program is not executed by cron but by run-parts (which is
> exec
Tom Scrape wrote:
> My /etc/cron.daily contains the problem file:
> [EMAIL PROTECTED]:/etc/cron.daily# ll pflogsumm-daily.cron
> -rwxr-xr-x 1 root root 354 2007-06-06 08:49 pflogsumm-daily.cron
> Cron.log shows nothing:
> [EMAIL PROTECTED]:/var/log# cat cron.log |grep pflogsumm
> [EMAIL PROTECTED]
> -Original Message-
> Sent: Wednesday, June 06, 2007 10:40 AM
>
> On Wed, 6 Jun 2007, Tom Scrape wrote:
>
> > I have a cron job that's not running when I think it should
> > be... that is, it's not running at all.
> >
> > My /etc
On Wed, 6 Jun 2007, Tom Scrape wrote:
I have a cron job that's not running when I think it should
be... that is, it's not running at all.
My /etc/cron.daily contains the problem file:
[EMAIL PROTECTED]:/etc/cron.daily# ll pflogsumm-daily.cron
-rwxr-xr-x 1 root root 354 2007-0
I have a cron job that's not running when I think it should
be... that is, it's not running at all.
My /etc/cron.daily contains the problem file:
[EMAIL PROTECTED]:/etc/cron.daily# ll pflogsumm-daily.cron
-rwxr-xr-x 1 root root 354 2007-06-06 08:49 pflogsumm-daily.cron
This file contai
On 5/29/07, Douglas Allan Tutty <[EMAIL PROTECTED]> wrote:
On Tue, May 29, 2007 at 09:42:30AM -0700, Jason Dunsmore wrote:
>
> Whenever updatedb runs via cron, it goes to sleep and never finishes
> the job, leaving all these processes running:
>
> 29519 ?S 0:00 /USR/SBIN/CRON
> 29520
On Tue, May 29, 2007 at 09:42:30AM -0700, Jason Dunsmore wrote:
>
> Whenever updatedb runs via cron, it goes to sleep and never finishes
> the job, leaving all these processes running:
>
> 29519 ?S 0:00 /USR/SBIN/CRON
> 29520 ?Ss 0:00 /bin/sh -c test -x /usr/sbin/anacron
Hi,
Whenever updatedb runs via cron, it goes to sleep and never finishes
the job, leaving all these processes running:
29519 ?S 0:00 /USR/SBIN/CRON
29520 ?Ss 0:00 /bin/sh -c test -x /usr/sbin/anacron || ( cd / && run
29521 ?S 0:00 /bin/sh -c test -x /usr/sbi
On Tue, Mar 20, 2007 at 08:11:43AM +, Liam O'Toole wrote:
> On Mon, 19 Mar 2007 19:59:18 -0400
> Michael Pobega <[EMAIL PROTECTED]> wrote:
>
> > On Mon, Mar 19, 2007 at 10:31:07PM +, Liam O'Toole wrote:
> > > On Mon, 19 Mar 2007 17:37:29 -0400
> > > Michael Pobega <[EMAIL PROTECTED]> wrote
On Tue, Mar 20, 2007 at 01:41:22AM -0400, Celejar wrote:
> On Mon, 19 Mar 2007 17:37:29 -0400
> Michael Pobega <[EMAIL PROTECTED]> wrote:
> >
> > I know ddclient can run as a daemon, but most of the time that daemon
> > doesn't work and I end up just having to run ddclient manually myself.
> > I'
On Mon, 19 Mar 2007 19:59:18 -0400
Michael Pobega <[EMAIL PROTECTED]> wrote:
> On Mon, Mar 19, 2007 at 10:31:07PM +, Liam O'Toole wrote:
> > On Mon, 19 Mar 2007 17:37:29 -0400
> > Michael Pobega <[EMAIL PROTECTED]> wrote:
> >
> > > I'm trying to get ddclient to run as a cronjob [...]
> > >
>
On Mon, 19 Mar 2007 17:37:29 -0400
Michael Pobega <[EMAIL PROTECTED]> wrote:
[snip]
> I know ddclient can run as a daemon, but most of the time that daemon
> doesn't work and I end up just having to run ddclient manually myself.
> I'd just like to be able to set it as a cronjob, if that's possibl
On Mon, Mar 19, 2007 at 10:31:07PM +, Liam O'Toole wrote:
> On Mon, 19 Mar 2007 17:37:29 -0400
> Michael Pobega <[EMAIL PROTECTED]> wrote:
>
> > I'm trying to get ddclient to run as a cronjob [...]
> >
>
> Just invoke ddclient from a script in one of the directories mentioned
> in /etc/cront
On Mon, 19 Mar 2007 17:37:29 -0400
Michael Pobega <[EMAIL PROTECTED]> wrote:
> I'm trying to get ddclient to run as a cronjob, but before I do it I
> was wondering if it is not safe to do this.
>
> I normally run under a user account (And not root), and ddclient can't
> be run by anyone but the o
I'm trying to get ddclient to run as a cronjob, but before I do it I
was wondering if it is not safe to do this.
I normally run under a user account (And not root), and ddclient can't
be run by anyone but the owner (It won't let you run it, even if you
have group access; "/etc/ddclient.conf must o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nate Bargmann wrote:
>> And do not forget that QEMU is mostly a GUI application, so you will
>> probably need to run xorg.
>
> Thanks for pointing that out. That may be another area to work around
> as well.
As Joshua Kugler already stated, you can
* Linas ??virblis <[EMAIL PROTECTED]> [2007 Feb 23 10:01 -0600]:
> A much simpler solution would be to have QEMU started by cron, and set
> up the guest OS to shut down after doing something. Or you could run
> QEMU in snapshot mode and simply kill it, when not needed. Or... the
> possibilities ar
On Friday 23 February 2007 07:00, Linas Žvirblis wrote:
> And do not forget that QEMU is mostly a GUI application, so you will
> probably need to run xorg.
You can run qemu headless, with a virtual framebuffer. Makes for a virtual
machine you connect to via VNC to view.
--
Joshua Kugler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nate Bargmann wrote:
> I am wanting to restart a QEMU virtual machine from a cron entry, let
> the VM do something, and then after a period of time freeze the VM
> until the next day. After reading the docs and browsing the Web for a
> few days, I'm
I am wanting to restart a QEMU virtual machine from a cron entry, let
the VM do something, and then after a period of time freeze the VM
until the next day. After reading the docs and browsing the Web for a
few days, I'm not so sure this is possible.
Of course, much control is available interacti
On Wed, 2 Aug 2006, Oliver Jato wrote:
> > Example (which not works)
> > index.php
> > >
> > // Read last timestamp
> > $file_name = "last_mail";
> > $file = fopen($file_name, "r+");
> > $content = fread($file, filesize($filename));
> >
> > $time = time();
> > if($file[0]
> Example (which not works)
> index.php
>
> // Read last timestamp
> $file_name = "last_mail";
> $file = fopen($file_name, "r+");
> $content = fread($file, filesize($filename));
>
> $time = time();
> if($file[0] >= $time + $diff) {
> include "mai
Hello Henning!
> I have a php-site on which I want to send periodic mails out.
> I want cron to schedule that, but I don't know how to get cron to
> manage that.
> I have my own Linux-box on which I put the line
> lynx http://blabla.com/mailscript.php
> but on my hosted webserver, there are obviou
I have a php-site on which I want to send periodic mails out.I want cron to schedule that, but I don't know how to get cron tomanage that.I have my own Linux-box on which I put the linelynx
http://blabla.com/mailscript.phpbut on my hosted webserver, there are obviously no lynx, cause it don'twork.
>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 subject of "unsubscribe". T
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: start-stop-daemon: command not fou
running is called with a cron job also:
wget -O /var/mp3/openline-`date +%m-%d-%Y`.ogg
http://localhost:8000/kwlv.ogg
The cron job will start the script at my set time, I'm just looking for a
way to stop the script. My command line works from the command line it just
doesn't work from cro
Hello,
I am experiencing a problem with lprng on several machines (all woody):
/etc/cron.daily/lprng:
co: file 'hfA615', age 45.01 hours > 24.00 hours maximum (removing)
I get messages like the above every day.
Users have also complained about missing print jobs, it would seem they
are spooled
b
On 2004-04-23, Adam Funk penned:
>
> I figured this out on my own and I'm posting the solution in case
> anybody else looks for it.
>
> /etc/cron.daily/aide now contains the lines:
> AIDEARGS="-V0"
>
> aide $AIDEARGS --$COMMAND >"$LOGDIR/$LOGFILE" 2>"$ERRORTMP"
>
> Changing it to
> AIDEARGS=""
On Saturday 17 April 2004 15:10, Adam Funk wrote:
> Following a recent apt-get upgrade, the morning e-mail from aide's
> cron job is a lot shorter (and less useful that it used to be):
> It used to include the list of added|removed|changed files (althought
> truncated if it
Following a recent apt-get upgrade, the morning e-mail from aide's cron
job is a lot shorter (and less useful that it used to be):
*
This is an automated report generated by the Advanced Intrusion
Detection
Environment on garcia at 2004-04-17 06:25.
AIDE produced no errors.
Output o
On Mon, Aug 12, 2002 at 09:13:12PM -0600, James Roberge wrote:
>
> Hey everyone. I seem to be having a little problem on my debian system. It
> seems that the system is crashing during the daily cron job. But, it DOES
> NOT happen every day.
>
> Here is a snip from /var/
Hello,
My daily dselecting recently lead to a PostgreSQL update to version 7.3 on my debian
testing box. Everything works fine aside from this error showing up daily:
> From: [EMAIL PROTECTED] (Cron Daemon)
> To: [EMAIL PROTECTED]
> Subject: Cron <[EMAIL PROTECTED]> /usr/bin/test -x
> /usr/lib/
1 - 100 of 144 matches
Mail list logo