katie/continuwuity-bsd

Fork 0

rc script issues #1

New issue

Closed

opened 2026-05-03 20:58:16 +00:00 by Ghost · 3 comments

Ghost commented

2026-05-03 20:58:16 +00:00

(Migrated from code.kat5.dev)

Hey,

I am so glad that I found your repo! I am fiddling with continuwuity quite a bit building it under FreeBSD, however with 0.5.8 I gave up..

I am running 15.0-p8 on latest with rocksdb-10.10.1 and installed the 0.5.8-generic variant. However starting thrws some rc-script issues:

# service -v continuwuity start
continuwuity is located in /usr/local/etc/rc.d
Starting continuwuity.
Unmatched '"'.
/usr/local/etc/rc.d/continuwuity: WARNING: failed to start continuwuity

If I start it directly via # su -m continuwuity -c '/usr/local/bin/continuwuity -c /usr/local/etc/continuwuity/continuwuity.toml' it starts.

My knowlege for rc-scripting is totally not existing (tried to solve it though but gave up..) - do you have a hint where to start (and whats gooing in the wrong direction?

Greetings
Sven

Hey, I am so glad that I found your repo! I am fiddling with continuwuity quite a bit building it under FreeBSD, however with 0.5.8 I gave up.. I am running 15.0-p8 on latest with rocksdb-10.10.1 and installed the 0.5.8-generic variant. However starting thrws some rc-script issues: ``` # service -v continuwuity start continuwuity is located in /usr/local/etc/rc.d Starting continuwuity. Unmatched '"'. /usr/local/etc/rc.d/continuwuity: WARNING: failed to start continuwuity ``` If I start it directly via `# su -m continuwuity -c '/usr/local/bin/continuwuity -c /usr/local/etc/continuwuity/continuwuity.toml' ` it starts. My knowlege for rc-scripting is totally not existing (tried to solve it though but gave up..) - do you have a hint where to start (and whats gooing in the wrong direction? Greetings Sven

Ghost commented

2026-05-05 20:14:51 +00:00

(Migrated from code.kat5.dev)

Found it:

daemon.log shows a number of

May 4 21:06:23 host continuwuity[25924]: Error: TOML parse error at line 1, column 15 | 1 | database_path=/var/db/continuwuity | ^^^^^^^^^^^^^^^^^^^^ string values must be quoted, expected literal string

entries. I removed the -O database_path="'\\\"'"${continuwuity_data_dir}"'\\\"'" and -O log_colors=false -c from the rc-script. The data dir is mentioned in the continuwuity.toml and the color bug doesn't bother me (I am the only user on the server). To be on the safe side I escaped the -c /path/to/config.toml, my command_args line looks like that now:

command_args="-S -p ${pidfile} -T continuwuity ${procname} -c \"/usr/local/etc/continuwuity/continuwuity.toml\""

and it works, continuwuity starts :)

Found it: daemon.log shows a number of `May 4 21:06:23 host continuwuity[25924]: Error: TOML parse error at line 1, column 15 | 1 | database_path=/var/db/continuwuity | ^^^^^^^^^^^^^^^^^^^^ string values must be quoted, expected literal string ` entries. I removed the `-O database_path="'\\\"'"${continuwuity_data_dir}"'\\\"'"` and `-O log_colors=false -c` from the rc-script. The data dir is mentioned in the continuwuity.toml and the color bug doesn't bother me (I am the only user on the server). To be on the safe side I escaped the -c /path/to/config.toml, my command_args line looks like that now: `command_args="-S -p ${pidfile} -T continuwuity ${procname} -c \"/usr/local/etc/continuwuity/continuwuity.toml\""` and it works, continuwuity starts :)

Ghost commented

2026-05-07 06:59:05 +00:00

(Migrated from code.kat5.dev)

The original error from the service command is odd, that sounds like it came from the shell, but I can't imagine why that would be returned unless $continuwuity_data_dir was explicitly empty or had a quote in it or something. I'll have to see if providing a later value in continuwuity.toml conflicts with it somehow.

The original error from the `service` command is odd, that sounds like it came from the shell, but I can't imagine why that would be returned unless `$continuwuity_data_dir` was explicitly empty or had a quote in it or something. I'll have to see if providing a later value in `continuwuity.toml` conflicts with it somehow.

Ghost commented

2026-06-16 19:38:29 +00:00

(Migrated from code.kat5.dev)

After some conversations in #bsd, I think the right move here is to remove the $continuwuity_data_dir RC variable and leave it up to the user (or a patch) to set database_path correctly. Otherwise we're stepping on the official documentation's toes, and splitting the config file in an arcane way.

Setting the permissions and owner correctly (my original concern in this area) should be doable via the packing list, and a message can be shown warning the user about it.

After some conversations in `#bsd`, I think the right move here is to remove the `$continuwuity_data_dir` RC variable and leave it up to the user (or a patch) to set `database_path` correctly. Otherwise we're stepping on the official documentation's toes, and splitting the config file in an arcane way. Setting the permissions and owner correctly (my original concern in this area) should be doable via the packing list, and a message can be shown warning the user about it.

katie referenced this issue from a commit

2026-07-09 14:41:03 +00:00

freebsd: create DB dir during install instead of from RC script.

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

katie/continuwuity-bsd#1

No description provided.

Rows
Columns