HELP: SCO Unix startup commands
ajb27
can hire one. Although I have used UNIX for many years, I'm not at the
level as an administrator. The responsibilities I have now are rudimentary:
make sure the backups occur, kill occasional processes, create new
accounts.
I've been approached my boss to try to get a unix command to load
whenever the system is rebooted. The command is "sink" and it should run
in the background. For the Windows world, this is tantamount to
placing commands in config.sys, autoexec.bat, even startup folder Win95+. I'm
rather comfortable editing the startup file, as long as this doesn't disrupt
other operations.
Surely there is a way to get this to work in Sco-Unix. If someone
could please point me in the right direction, I would be very grateful.
Thanks in advance. Please reply by email as well as posting.
ajb
ajb27
ajb27
ajb27
ajb27
Steve Wertz
> I've been approached my boss to try to get a unix command to load
> whenever the system is rebooted. The command is "sink" and it should run
> in the background.
Perhaps the boss means 'sync'. 'man ADM sync' for more info.
I don't know what this will fix, though (except some hand-tension
or obsessive-compulsive disorders). You would presumably put them
into the culprit /etc/rc2.d/* scripts, or one of your own scriptsa
(called S99-whatever).
Perhaps you should post what the underlying problem really is,
though..
> For the Windows world, this is tantamount to placing commands in
> config.sys, autoexec.bat, even startup folder Win95+.
..without the analogies, please :-)
-sw
Jean-Pierre Radley
| I've been designated the acting Unix Administrator until my employer
| can hire one. Although I have used UNIX for many years, I'm not at
| the level as an administrator. The responsibilities I have now are
| rudimentary: make sure the backups occur, kill occasional processes,
| create new accounts.
|
| I've been approached my boss to try to get a unix command to load
| whenever the system is rebooted. The command is "sink" and it should
| run in the background. For the Windows world, this is tantamount to
| placing commands in config.sys, autoexec.bat, even startup folder
| Win95+. I'm rather comfortable editing the startup file, as long as
| this doesn't disrupt other operations.
|
| Surely there is a way to get this to work in Sco-Unix. If someone
| could please point me in the right direction, I would be very
| grateful.
Posting your message four times guarantees 4X irritation, not 4 times as
many replies. :-)
| Thanks in advance. Please reply by email as well as posting.
Uh, really not. Post in a newsgroup, read the answers there as well.
Add your command
sink &
to /etc/rc.d/7/udaemons.
--
JP
Tony Lawrence
> ajb27 <aj...@drexel.edu> wrote:
>
> > For the Windows world, this is tantamount to placing commands in
> > config.sys, autoexec.bat, even startup folder Win95+.
>
> ..without the analogies, please :-)
I'm going to disagree with that. Analogies from a model the
poster understands are often very helpful in understanding
what he really means.
--
Tony Lawrence (to...@aplawrence.com)
SCO articles, help, book reviews, tests,
job listings and more : http://www.ApLawrence.com
Jim Richardson
ajb27 <aj...@drexel.edu> wrote:
> I've been designated the acting Unix Administrator until my employer
> can hire one. Although I have used UNIX for many years, I'm not at
the
> level as an administrator. The responsibilities I have now are
rudimentary:
> make sure the backups occur, kill occasional processes, create new
> accounts.
>
> I've been approached my boss to try to get a unix command to load
> whenever the system is rebooted. The command is "sink" and it should
run
> placing commands in config.sys, autoexec.bat, even startup folder
> rather comfortable editing the startup file, as long as this doesn't
disrupt
> other operations.
>
> Surely there is a way to get this to work in Sco-Unix. If someone
> could please point me in the right direction, I would be very
grateful.
>
>
>
I'm not familar with 'sink'. Is it a program that you can describe?
There is the unix command 'sync' which flushes the buffers to disk.
It's usually run during a shutdown procedure to make sure all the writes
have completed, but it would do little effective on boot, and runns only
once so there's no need for it to be a background process.
If you want to run a command at startup, create a file in /etc/rc2.d
called S99sink. In the file place the fully qualified pathname to the
command. Note that the S is a capital.
If that's not exactly what you need, please post exactly what you're
trying to do and I'm sure some of the more qualified folks will have an
answer for you.
--
Jim Richardson
I like NT because it constantly reminds me of my daughter.
"Honest Daddy, I wasn't doing anything and it just broke."
Sent via Deja.com http://www.deja.com/
Before you buy.
Tom Parsons
A quick "man sink" might make one wonder what they are trying to
accomplish.
--
==========================================================================
Tom Parsons t...@tegan.com
==========================================================================
Bill Vermillion
>> I've been approached my boss to try to get a unix command to load
>> whenever the system is rebooted. The command is "sink" and it
>> should run in the background.
>Perhaps the boss means 'sync'. 'man ADM sync' for more info.
Why 'sync' on a reboot? Maybe the boss meant when you start the
reboot. Perhaps they don't know about shutdown. I ran across an
SCO system recently where it was always just turned off - no one
had instructed anyone on shutdown.
--
Bill Vermillion bv @ wjv.com
Tim Clarke
> I've been designated the acting Unix Administrator until my employer
> can hire one. Although I have used UNIX for many years, I'm not at the
> level as an administrator. The responsibilities I have now are rudimentary:
> make sure the backups occur, kill occasional processes, create new
> accounts.
>
> I've been approached my boss to try to get a unix command to load
> whenever the system is rebooted. The command is "sink" and it should run
> in the background. For the Windows world, this is tantamount to
> placing commands in config.sys, autoexec.bat, even startup folder Win95+. I'm
> rather comfortable editing the startup file, as long as this doesn't disrupt
> other operations.
>
> Surely there is a way to get this to work in Sco-Unix. If someone
> could please point me in the right direction, I would be very grateful.
>
> Thanks in advance. Please reply by email as well as posting.
>
> ajb
If you are running SCO OPENSERVER then the place to put this command is in the
S..userdef file within directory /etc/rc2.d
Our 'user startup' file is called, eg,: /etc/rc2.d/S97userdef
The 'userdef' file must be executable by root
As files within /etc/rc2.d have a limited PATH environment, from recollection,
you ideally need to specify the full
pathname of 'sink' (eg /usr/bin/sink'
Also, if you wish it to run as a background process, you MUST follow tghe command
name with an ampersand &
Otherwise it will hold up the startup process (on Unix 324 it will effectively
stall the startup process !)
Take care that any output from 'sink' is redirected to the right place,
eg /usr/bin/sink > /dev/null 2> /dev/null &
will direct both normal output and error output down the system ''black hole''
The correct pathname for UNix 324 is different from memory; the system admin
guide has a section on
customising startup. No doubnt openserver also has a section in the on-line
manuals, if you dont mind going
blind reading them !
tc
- bill -
>
> I've been designated the acting Unix Administrator until my employer
> can hire one. Although I have used UNIX for many years, I'm not at the
> level as an administrator. The responsibilities I have now are rudimentary:
> make sure the backups occur, kill occasional processes, create new
> accounts.
>
> I've been approached my boss to try to get a unix command to load
> whenever the system is rebooted. The command is "sink" and it should run
> in the background. For the Windows world, this is tantamount to
> placing commands in config.sys, autoexec.bat, even startup folder Win95+. I'm
> rather comfortable editing the startup file, as long as this doesn't disrupt
> other operations.
>
> Surely there is a way to get this to work in Sco-Unix. If someone
> could please point me in the right direction, I would be very grateful.
>
> Thanks in advance. Please reply by email as well as posting.
>
> ajb
jp recommended /etc/rc.d/7/udaemons
everybody else recommended variations on /etc/rc2.d
could we have an explanation of these two options ?
--
-bill-
Technical Service Systems - bi...@TechServSys.com
Jean-Pierre Radley
|
| jp recommended /etc/rc.d/7/udaemons
| everybody else recommended variations on /etc/rc2.d
|
| could we have an explanation of these two options ?
I've got quite a collection of things I do in /etc/rc.d/[78]/*,
and I'm just used to adding new boot-up tasks there.
For quite a while, SCO OSes have had warnings that /etc/rc.d is
a vestigial repository and SCO might not continue to ship such a
directory, nor look to execute any scripts thereunder. It hasn't
happened yet.
Maybe the guillotine will drop one day, and I will be slightly I
regretful.
Other than that, go with the flow, man: there is typically more
than one way to do any given task on any Unix Operating System.
--
JP
- bill -
Thank you Master.
Do the same warnings apply to /etc/rc2.d ?
Tony Lawrence
>
> Jean-Pierre Radley wrote:
> > For quite a while, SCO OSes have had warnings that /etc/rc.d is
> > a vestigial repository and SCO might not continue to ship such a
> > directory, nor look to execute any scripts thereunder. It hasn't
> > happened yet.
> Thank you Master.
> Do the same warnings apply to /etc/rc2.d ?
No. /etc/rc2.d is Sys V, and it's extremely unlikely that
would be changed- there's no reason to change it, and
there's plenty of reasons not to.
I doubt that the rc.d/* will go away any time soon, either.
It's easy to accomodate it by actually running it from rc2.d
(that's how it's handled now- do a "grep -l rc.d
/etc/rc2.d/*") and people have been tucking things there for
a looong time..
Jean-Pierre Radley
| Jean-Pierre Radley wrote:
| >
| > - bill - propounded (on Fri, Jan 21, 2000 at 04:57:09PM -0500):
| > |
| > | jp recommended /etc/rc.d/7/udaemons
| > | everybody else recommended variations on /etc/rc2.d
| > |
| > | could we have an explanation of these two options ?
| >
| > I've got quite a collection of things I do in /etc/rc.d/[78]/*,
| > and I'm just used to adding new boot-up tasks there.
| >
| > a vestigial repository and SCO might not continue to ship such a
| > directory, nor look to execute any scripts thereunder. It hasn't
| > happened yet.
| >
| > regretful.
| >
| > Other than that, go with the flow, man: there is typically more
| > than one way to do any given task on any Unix Operating System.
| >
| > --
| > JP
|
| Do the same warnings apply to /etc/rc2.d ?
Of course not...
--
JP