Summary: | GNOKII Version 0.6.4 will only run as root | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Colin Tinker <g1gsw> |
Component: | New packages | Assignee: | Gentoo Dialup Developers <net-dialup> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Colin Tinker
2005-02-06 09:07:54 UTC
Please set proper permissions on /var/lock directory (you must have w) and tell me if this solved your problem. Setting /var/lock to be writable by the user does fix this but would it not make more sense to have the application write its lock file in the users home directory? On a multi user system /var/lock would have to be world writable which could be a security risk. Another issue with gnokki and xgnokii seems to be the amount of memory and cpu it uses. I have 1gb of memory and it will use it all with around a gb of swap space pushing the cpu usage through the roof. I didn't say to set /var/lock world writable. I've suggested to have w right in this dir. The best way is to be member in uucp group (or whatever group is set on this dir). The whole idea of locking mechanism is to make a specific resource globally unavailable for other applications, either if you lauch them or another user. If you set lock dir to be $HOME dependent, you loose the global efect, doesn't it? You could set "use_locking = no", you know... As for the second issue, I've just launched xgnokii on a lousy notebook with 256M. With xfce, xgnokii, firefox and thunderbird running, memory used is insignificant (a quarter of the entire physical memory). |