03-28-2008
The inode changed there so you really have a new file there, under the hood. Some editors work like that, for various reasons.
For tracking system-wide when a named file has changed, with history, you need to install some additional software which monitors the file system for you; the desired functionality is not available by default. If you are on a HAL system (try man hald) then I think it may offer something like this, possibly as an add-on.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Like the topic says, does anyone know if it is possible to check to see when an FTP only user has logged in? Because the shell is /bin/false and they are only using FTP to access the system doing a "finger" or "last" it says they have never logged in.
Is there a way to see when ftp users log in... (1 Reply)
Discussion started by: LordJezo
1 Replies
2. Solaris
Hi all -
I've searched the forums and seen a few questions related, but nothing which explicitly answers what I'm looking for.
I need to know if there's ANY way to get the modification history of any users crontab.
Yes, I know that crontabs are in /var/spool/cron. I know that the... (2 Replies)
Discussion started by: amcq
2 Replies
3. Shell Programming and Scripting
Can anyone please suggest an alternate command for "stat" . I am trying this on Solaris 5.9 , but the command doesn't exist.
Basically i need to see one particalar file modification history. Any help is appreciated. (4 Replies)
Discussion started by: mk1216
4 Replies
4. Shell Programming and Scripting
Hi All,
I am a pretty new to programming or scripting. Please help me in my below query.
I want to write a script which can track a file for any kind of modification and if there is any modification then it should move that file or i should say backup that file to another server.
Please... (6 Replies)
Discussion started by: makkar4u
6 Replies
5. Solaris
What is the command for checking modification history on file?
---------- Post updated at 01:20 PM ---------- Previous update was at 12:35 PM ----------
Let me rephrase this. On a regular Unix file can I at least check to see the time and date history modification of the file? (6 Replies)
Discussion started by: jastanle84
6 Replies
6. UNIX for Advanced & Expert Users
Hi all,
My need is :
1. To know who , when , which command used.
2. Local user should not delete this information.
I mean , with an example , i can say
i have a user user1
i need to give all the following permissions to user1, :
a. A specific directory other than his home... (3 Replies)
Discussion started by: linuxadmin
3 Replies
7. UNIX for Dummies Questions & Answers
Hi all,
My need is :
1. To know who , when , which command used.
2. Local user should not delete this information.
I mean , with an example , i can say
i have a user user1
i need to give all the following permissions to user1, :
a. A specific directory other than his home... (1 Reply)
Discussion started by: sriky86
1 Replies
8. Shell Programming and Scripting
Hello :)
I'm a newb when it comes to shell scripting and was wondering about a command(s) for a script that could be used to checkout a certain number of version/revision histories of a file. I know for the latest revison you "co filename" or for a certain revision number "co -r*.* filename"... (2 Replies)
Discussion started by: MN-DBA
2 Replies
9. Shell Programming and Scripting
commands to view the history file in unix.
I am not sure whether it is bash_history.sh (1 Reply)
Discussion started by: ramkumar15
1 Replies
10. What is on Your Mind?
I am pleased to announce this new video in 1080 HD for UNIX lovers honoring thirty years of UNIX history spanning from 1969 to 1999 presented in 150 seconds (two and a half minutes) in 1080 HD, celebrating the 50th anniversary of UNIX.
The Great History of UNIX (1969-1999) | 30 Years of UNIX... (8 Replies)
Discussion started by: Neo
8 Replies
LEARN ABOUT OPENDARWIN
hald
HALD(8) System Manager's Manual HALD(8)
NAME
hald - HAL daemon
SYNOPSIS
hald [options]
DESCRIPTION
hald is a daemon that maintains a database of the devices connected to the system system in real-time. The daemon connects to the D-Bus
system message bus to provide an API that applications can use to discover, monitor and invoke operations on devices. For more information
about both the big picture and specific API details, refer to the HAL spec which can be found in /usr/share/doc/hal-doc/spec/hal-spec.html
depending on the distribution.
OPTIONS
The following options are supported:
--daemon=yes|no
Specify whether to run in the foreground or the background.
--verbose=yes|no
Enable verbose debug output.
--use-syslog
Enable logging of debug output to the syslog instead of stderr. Use this option only together with --verbose.
--help Print out usage.
--version
Print the version of the daemon and exit.
BUGS AND DEBUGGING
Please send bug reports to either the distribution or the HAL mailing list, see http://lists.freedesktop.org/mailman/listinfo/hal on how to
subscribe.
First, to obtain useful debug traces you will need to have debuginfo packages installed. On a Fedora system this is in the hal-debuginfo
package and can be installed via the yum update program.
Second, shut down the existing hald daemon instance; on a Fedora system this is achieved by
/etc/init.d/haldaemon stop
After having shut down the daemon, you might want to run
pkill hald
to ensure that all the helper processe of hald are killed too. To start the HAL daemon, use
/usr/sbin/hald --daemon=no --verbose=yes
If the daemon crashes, you can start it under a debugger via
gdb /usr/sbin/hald
and then typing
run --daemon=no --verbose=yes
at the (gdb) prompt. To capture a back trace, use the bt command and attach this to the bug report.
Please also attach the output of lshal(1) in the bug report if possible (it's not possible if the hald daemon crashed). If the nature of
the bug has to do with hotplugging, attach two outputs of lshal(1) - one before the device hotplug event and one after.
SEE ALSO
udev(7), dbus-daemon(1), lshal(1), hal-set-property(1), hal-get-property(1), hal-find-by-property(1), hal-find-by-capability(1), hal-is-
caller-locked-out(1)
AUTHOR
Written by David Zeuthen <david@fubar.dk> with a lot of help from many others.
HALD(8)