I'm running MAC OS X and I'm wondering how I start 'nixey programs (not normal apps) on startup? Things like the dnet client and hxd Hotline Server. Anyone know? (1 Reply)
hi
i want to know the way by which i put any file somewhere and it get s started when the system restarts or bots
i mean whenever my system starts that application must also start
thanks (3 Replies)
Hi all,
Before I start, I just wanted to mention that I did check in the "I'm new to Unix, what books should I read" sub-forum but didn't find anything that I thought was useful (or maybe I don't know what I'm looking for!).
I'm a Windows Admin, have been for quite a few years, all the way... (12 Replies)
As topic, assume we have a service called "blahservice"
and we can start it by:
startsrc -s blahservice
what is the best practice to run such command when system start?
- directly use mkitab to add it into /etc/inittab
or
- drop startup scripts in /etc/rc.d/rcX.d
I know they... (4 Replies)
Hey!
I'm working on a script that will add a user, create some configfiles, and add a crontab for the user.
The crontab looks like the following:
@reboot /home/user/program config.conf &
I would like for this process to start at the end of my script under the corresponding username by... (0 Replies)
Hi,
I am trying to remove lines once a string is found till another string is found including the start string and end string. I want to basically grab all the lines starting with color (closing bracket). PS: The line after the closing bracket for color could be anything (currently 'more').... (1 Reply)
I need to replace the (*) in the fist of a list with numbers using sed for example >
this file contain a list
* linux
* computers
* labs
* questions
to >>>>
this file contain a list
1. linux
2. computers
3. labs
4. questions (7 Replies)
Below are my custom period start and end dates based on a calender, these dates are placed in a file, for each period i need to split into three weeks for each period row, example is given below.
Could you please help out to achieve solution through shell script..
File content:
... (2 Replies)
Discussion started by: nani2019
2 Replies
LEARN ABOUT NETBSD
compat_osf1
COMPAT_OSF1(8) BSD System Manager's Manual COMPAT_OSF1(8)NAME
compat_osf1 -- setup procedure for running OSF/1 binaries
DESCRIPTION
NetBSD supports running OSF/1 (a.k.a Digital Unix, a.k.a. Tru64) binaries on NetBSD/alpha systems. Most programs should work, including the
ones that use the shared object libraries. Programs that make direct MACH system calls will not work. The OSF/1 compatibility feature is
active for kernels compiled with the COMPAT_OSF1 option enabled (see options(4)).
To run dynamically linked programs, you will need the OSF/1 shared libraries, runtime linker, and certain configuration files found in /etc.
These are installed in a ``shadow root'' directory called /emul/osf1. Any file operations done by OSF/1 programs run under NetBSD will look
in this directory first, and fall back to the file system proper. So, if an OSF/1 program opens /etc/svc.conf, NetBSD will first try to open
/emul/osf1/etc/svc.conf, and if that file does not exist it will then try /etc/svc.conf. Shared libraries and configuration specific to
OSF/1 should be installed in the shadow tree.
Setting up /emul/osf1
The simple technique is to install pkgsrc/emulators/osf1_lib. (You may also want to install pkgsrc/www/navigator and/or pkgsrc/www/communi-
cator.)
Alternatively, if you have access to an OSF/1 machine and if the licensing details permit, you can copy the contents of:
/shlib
/usr/shlib
/etc/sia
/usr/lib/X11/locale
(The latter is required to run Netscape Navigator or Communicator.)
Also copy
/etc/svc.conf
/usr/ccs/lib/cmplrs/otabase/libots.so
/sbin/loader
Or, simply NFS mount the appropriate directories under /emul/osf1.
SEE ALSO config(1), options(4)BUGS
Your hostname(1) must contain a dot or your resolv.conf(5) must contain a search line. Without one of those, the OSF/1 resolver will die and
no hostname resolution will be possible.
Certain values in /emul/osf1/etc/svc.conf can cause programs to fail with ``Bad system call''.
Pathnames pointed to by symbolic links are not looked up in the shadow root when running an OSF/1 executable. This is not consistent.
BSD November 4, 1999 BSD