| 1 |
On Saturday 06 December 2008 23:40:15 Philip Webb wrote: |
| 2 |
> At start-up & shut-down, lines appear on screen : |
| 3 |
> |
| 4 |
> /var/log/lvm2.log : fopen failed : No such file or directory |
| 5 |
> |
| 6 |
> When I check for the file I get : |
| 7 |
> |
| 8 |
> root:537 log> pwd |
| 9 |
> /var/log |
| 10 |
> root:538 log> ls -l lvm2.log |
| 11 |
> -rw-rw-rw- 1 root root 116194 2007-11-02 04:49 lvm2.log |
| 12 |
> root:539 log> file lvm2.log |
| 13 |
> lvm2.log: ASCII text |
| 14 |
> |
| 15 |
> It seems it was written when I set up LVM on this machine in 2007 , |
| 16 |
> but hasn't been accessible since then. |
| 17 |
> |
| 18 |
> Is the problem that /var is not mounted at these moments ? |
| 19 |
> |
| 20 |
> root:535 log> df |
| 21 |
> Filesystem 1K-blocks Used Available Use% Mounted on |
| 22 |
> ... |
| 23 |
> /dev/mapper/lvm-var 2097084 647704 1449380 31% /var |
| 24 |
> |
| 25 |
> If so, what is the correct way out of the jam ? |
| 26 |
|
| 27 |
I left mine at the defaults settings, thusly |
| 28 |
|
| 29 |
log { |
| 30 |
|
| 31 |
# Controls the messages sent to stdout or stderr. |
| 32 |
# There are three levels of verbosity, 3 being the most verbose. |
| 33 |
verbose = 0 |
| 34 |
|
| 35 |
# Should we send log messages through syslog? |
| 36 |
# 1 is yes; 0 is no. |
| 37 |
syslog = 1 |
| 38 |
|
| 39 |
# Should we log error and debug messages to a file? |
| 40 |
# By default there is no log file. |
| 41 |
#file = "/var/log/lvm2.log" |
| 42 |
|
| 43 |
# Should we overwrite the log file each time the program is run? |
| 44 |
# By default we append. |
| 45 |
overwrite = 0 |
| 46 |
|
| 47 |
# What level of log messages should we send to the log file and/or syslog? |
| 48 |
# There are 6 syslog-like log levels currently in use - 2 to 7 inclusive. |
| 49 |
# 7 is the most verbose (LOG_DEBUG). |
| 50 |
level = 0 |
| 51 |
|
| 52 |
Seems this is adequate to get around your dilemma |
| 53 |
|
| 54 |
|
| 55 |
|
| 56 |
-- |
| 57 |
alan dot mckinnon at gmail dot com |
Archives