So I worked out a script for Mac OSX from an existing script. This script checks the versionnumber of a plugin and a package. If the plugin version is different from the package it has to update the plugin. The script works fine but the final check fails.
Here is my script:
So lets say the installedversion is OLD and the newestversion is NEW.
It keeps saying ERROR. If I manually check the version number it's updated to version NEW.
If I add a line to the script to echo the ${newlyinstalledversion} to the log file it says OLD.
I tried to add 10 or 20 seconds 'sleep' after the installer command but that didn't help.
Is this a cache problem?
Last edited by mattiasvdm; 12-27-2012 at 06:37 AM..
Reason: added OS
Okee problems...!!
What is happening: Unix server with some programms, workstations are windows 2000, the workstations work good but when you start a programm on the Unix server the CPU of the workstations go to 100% usage resulting that the system gets very slow. The programm well its running so... (2 Replies)
hi,
What is the difference between UBC cache and Metadata cache ? where can i find UBC cache Hits and Metadata cache Hits in hp-ux?
Advanced thanx for the help. (2 Replies)
Does anyone know how the unix buffer / cache is set in a Solaris based system ?
( I presume it is a kernel based setting )
I notice from SAR -d that my read cache is consistently at 100% but my write cache frequently falls below 65%. What does this mean. Should I be tuning the write cache and... (1 Reply)
Hello Moto
I hope someone can help
We's here at work, have a unix box with sco openserver 5 on it, so it has a nice gui interface.. and also a fair few windows computers..
a system admin guy b4 me, has set up a user called neil, which can, when u try to access the unix box using windows... (2 Replies)
Hi all
I am trying to understand the kernel memory management and require assistance in this regard. Kernel first creates the cache memory to perform any subsequent allocation to processes. I could not figure out how it is accomplished. Do kernel directly allocates any hardware cache or allocates... (0 Replies)
Hi all
I saw in Microsoft web site www.SysInternals.com a tool called CoreInfo from able to print out on screen the size of the Data and Instruction caches of your processor, the Locigal to Physical Processor mapping, the number of the CPU sockets. etc..
Do you know if in Linux is available a... (2 Replies)
My server is running HP-UX 11.23 and one Oracle database. The server has 8 CPUs and is mostly idle all the time. Buffer cache is set to 10%min/max with 5GB memory on the server.
I have a user complaining that a batch process is all of a sudden taking a long time to finish. The DBA gave me the... (13 Replies)
Hi All,
could any one point out any open source test-suites for "File cache" testing and as well as performance test suites for the same. Currently my system is up with Linux/ext4.
Regards
Manish (0 Replies)
I have DNS Server running in solaris 10 .
There is website called exaple.com ,whcih was hosted in this dns server with IP 1.2.3.4 ,now we deleted the DNS entry of that website from our DNS Server (db.exmaple.com is deleted from named.conf ) and it is hosted with some other name server with IP... (1 Reply)
Discussion started by: sandeep.tk
1 Replies
LEARN ABOUT DEBIAN
dh_installinit
DH_INSTALLINIT(1) Debhelper DH_INSTALLINIT(1)NAME
dh_installinit - install init scripts and/or upstart jobs into package build directories
SYNOPSIS
dh_installinit [debhelperoptions] [--name=name] [-n] [-R] [-r] [-d] [--params]
DESCRIPTION
dh_installinit is a debhelper program that is responsible for installing init scripts with associated defaults files, as well as upstart
job files into package build directories.
It also automatically generates the postinst and postrm and prerm commands needed to set up the symlinks in /etc/rc*.d/ to start and stop
the init scripts.
FILES
debian/package.init
If this exists, it is installed into etc/init.d/package in the package build directory.
debian/package.default
If this exists, it is installed into etc/default/package in the package build directory.
debian/package.upstart
If this exists, it is installed into etc/init/package.conf in the package build directory.
OPTIONS -n, --noscripts
Do not modify postinst/postrm/prerm scripts.
-o, --onlyscripts
Only modify postinst/postrm/prerm scripts, do not actually install any init script, default files, or upstart job. May be useful if the
init script or upstart job is shipped and/or installed by upstream in a way that doesn't make it easy to let dh_installinit find it.
-R, --restart-after-upgrade
Do not stop the init script until after the package upgrade has been completed. This is different than the default behavior, which
stops the script in the prerm, and starts it again in the postinst.
This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon
will not get confused by the package being upgraded while it's running before using this option.
-r, --no-restart-on-upgrade
Do not stop init script on upgrade.
--no-start
Do not start the init script on install or upgrade, or stop it on removal. Only call update-rc.d. Useful for rcS scripts.
-d, --remove-d
Remove trailing d from the name of the package, and use the result for the filename the upstart job file is installed as in etc/init/ ,
and for the filename the init script is installed as in etc/init.d and the default file is installed as in etc/default/ . This may be
useful for daemons with names ending in d. (Note: this takes precedence over the --init-script parameter described below.)
-uparams --update-rcd-params=params
-- params
Pass params to update-rc.d(8). If not specified, defaults will be passed to update-rc.d(8).
--name=name
Install the init script (and default file) as well as upstart job file using the filename name instead of the default filename, which
is the package name. When this parameter is used, dh_installinit looks for and installs files named debian/package.name.init,
debian/package.name.default and debian/package.name.upstart instead of the usual debian/package.init, debian/package.default and
debian/package.upstart.
--init-script=scriptname
Use scriptname as the filename the init script is installed as in etc/init.d/ (and also use it as the filename for the defaults file,
if it is installed). If you use this parameter, dh_installinit will look to see if a file in the debian/ directory exists that looks
like package.scriptname and if so will install it as the init script in preference to the files it normally installs.
This parameter is deprecated, use the --name parameter instead. This parameter is incompatible with the use of upstart jobs.
--error-handler=function
Call the named shell function if running the init script fails. The function should be provided in the prerm and postinst scripts,
before the #DEBHELPER# token.
NOTES
Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command. Otherwise, it may cause multiple
instances of the same text to be added to maintainer scripts.
SEE ALSO debhelper(7)
This program is a part of debhelper.
AUTHORS
Joey Hess <joeyh@debian.org>
Steve Langasek <steve.langasek@canonical.com>
9.20120909 2012-04-10 DH_INSTALLINIT(1)