08-05-2013
Thank everyone, I devised my own fix. I converted the txt file to xml and that made extraction much easier.
Mike
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Quick question...I'm trying to grab the .tif file name from this output from our fax server. What is the best way i can do this in a bash script? I have been looking at regular expressions with bash or using awk but having some trouble. thanks! The only output i want is... (5 Replies)
Discussion started by: kuliksco
5 Replies
2. UNIX for Dummies Questions & Answers
hiii, Help me out..i have a huge set of data stored in a file.This file has has 2 columns which is latitude & longitude of a region. Now i have a program which asks for the number of points & based on this number it asks the user to enter that latitude & longitude values which are in the same... (7 Replies)
Discussion started by: reva
7 Replies
3. UNIX for Dummies Questions & Answers
Hi folks;
I have a temperature sensor that configured with an IP address so we can open a browser to see the temperatures in our 3 labs all showing in one screen.
I'm trying to write a script to call this link then email me the results/output so i don't have to open a browser manually every... (3 Replies)
Discussion started by: Katkota
3 Replies
4. Shell Programming and Scripting
Hi,
I have a file with one column data (sample below) and I am trying to write a shell script to calculate the difference between consecutive data valuse i.e
Var = Ni -N(i-1)
0.3141
-3.6595
0.9171
5.2001
3.5331
3.7022
-6.1087
-5.1039
-9.8144
1.6516
-2.725
3.982
7.769
8.88 (5 Replies)
Discussion started by: malandisa
5 Replies
5. Shell Programming and Scripting
Hello,
I am really stuck and I'm hoping somone can help. I have a text file that is similar to this:
<--First User-->
<function>account='uid=user1,.......
<--Second User-->
<function>account='uid=user2,.......What I want is to grab the usernames after "uid=" and before the following... (9 Replies)
Discussion started by: mafia910
9 Replies
6. Shell Programming and Scripting
If I have a txt file with
test.txt
somelineoftext
and I want to set that line of text to variable in a script:
so
#!/bin/bash
var=''
becomes
#!/bin/bash
var='somelineoftext' (3 Replies)
Discussion started by: digitalviking
3 Replies
7. Shell Programming and Scripting
Hi,
I have a Report.txt file. Say the contents of this file are :
1 2 3 4 5 7 df v g gf
e r dfkf lsdk dslsdklsdk
Report Start: xxxxxxdad
asdffsdfsdfsdfasfasdffasdf
sadfasdfsadffsfsdf Report End.
sdfasdfasdf
sdfasfdasdfasdfasdfasdf
sadfasdfsdf
I need to grab from Report Start... (3 Replies)
Discussion started by: mrskittles99
3 Replies
8. Shell Programming and Scripting
Hello there,
I am a beginner in Perl, and I have a challenging project:
I have to create a program that checks regularly on an online bank account for new operations, it should then feed a database keeping track of all the money going in and out.
Of course the login details of this online... (4 Replies)
Discussion started by: freddie50
4 Replies
9. Shell Programming and Scripting
I have a file full of coordinates of the form:
37.68899917602539 58.07500076293945 57.79100036621094
The numbers don't always have the same number of decimal points. I need to reduce the decimal points of all the numbers (there are 128 rows of 3 numbers) to 2.
I have tried to do this... (2 Replies)
Discussion started by: crunchgargoyle
2 Replies
10. Shell Programming and Scripting
I would like to grab complex html text between lines using variables. I am running Debian and using mksh shell.
Here is the part of the html that I want to extract from. I would like to extract the words 'to love,' and I would like to use the above and below lines as reference points.
... (3 Replies)
Discussion started by: bedtime
3 Replies
LEARN ABOUT CENTOS
systemd.device
SYSTEMD.DEVICE(5) systemd.device SYSTEMD.DEVICE(5)
NAME
systemd.device - Device unit configuration
SYNOPSIS
device.device
DESCRIPTION
A unit configuration file whose name ends in ".device" encodes information about a device unit as exposed in the sysfs/udev(7) device tree.
This unit type has no specific options. See systemd.unit(5) for the common options of all unit configuration files. The common
configuration items are configured in the generic "[Unit]" and "[Install]" sections. A separate "[Device]" section does not exist, since no
device-specific options may be configured.
systemd will dynamically create device units for all kernel devices that are marked with the "systemd" udev tag (by default all block and
network devices, and a few others). This may be used to define dependencies between devices and other units. To tag a udev device, use
"TAG+="systemd"" in the udev rules file, see udev(7) for details.
Device units are named after the /sys and /dev paths they control. Example: the device /dev/sda5 is exposed in systemd as dev-sda5.device.
For details about the escaping logic used to convert a file system path to a unit name see systemd.unit(5).
THE UDEV DATABASE
The settings of device units may either be configured via unit files, or directly from the udev database (which is recommended). The
following udev device properties are understood by systemd:
SYSTEMD_WANTS=
Adds dependencies of type Wants from the device unit to all listed units. This may be used to activate arbitrary units when a specific
device becomes available. Note that this and the other tags are not taken into account unless the device is tagged with the "systemd"
string in the udev database, because otherwise the device is not exposed as systemd unit (see above). Note that systemd will only act
on Wants dependencies when a device first becomes active, it will not act on them if they are added to devices that are already active.
Use SYSTEMD_READY= (see below) to influence on which udev event to trigger the device dependencies.
SYSTEMD_ALIAS=
Adds an additional alias name to the device unit. This must be an absolute path that is automatically transformed into a unit name.
(See above.)
SYSTEMD_READY=
If set to 0, systemd will consider this device unplugged even if it shows up in the udev tree. If this property is unset or set to 1,
the device will be considered plugged the moment it shows up in the udev tree. This property has no influence on the behavior when a
device disappears from the udev tree. This option is useful to support devices that initially show up in an uninitialized state in the
tree, and for which a "changed" event is generated the moment they are fully set up. Note that SYSTEMD_WANTS= (see above) is not acted
on as long as SYSTEMD_READY=0 is set for a device.
ID_MODEL_FROM_DATABASE=, ID_MODEL=
If set, this property is used as description string for the device unit.
SEE ALSO
systemd(1), systemctl(8), systemd.unit(5), udev(7), systemd.directives(7)
systemd 208 SYSTEMD.DEVICE(5)