09-12-2018
Just a shot in the dark: did you consider supplying the full pathnames?
10 More Discussions You Might Find Interesting
1. Linux
installed fedora core 5 on a pc with USB and some usual things. in boot up it is stopped at "Starting udev:". Its harddisk light is busy. is it reconfiguring the kernel?. what do to solve this problem?. (0 Replies)
Discussion started by: GJ2
0 Replies
2. Shell Programming and Scripting
Hello all
I have to run manually make commands in our system the make compilations task's takes very long
And I like to be able to run another make task right after one is finished.
What is the best way to automate it ? (2 Replies)
Discussion started by: umen
2 Replies
3. Shell Programming and Scripting
Hello!
rescuecd:/var# fdisk -l | grep stupid
Disk /dev/sda doesn't contain a valid partition table
Disk /dev/sdb doesn't contain a valid partition table
rescuecd:/var#
It shows always this statement. Why? :(
Raw fdisk -l shows
rescuecd:/var# fdisk -l
Disk /dev/sda: 750.1 GB,... (4 Replies)
Discussion started by: pug123
4 Replies
4. Shell Programming and Scripting
Hi,
I worte a script which runs perfect when i execute it manually. But when i scheduled into cron the grep command alone is not working.
the sample script,
/usr/bin/grep FTP $subfile > /tmp/tfsrec.dat
tfs=`echo $?`
if
then
echo "FTP FOUND"
else
echo "FTP NOT FOUND"
Where... (5 Replies)
Discussion started by: thiru_cs
5 Replies
5. Filesystems, Disks and Memory
I'm curious about the behavior where any udev labeled device causes that corresponding listing to disappear from fdisk, sfdisk, or in the case of RDAC, lsvdev.
I have seen this on both EMC clariion and Sun Storagetek/Engenio 6540 arrays.
We use RHEL5.1 and udev to create persistent labels for... (2 Replies)
Discussion started by: Radar
2 Replies
6. Shell Programming and Scripting
Hello!
I'm sorry if this is the false Forum, didn't really knew where to put it...
My question:
I have serveral USB-Sticks and wrote several Udev-Rules for theme, each Sticks needs to do something else, but all are using the same script (they have common tasks to do) and only some parts are... (2 Replies)
Discussion started by: al0x
2 Replies
7. Solaris
I use fdisk -l command to see the attached hard disk drives in rhel5 and cntos 5.5 what is the same command for sun 5.9 (4 Replies)
Discussion started by: z_haseeb
4 Replies
8. Shell Programming and Scripting
hi
i want to automate fdisk command .
i spawned a process containing fdisk command from a process
and tried to send the options to fdisk promt from that process.
but that spawed process is notstarting itself
help me out
trying for two days
:wall:
my code:
#!/bin/bash
echo... (5 Replies)
Discussion started by: jagak89
5 Replies
9. BSD
Hello,
MBR partition table made by linux fdisk looks certainly not correct when printed by openbsd fdisk:
Partition table created on linux (centos 6.3):
# fdisk -l /dev/sdc
Disk /dev/sdc: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders
Units = cylinders of 16065 *... (2 Replies)
Discussion started by: vilius
2 Replies
10. UNIX for Beginners Questions & Answers
I have made a program that reads a text file and checks for palindromic words and then outputs them. They each appear on a new line with a count of the number of occurences beside each of the words.
Requirements for being classed as palindrome are that the word must have at least 3 letters and... (7 Replies)
Discussion started by: greenhouse91
7 Replies
LEARN ABOUT OPENDARWIN
dpkg-trigger
dpkg-trigger(1) dpkg suite dpkg-trigger(1)
NAME
dpkg-trigger - a package trigger utility
SYNOPSIS
dpkg-trigger [option...] trigger-name
dpkg-trigger [option...] command
DESCRIPTION
dpkg-trigger is a tool to explicitly activate triggers and check for its support on the running dpkg.
This can be used by maintainer scripts in complex and conditional situations where the file triggers, or the declarative activate triggers
control file directive, are insufficiently rich. It can also be used for testing and by system administrators (but note that the triggers
won't actually be run by dpkg-trigger).
Unrecognized trigger name syntaxes are an error for dpkg-trigger.
COMMANDS
--check-supported
Check if the running dpkg supports triggers (usually called from a postinst). Will exit 0 if a triggers-capable dpkg has run, or 1
with an error message to stderr if not. Normally, however, it is better just to activate the desired trigger with dpkg-trigger.
-?, --help
Show the usage message and exit.
--version
Show the version and exit.
OPTIONS
--admindir=dir
Change the location of the dpkg database. The default location is /var/lib/dpkg.
--by-package=package
Override trigger awaiter (normally set by dpkg through the DPKG_MAINTSCRIPT_PACKAGE environment variable of the maintainer scripts,
naming the package to which the script belongs, and this will be used by default).
--no-await
This option arranges that the calling package T (if any) need not await the processing of this trigger; the interested package(s) I,
will not be added to T's trigger processing awaited list and T's status is unchanged. T may be considered installed even though I
may not yet have processed the trigger.
--await
This option does the inverse of --no-await (since dpkg 1.17.21). It is currently the default behavior.
--no-act
Just test, do not actually change anything.
EXIT STATUS
0 The requested action was successfully performed. Or a check or assertion command returned true.
1 A check or assertion command returned false.
2 Fatal or unrecoverable error due to invalid command-line usage, or interactions with the system, such as accesses to the database,
memory allocations, etc.
ENVIRONMENT
DPKG_ADMINDIR
If set and the --admindir option has not been specified, it will be used as the dpkg data directory.
SEE ALSO
dpkg(1), deb-triggers(5), /usr/share/doc/dpkg-dev/triggers.txt.gz.
1.19.0.5 2018-04-16 dpkg-trigger(1)