Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

cron as persistent process

49 views
Skip to first unread message

Robi

unread,
Mar 8, 2012, 5:19:48 AM3/8/12
to
Hello

I am just playing with cron in OSS. I would like to start cron as
persistent process. I do that by the book as described in "Open System
Services Shell and Utilities Reference Manual" (527188-017) pages
873-875. When i try to add process same way as in example there is
problem with infile parameter. We don't have $NULL process. I can
start without INFILE but this parameter is required. $ZHOME as
parameter is not recommended regarding to document "SCF Reference
Manual for the Kernel Subsystem".

The process is started even if there is no INFILE defined. But i
assume this leads to cron logfile flooding with message "! read: No
such file or directory". Log file is filled until we abort kernel
process.

Please advise how can i start cron.

Thank you and best regards,
Robert

Joachim Schmitz

unread,
Mar 8, 2012, 5:50:56 AM3/8/12
to
By making sure a $NULL is started. As part of an OSS installation it
nowadays gets configured and started anyway. Also as a persisnt process...

Alternativly it might work to use OSS I/O redirection in the STARTUMSG:

STARTUPMSG "-osstty -name /G/cro1 -p /bin/cron -f </dev/null",&



bye, Jojo

wbreidbach

unread,
Mar 8, 2012, 8:11:16 AM3/8/12
to
According to the Knowledge Base it is depending on the OS-release whether you are able to make cron persistent. In older releases it was not possible. Anyhow, the way you can make OSS processes persistent is not very amazing.

Joachim Schmitz

unread,
Mar 8, 2012, 12:32:01 PM3/8/12
to
If cron accepts the -f option, you can make it persistent.
Even if not (ie. with older releases), you could too, using the -d option
and discarding the debug output to /dev/null, but this is more a kludge than
a solution.
Both options keep cron in the forground, this is needed for $ZZKRN to be
able to track it.

> Anyhow, the way you can make OSS processes
> persistent is not very amazing.

Why? I think it works quite well and I'm using it since a long time now, for
cron, inetd, named and even for samba.

Bye, Jojo

wbreidbach

unread,
Mar 9, 2012, 3:10:41 AM3/9/12
to
Am Donnerstag, 8. März 2012 11:19:48 UTC+1 schrieb Robert Bolha:
Am Donnerstag, 8. März 2012 11:19:48 UTC+1 schrieb Robert Bolha:
I am using it for several OSS-processes, too. But using an OSH-process to start your persistent OSS-process is not the way I like it.

Joachim Schmitz

unread,
Mar 9, 2012, 4:54:05 AM3/9/12
to
wbreidbach wrote:
<snip>
> I am using it for several OSS-processes, too. But using an
> OSH-process to start your persistent OSS-process is not the way I
> like it.

So you'd rather like $ZZKRN to be able to start OSS processes directly?
Sounds like a reasonable RFE ;-) although I don't ses it happening anytime
soon.
The 'workaround' of using OSH is just too easy...

Bye, Jojo

wbreidbach

unread,
Mar 9, 2012, 5:32:24 AM3/9/12
to
Am Donnerstag, 8. März 2012 11:19:48 UTC+1 schrieb Robert Bolha:
I agree.
0 new messages