[Grozni Majmun]

Every time I reboot, I get an email from Cron Daemon with a couple of errors. It looks like this:

From: rotne (Cron Daemon)
Date: Sat May 04, 2002 11:15:28 PM US/Eastern
To: rotne
Subject: Cron <rotne@rotne-2> cd "/Applications/Ubero"; ./uberorunner &

cd: no such file or directory: /Applications/Ubero
zsh: no such file or directory: ./uberorunner

I have messed around with so many different DC things that I am not entirely sure what caused this. Perhaps it is left over from an early version of the MDC3 app. So, my question is: where is the file that causes this? I am not entirely UNIX challenged, but not particularly proficient either. (I can navigate in the terminal and edit files in pico)

Any help will be much appreciated

[reader50]

It's caused by a crontab entry to "cd to Applications/Ubero", and then launch "uberorunner" in nohup mode. Use CronniX to check your own crontable, root's, and system's crontables. It should be in one of them.

[Grozni Majmun]

Originally posted by reader50:
<STRONG>It's caused by a crontab entry to "cd to Applications/Ubero", and then launch "uberorunner" in nohup mode. Use CronniX to check your own crontable, root's, and system's crontables. It should be in one of them.</STRONG>

Thanks reader. I downloaded cronnix, but it just quits instantly when I start it. I did 'locate crontab' and found a crontab in /private/sbin and one in /etc

the one in /etc looks normal. I can pretty much understand what is in there and it doesn't say anything about ubero. The other one is mostly gobbledygook. I mean, when I do 'cat /private/sbin/crontab', I get a few screenfuls of seemingly random characters, with some snippets of text. This is not normal, right? Should I try to replace that file or what?

Thanks again

[reader50]

files in "bin" or "sbin" are usually binaries (executable files). They will appear as gobblygook if opened in a text editor.

I have one in /usr/bin -- that one is a binary.

I have another one in /private/etc/ -- that one is the System's crontab. The only entries are daily, weekly, and monthly outputs.

All other crontabs are stored in /private/var/cron/tabs/
The crontabs here will be named with user names. The system will try to keep you out of cron/, that is a restricted folder by default. su to root and go in, or su to root and change the permissions if yours is a single-user computer.

[ 05-05-2002: Message edited by: reader50 ]

[Grozni Majmun]

Thanks,

I found it. It was put there by Mikkyo's uberorunner script, and then I just forgot about it. It is a file called /var/cron/tabs/rotne

The file reads:

# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (./uberotab installed on Mon Apr 8 22:02:14 2002)
# (Cron version -- $FreeBSD: src/usr.sbin/cron/crontab/crontab.c,v 1.17 2001/06/16 03:16:52 peter Exp $)
@reboot cd "/Applications/Ubero"; ./uberorunner &

That is all there is in it. Is it ok to just delete the file, or is there a hidden danger in that?

[reader50]

I'm not an expert on MDC3 or the Ubero scripts. If the original app or utility is gone, it should be perfectly safe to remove that crontab. If it returns, you will need to hunt up the startup item that is responsible.

[Grozni Majmun]

Originally posted by reader50:
<STRONG>I'm not an expert on MDC3 or the Ubero scripts. If the original app or utility is gone, it should be perfectly safe to remove that crontab. If it returns, you will need to hunt up the startup item that is responsible.</STRONG>

Thanks a lot reader. I removed the crontab, restarted, and there was no message this time. I think the crontab was set when I tried to run Mikkyo's uberoscript, but it is not something that is set to run on a regular basis.

[mikkyo]

Originally posted by Grozni Majmun:
<STRONG>
Thanks a lot reader. I removed the crontab, restarted, and there was no message this time. I think the crontab was set when I tried to run Mikkyo's uberoscript, but it is not something that is set to run on a regular basis.</STRONG>

Yep that was set to launch Ubero at startup, but you deleted Ubero obviously.
To see/remove crontabs for future reference jsut do:
crontab -l
(that's an L)
to list the cronfile for that user
and
crontab -r
to remove it for the current user.
If you ran the Uberorunner script as root, you would have to become root to view root's crontab and use the above commands to see anything.

As you discovered you can always remove the file in /var/cron/tabs that corresponds to the user who set up the crontab as well.

Originally posted by mikkyo:
<STRONG>

Yep that was set to launch Ubero at startup, but you deleted Ubero obviously.
To see/remove crontabs for future reference jsut do:
crontab -l
(that's an L)
to list the cronfile for that user
and
crontab -r
to remove it for the current user.
If you ran the Uberorunner script as root, you would have to become root to view root's crontab and use the above commands to see anything.

As you discovered you can always remove the file in /var/cron/tabs that corresponds to the user who set up the crontab as well.</STRONG>

There is also
<BLOCKQUOTE><font size="1"face="Geneva, Verdana, Arial">code:</font><HR><pre><font size=1 face=courier>crontab -e</font>[/code]
This allows you to edit the crontab in situ. Whenever I have used this the default editor was 'vi'. Not sure if you can alter this to be pico or emacs or another editor.
What I tend to do is:
<BLOCKQUOTE><font size="1"face="Geneva, Verdana, Arial">code:</font><HR><pre><font size=1 face=courier>crontab -l &gt; filename</font>[/code]
then edit the file created. Followed by:
<BLOCKQUOTE><font size="1"face="Geneva, Verdana, Arial">code:</font><HR><pre><font size=1 face=courier>crontab filename</font>[/code]
to load the new file into the cron daemon. Review the man pages for full details.