9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi @all!
In my MySQL-backup-script I backup and compress every single table with this command:
/usr/bin/mysqldump --opt database_x table_y | /usr/bin/pbzip2 -c > "/media/BackUpDrive/Backup/table_x.gz"Unfortunately these files need modification - they have to start with the following line(s):... (7 Replies)
Discussion started by: gogo555
7 Replies
2. Ubuntu
I'm I able to make vlc or mplayer transparent.
If so how can i do it please.
thanks in advance josh (0 Replies)
Discussion started by: jtsmith90
0 Replies
3. UNIX for Dummies Questions & Answers
in windows you can encrypt and compress file via it properties.
It compress the file in a way that is transparent, I mean you do know that it is compressed, but you can work with it as if it is not, you don't need to decompress it in order to edit it or watch it.
The same go for encryption as... (0 Replies)
Discussion started by: programAngel
0 Replies
4. Shell Programming and Scripting
I have a DB folder which sizes to 60GB approx. It has logs which size from 500MB - 1GB. I have an Installation which would update the DB. I need to backup this DB folder, just incase my Installation FAILS. But I do not need the logs in my backup. How do I exclude them during compression (tar)?
... (2 Replies)
Discussion started by: DevendraG
2 Replies
5. Virtualization and Cloud Computing
Hello,
If you switch to "seamless mode" in virtualbox, you can see the taskbar of the OS on your screen , like having a transparent background on your VM.
My question: is there a possibility to do the same in VMware's Workstation (7) ? I know and use the "Unity" mode in Workstation/Player, but... (0 Replies)
Discussion started by: al0x
0 Replies
6. UNIX for Advanced & Expert Users
I am trying to list the name of files on an MOD - I use the command
tar vtf /MOD_DRIVE|more
and I get a nice list of filenames/directories on this particular MOD. When I put in another MOD that contains software options I get the error "directory checksum error". I would like to be able to... (2 Replies)
Discussion started by: drew_holm
2 Replies
7. UNIX for Advanced & Expert Users
I have been doing some investigation into a log file from one of my systems, and the means which I currently use to compress and rotate it. I am looking for something smarter than gzip, faster than bzip2, and that can match or beat "my script" (which is slow as heck, but WAY better compression... (2 Replies)
Discussion started by: jjinno
2 Replies
8. Solaris
Hi. Is there an app available for Solaris 9 that will play real audio media files (.ram)? It doesn't look like RealPlayer for UNIX supports version 9. I'd imagine there is an open source app out there somewhere, but I just haven't found it yet.
Thank.
P.S. I don't really need streaming... (2 Replies)
Discussion started by: Plain Person
2 Replies
9. Shell Programming and Scripting
I just want to make my xterm to be transparent, but I don't know how, could somebody tell me?
:( (3 Replies)
Discussion started by: zhiyuan
3 Replies
UDISKS-GLUE.CONF(5) udisks-glue Manual UDISKS-GLUE.CONF(5)
NAME
udisks-glue.conf - udisks-glue configuration file format
SYNOPSIS
~/.udisks-glue.conf
$XDG_CONFIG_HOME/udisks-glue/config
/etc/udisks-glue.conf
$XDG_CONFIG_DIRS/udisks-glue/config
DESCRIPTION
udisks-glue is configured by a series of match directives referencing filter directives. Filter directives define parameters that filter
the UDisks events. Match directives specify actions to be taken by udisks-glue in case the corresponded filter matches.
Filter and match directives can be specified in any order. You should use unique names for filter directives. The rules are evaluated in
the order the match directives are specified. A default directive is a special directive used as a fallback in case no other directives
match. It does not reference a filter directive. You may choose not to specify a default directive.
Due to the way the rules are evaluated, it's recommended that more specific match directives are defined before less specific ones. If a
match directive does not specify one of the available actions, another directive may be chosen. The currently available match directives
are:
automount If set, try to automatically mount the device (unset by default)
automount_filesystem Filesystem type to use when automounting the device
automount_options List of options to use when automounting the device
post_insertion_command Command to run after a device is inserted or after its media has been made available
post_mount_command Command to run after a device has been mounted
post_unmount_command Command to run after a device has been unmounted
post_removal_command Command to run after a device or its media has been removed
udisks-glue will substitute some tokens with information about the device in each of the commands listed above:
%device_file Path to the device file
%mount_point Last known mount point for the device (only replaced in post_mount_command and post_unmount_command)
The currently supported filter parameters are:
label (string) User-visible label of the detected file system
optical (boolean) Set if the device uses optical disc as its media
optical_disc_closed (boolean) Set if the optical disc is closed
optical_disc_has_audio_tracks (boolean)
Set if the optical disc has audio tracks
optical_disc_has_audio_tracks_only (boolean)
Set if all tracks in the optical disc are audio tracks
partition (boolean) Set if the device is a partition of another device
partition_table (boolean) Set if the device has a partition table
readonly (boolean) Set if the device is a ready-only device
removable (boolean) Set if the device is a removable device
type (string) Extended information about the device, generally set to the name of the detected file system if the usage
property is set to filesystem
usage (string) The result of probing for signatures on the block device, generally set to filesystem if a mountable file
system was detected
uuid (string) UUID of the detected file system
Note that the rules are evaluated only at the time the device or its media is inserted. Internal drives are always ignored.
EXAMPLE
The following configuration example shows how you can automount USB pendrives and similar devices. Notifications are provided by a custom
script that could display on-screen information or provide notifications in some other way:
filter disks {
optical = false
partition_table = false
usage = filesystem
}
match disks {
automount = true
automount_options = sync
post_mount_command = "mount-notify mounted %device_file %mount_point"
post_unmount_command = "mount-notify unmounted %device_file %mount_point"
}
A more complex example shows how the filters can be used to mount optical and non-optical media (USB pendrives and the like) using differ-
ent mount options and how a specific program can be launched on non-closed optical discs.
#
# Filters
#
filter disks {
optical = false
partition_table = false
usage = filesystem
}
filter burnable {
optical = true
optical_disc_closed = false
}
filter optical {
optical = true
}
#
# The default entry (only used if no filters match)
#
default {
post_insertion_command = "insertion-notify %device_file"
}
#
# Additional entries
#
match disks {
automount = true
automount_options = { sync, noatime }
post_mount_command = "mount-notify mounted %device_file %mount_point"
post_unmount_command = "mount-notify unmounted %device_file %mount_point"
}
match burnable {
post_insertion_command = "k3b %device_file"
post_mount_command = "mount-notify mounted %device_file %mount_point"
post_insertion_command = "udisks --mount %device_file --mount-options ro"
}
match optical {
automount = true
automount_options = ro
post_mount_command = "mount-notify mounted %device_file %mount_point"
post_insertion_command = "udisks --mount %device_file --mount-options ro"
}
SEE ALSO
udisks(1), udisks-glue(1) udisks(7), udisks-daemon(8)
udisks-glue 2011-04-20 UDISKS-GLUE.CONF(5)